Seam 3 snapshots
by Pete Muir
Ondrej/Dan,
Can we get Seam 3 module snapshots deploying to snapshots.jboss.org (I
just deployed one manually) on a nightly basis from Hudson?
Ondrej, if you can set up the jobs, Dan can give you guidance on what
commands and svn URLs to use.
Thanks!
15 years, 8 months
Problem building Seam-permalink example
by Pete Muir
For now I've removed it from the default examples
[INFO]
------------------------------------------------------------------------
[INFO] Building Seam Permalink Example (Servlet)
[INFO] task-segment: [eclipse:m2eclipse]
[INFO]
------------------------------------------------------------------------
[INFO] Preparing eclipse:m2eclipse
...
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) com.steeplesoft.jsf:facestester:jar:0.2.PR1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.steeplesoft.jsf -
DartifactId=facestester -Dversion=0.2.PR1 -Dpackaging=jar -Dfile=/path/
to/file
Alternatively, if you host your own repository you can deploy the
file there:
mvn deploy:deploy-file -DgroupId=com.steeplesoft.jsf -
DartifactId=facestester -Dversion=0.2.PR1 -Dpackaging=jar -Dfile=/path/
to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.seam.examples:seam-servlet-permalink:war:3.0.0-SNAPSHOT
2) com.steeplesoft.jsf:facestester:jar:0.2.PR1
----------
1 required artifact is missing.
for artifact:
org.jboss.seam.examples:seam-servlet-permalink:war:3.0.0-SNAPSHOT
from the specified remote repositories:
snapshots.jboss.org (http://snapshots.jboss.org/maven2),
central (http://repo1.maven.org/maven2),
repository.jboss.org (http://repository.jboss.org/maven2)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 28 seconds
[INFO] Finished at: Fri May 29 14:49:16 BST 2009
[INFO] Final Memory: 39M/80M
[INFO]
------------------------------------------------------------------------
15 years, 8 months
2.1.2 release
by Norman Richards
I haven't seen any issues with CR2, so I think we should get the final
release process going. Does anyone need more time for anything?
15 years, 8 months
jsf in seam 3
by Dan Allen
Working on the booking example has allowed me to gain a perspective about
what services we need right away out of the faces (jsf) module. Perhaps it
can be removed once the next rev of the EL is ready, but for now we need
JBoss EL to get parametrized EL expressions. That means providing a custom
JSF Application factory.
Fortunately, overriding the default Application impl got way simpler in JSF
2.0 since the spec now provides a base implementation class that you can
override a single method at a time. We can eliminate these overrides as they
come available in the platform. But for now we need it.
...that brings me to my next very important point. I think we need to be
developing against the JSF trunk. The last release, PR2, does not have any
of the features that we recently contributed, making development against PR2
almost pointless. I would like to compile a JSF release, call it 2.0.0-PR2_1
(or suggest another version number), deploy it to the JBoss repository, and
Seam can depend on that for now. If there are no objections, I will do that
today.
Going back to the faces module, instead of continuing with the
org.jboss.seam.jsf and org.jboss.seam.faces package split in Seam 3, I think
we should put all the faces classes under org.jboss.seam.faces and use
appropriate sub-package names. So in this case, I propose
org.jboss.seam.faces.application.SeamApplicationFactory and
org.jboss.seam.faces.application.SeamApplication for overriding the default
Application impl. We will also need the org.jboss.seam.el package (perhaps
module).
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
15 years, 8 months
Will we release 2.0.3 GA?
by Christian Bauer
All the issues for CR2 and GA seem to be DONE, any reason why we
didn't release it?
15 years, 8 months
Message to the moderator
by Denis Forveille
Dear seam-dev moderator,
In the last weeks, I tried to post a few messages on the seam-dev list
without great success. For some messages I received a message telling me
that my message was under review by you, the moderator, and for other I
recevied nothing at all.
In both cases, my messages have not been post and I don't know why
What's going on? Could I have an explaination?
Thanks in advance
For example I post two messages signaling the fact that some download links
were broken since weeks on the seam WiKi, but they hav not been posted..
Denis Forveille
15 years, 8 months
Re: [webbeans-dev] Seam-bridge-api and seam-webbeans-bridge question
by Dan Allen
On Fri, May 22, 2009 at 5:50 PM, Clint Popetz <cpopetz(a)gmail.com> wrote:
> Hi,
>
> Is there any reason seam-bridge-api and seam-webbeans-bridge shouldn't move
> to
> webbeans-extensions? I have this jira issue:
>
> https://jira.jboss.org/jira/browse/WBX-34
>
> to allow the webbeans wicket support to work with any jsr-299 impl,
> and part of making that work is providing a way for the wicket
> extension to grab the current manager instance. It seems like this
> functionality
> is useful independent of seam.
I think we are engaging in a struggle over ownership of features and
defining boundaries between Seam and WB.
In my definition, Seam is the universal middleware stack at Red Hat which is
most definitely independent of JSR-299 implementation. Therefore, it's my
position that anything that "extends" 299 towards "rich web" should be a
module of Seam. Extensions which don't go in that direction, such as the
Java SE support, are a better fit as a webbeans extension. Furthermore, I
don't think you should feel like you "have to depend on Seam" because it
isn't going to be like Seam 2 where it is all or nothing. Modules are
starkely independent and can be seen as a lose collection of extensions.
Perhaps others will disagree with my definition, or think it too liberal,
but if we don't define where Seam begins, then you could easily rationalize
all modules of Seam be extensions of Web Beans...I will admit though that
the bridge is a gray area in that it could go either way.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
15 years, 8 months
Seam examples via JBoss Tools Project Examples + Cheatsheets
by Max Rydahl Andersen
Hi,
I thought you might be interested in this.
We've started adding the Seam examples to our Project Examples feature
in JBoss Tools/Developer Studio.
Primarily because they are very well documented and that users are
asking "how to run the examples in eclipse".
So Snjezana have been doing a couple proof of concepts, the last one
being the "Message" example.
http://www.screencast.com/users/Snjeza/folders/Jing/media/a8430ad8-a642-4...
Please take a look at the screencast above and let me know what you
think. We haven't uploaded this to project examples yet,
but will do shortly - especially if you give us feedback ;)
p.s. the screencast shows Maven updating dependencies but that is just
m2eclipse running - it is not a requirement
to use this.
/max
15 years, 8 months
