Module leads, can you please review the list of example applications
below and let me know if any of them should be added to the Seam bundled
-------- Original Message --------
Subject: [seam-issues] [JBoss JIRA] (SEAM-104) Consider adding missing
examples to the distribution
Date: Fri, 7 Oct 2011 08:17:16 -0400 (EDT)
From: Jozef Hartinger (Created) (JIRA) <jira-events(a)lists.jboss.org>
Consider adding missing examples to the distribution
Project: Seam 3 Distribution
Issue Type: Task
Affects Versions: 3.1.0.Beta3
Reporter: Jozef Hartinger
Assignee: Shane Bryzak
Fix For: 3.1.0.CR1
The following sample applications are developed as part of Seam modules but are not bundled within the Seam distribution.
Please, go over them and reevaluate if the should be included or not. (I am not saying they should be, I am just making sure we do not miss anything unintentionally :-) )
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
seam-issues mailing list
At the title of Weld documentation, there is a list of translations, but I
can not find out where to download the translated version . So my questions:
1 How and where to download the translated Weld documentation, such as
Simplified Chinese version?
2 If there is not a translated version, how can I involved in the
Thanks in advance!
- 3.1.0.Beta3 released (5 min)
- Remaining 3.1.0 Roadmap (10 min)
I'm falling short on other topics. Anyone else have anything they'd like to
add? Please blog, tweet, etc about Seam Hack Night coming up.
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
The 3.1.0.Beta3 release has been tagged, and the artifacts have been
released on the JBoss Nexus repository. There's still a few things to
do to complete the release:
1) Build and upload the distributions for all the modules and upload to
2) Upload new versions of all the docs to docs.jboss.org.
3) Finish updating the bundled distribution and release it to sourceforge.
4) Update release dates in JIRA
5) Post release announcement to in.relation.to
These remaining items will be completed tomorrow. I would like to thank
everyone for the hard work done on this release, it's great to see the
addition of a number of new modules and the progression of features and
quality improvement on the existing modules. I'm personally very
excited about the addition of the JCR and Social modules, I'm looking
forward to using them myself.
We are planning on a CR1 release on the 18th of October, followed
shortly after by the final release on the 28th October. I encourage
everyone to try out this new release (yes, it's actually a public
release this time) and let us know of any issues that you find.
I've been working diligently (whenever I have time) to get the seam JMS
module up and running on the new test suite format. One thing I've noticed
is that because of the caveats of using JMS In SE vs. EE, it didn't just
work to run weld ee embedded and within a container tests by themselves. It
also became clear that in general this wouldn't work outside of a container
because of differences in how to start open mq vs. hornetq vs. activemq.
Even working in a remote JNDI provider (similar to how weblogic JMS works)
it wouldn't have worked quite right.
Soemthing I started a while ago (maybe 4-5 weeks) was to separate various
impls to different modules. I want to go ahead and move forward with this
approach. This would provide the main api and impl (across all impls) as
well as a domain specific impl (e.g. seam-jms-ee-impl) that contains
functionality for EE environments. As a result, when running the test
suite, you are verifying the api, impl, the domain specific impl and the
test suite for that specific combination.
Does anyone have any concerns with this approach?