I've reduced the session timeouts for in.relation.to and
seamframework.org to 5 minutes and 15 minutes respectively, from 30
minutes. If anyone experiences any issues with this new configuration
please let me know, however it already seems to have had a positive
effect on performance so far.
sorry for posting this to the group, but I feel that this is at least
_related_ to Seam 3 / development...
My issue is the more or less *complete *unreachability of seamframework.org,
since over a week inbetween (at least from Central Europe). Sometimes I get
through to the site, which then renders more or less normal, but most of the
time it's just a long wait for the timeout.
*HTTP Status 400 - Request failed, please check the application log or
contact the administrator (pmuir(a)redhat.com):
'javax.resource.ResourceException, No ManagedConnections available within
configured blocking timeout ( 5000 [ms] ) in
I know that none of you is an administrator, but since this has started to
have serious influence on the Seam 3 / Seam 2 / Weld community, I figured
that someone in this mailing-list might at least be able to check if anyone
at JBoss/RedHat is taking care of the problem, and maybe "emphasize" the
importance a bit ;-)
I would like to propose a new module on Seam: *Seam Cache*.
That module would be JSR-107 compatible (essentially Infinispan and EhCache)
and would allow to:
1) @Inject Cache cache;
2) Provide a new scope @CacheScoped(regionName="xx"). That would live for
the time of the cache configured by the region name itself.
The module should be tested on Inifinispan and EhCache.
What do you guys think ?
I've forked the Seam Cron module and:
* made it work with Seam 3 Final
* switched to Arquillian as testing framework
* renamed into org.jboss.seam.cron package
* made it's pom.xml compliant with other Seam 3 modules.
* removed dependency on commons-collection and used slf4j-api instead
IMO it's a good step towards a beta/production release. In fact, I'm using
it in production - and didn't want to create my own scheduling extension.
Except for package naming, no API has changed.
Since I'm not a committer, I published it in a forked github repo:
https://github.com/cjalmeida/cron. Be my guest to incorporate it into
BTW, thanks again for the great framework.
View this message in context: http://seam-framework.2283336.n4.nabble.com/Seam-Cron-tp3439156p3439156.html
Sent from the seam-dev mailing list archive at Nabble.com.
I'd like to start up a weekly Seam module spotlight. Basically, each
week I'd like one of you to write up an article that we can publish on
in.relation.to that shows off the best features of your module.
Preferably the article would be use-case centric, as opposed to the
feature-centric style that we generally write with in the reference
documentation. For example, if I was writing a blog post about the
persistence module I would make the point that if you're writing POJO
beans to implement your business layer that I would not have transaction
support by default, and that is where the transaction features of the
persistence module come in. I'd also explain how it could be useful in
other container environments, such as Tomcat or even Java SE.
This style of writing is more likely to get your readers to a point
where they understand why your module is as cool as we say it is, as
they can relate its coolness in terms of real life use cases. Whereas
explaining things from a feature point of view might leave some confused
as to how they can actually *use* that feature in their own projects.
Anyway, I'm looking for a brave volunteer to go first. Ideally we'd get
the first spotlight article published by the end of next week (before
the 9th) so that should leave enough time to put together an informative
Talking with Seam/CDI tooling team at EclipseCon and we are still in the dark on how tooling are supposed to identify CDI extensions that are registered programmatically and often does not have a beans.xml to "mark" them.
Today we do it by simply scanning jars with *weld*.jar naming pattern (very brittle and not good for 3rd party extensions).
Furthermore we also have a list of classes to include/exclude since some components in these jars aren't CDI compliant.
How do we go about identifying these things ?
The idea discussed with Dan/Pete on this topic previously were to add a design-beans.xml
and use that as a marker + list the classes we should load/configure as possible injection/navigation candidates in the tooling.
I was hoping this were settled before Seam 3 GA but it seem to fallen through the cracks ?
Something I missed ?
Now that the Seam final release has been out for about a week (and I've
had a chance to gather my wits), I've been thinking a bit about what we
should do with the seamframework.org web site. I think that we're all
in agreement that we need to do something, however the devil is in the
details - it's plain to me that we can't do a straight migration of all
content to the jboss.org community site and still retain all the value
that the current site provides.
Essentially, the contents of the site can be broken down into a few
4. Reference - links to documentation, downloads, Maven artifacts, etc
I believe that 1, 3 and 4 are the types of content that we can
successfully host on the jboss.org infrastructure (still accessible from
www.seamframework.org), in a similar way that hibernate.org does it.
What I don't believe that we can host there is the knowledgebase. I
think that this is one area where we're currently failing our community,
and that we have the potential to make vast improvements on.
This is where Seam University comes in. My vision for this is to build
a site that is run with the same collaborative community effort that has
exploded into existence as a result of Seam 3. This would be a site
where Seam users could submit their own articles, tutorials and tips for
using Seam, and have it properly indexed via a powerful keyword search
algorithm (this bit is quite important). I know we have in.relation.to,
but the problem with this site is a) only a select few can submit
content to it, b) new content falls off the radar quite quickly and c)
it's mainly centered around product announcements.
As for hosting this, my preference would be to use Google App Engine so
that the site could double up in purpose as being a showcase of CDI/Seam
technology in the cloud.
Anyway, these are my initial thoughts on this subject and I would really
love to hear some feedback on these ideas. So don't be shy to let me
know what you think. :)
Absolutely. Module leads, please feel empowered to promote either your
module or the Seam 3 release. You can coordinate on seam-dev if you are
worried about double submitting something.
The most updated "message" is Shane's announcement blog post and the
introductory section of the Seam 3 bundle reference guide.
On Mon, Apr 4, 2011 at 08:05, José Rodolfo Carrijo de Freitas <
> Hey guys,
> Is there a plan to make some noise at those tech news sites?
> seam-dev mailing list
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
I try to shorten my Expression language code and don't want to create delegate methods in my controller to access propertir of a business component.
I didn't found something like @Out. Does it exists ?