From line 0 added to lines 0 to 1:
<div style="color: rgb(255,0,0); font-weight: bold;">This page is deprecated. Please refer to the the [Seam 3 project page=>wiki://121356] for a complete list of modules.</div>
From lines 3 to 4 changed to lines 5 to 6:
From line 6 changed to line 8:
=[XML Bean Config=>wiki://122707]
From lines 11 to 12 changed to lines 13 to 14:
=[Transactions and Persistence=>wiki://74847#TXAndPersistenceLeadNeeded]
=[Transactions and Persistence=>wiki://124426]
From line 15 changed to line 17:
From line 68 changed to line 70:
TODO what does Seam add?
TODO what does Seam add?
From lines 70 to 95 deleted to line 72:
+++ Faces (led by Lincoln Baxter and Dan Allen)
Seam's JSF support offers a number of enhancements for using CDI with JSF. It may be that we are prototyping new ideas for the JSF and CDI specifications, or it may be that we are providing JSF support for other Seam modules.
Included in this package is the ability to interoperate with Seam's i18n support, debugging output for JSF, context implementations for JSF's flash scope (|@FlashScoped|) and view scope (|@ViewScoped|) (and look into Window scope, see [Edoras scopes=>http://www.edorasframework.org/web/fw/scopes]), |@Inject| into JSF system event listeners, converters and validators, support for nested conversations, view metadata components such as viewAction and restrictView, etc.
Any rendering UIComponent should be introduced into RichFaces rather than Seam, a change in policy from Seam 2. The Seam project doesn't want to be in the business of maintaining a component library since we already have a whole team for that work.
Further, this module contains "Seam Managed Transactions".
For more information on the Faces module concepts, managed transactions, and nested conversations, view the:
= [Design Notes=>wiki://119602]
+++ il8n/l10n (led by Lincoln Baxter and Ken Finnigan)
Internationalization is very important for those of us who develop applications for non-English speakers, but is unfortunately poorly supported in various places in Java. It certainly isn't seamless to configure.
Seam aims to provide a unified approach to configuring your application for the right locale, propagating the locale to all aspects of the application.
+++ XML (led by Stuart Douglas)
Implement the typesafe XML-based configuration format that was defined in earlier revisions of the specification.
From line 114 deleted to line 90:
From line 126 deleted to line 101:
From lines 141 to 150 deleted to line 115:
+++ Servlet support (led by Nicklas Karlsson and Lincoln Baxter)
Provide utilities and functionality to complement the Servlet API such as injection Request, Response and Session artifacts.
+++ TX and persistence (lead needed)
The Seam 3 Transaction and Persistence Module will enable persistence context injection as well as transactional methods outside of a Java EE container. This will bring features regularly handled by Java EE containers to your CDI application running on Java SE or servlet containers, like Tomcat or Jetty.
From lines 168 to 188 deleted to line 132:
+++ JMS (led by Jordan Ganoff with Dan Allen)
Seam extends the CDI programming model into the messaging world by allowing you to inject JMS resources into your beans. Further, Seam bridges the CDI event bus over JMS; this gives you the benefits of CDI-style type-safety for inter-application communication.
The general goals can be divided into two categories: injection of JMS resources and forwarding of events.
++++ Injection of JMS Resources
= Destination (Topic/Queue)
= Message Producer
= Message Consumer
++++ Forwarding of Events
= Implicit - use a stereotype annotation when firing events
= Explicit - events and qualifiers are registered explicitly
For a preview implementation check out our temporary git repository at GitHub: [http://github.com/jganoff/seam3-jms=>http://github.com/jganoff/seam3-jms]