I'm pleased to announce the availability of our first Seam 3 module, Seam Remoting 3.0.0.Beta1. This release provides a CDI-based port of most of the AJAX remoting features that you know from Seam 2.x, and also introduces a new feature, the Model API. Please refer to the following links for downloads and documentation, and if you encounter any issues please use the issue tracking link to let us know about them. (Seam Remoting now has its own project in JIRA).
Also, stay tuned for a release of the Seam XML module in the next day, which will allow you to configure your CDI beans via an XML configuration file.
Created: 16. Mar 2010, 11:20 CET (Shane Bryzak)
Last Modified: 24. Mar 2010, 11:57 CET (Dan Allen)
Cool, congrats on the release!
Do you think it would be an option to JSF2/Servlet3:ify the usage with autoregistering servlets (and perhaps resourcehandlers, dunno)?
I was trying to keep dependencies to a minimum (I'd require the JSF libs to support this right?), also it might be an issue that there are two remoting servlets - one (portable) for containers that support servlet injection, and the other (non-portable) where the container doesn't support it.
So will Remoting 3.0 be included in a Seam 3.0-M1 release? I'm imagine that the new Seam core, integrating Weld and including backwards-compatability with Seam 2.x apps, will be required for M1 release....
Awesome!
Good to see that Seam 3 is finally !
Congrats and keep up the good job!
James
Good idea. We are targeting Java EE 6 after all. => JIRA
Congratulations on the release!
Shane, is it possible the useage of Seam Remoting 3.0.0.Beta1 with the latest release of Weld without waiting for a milestone release of Seam 3 ?
I'm sure the answer to this is no. Seam is an extension of Weld via the portable extensions and SPI. Seam Remoting is not in the CDI spec (JSR299) and thus should not be implemented in Weld...
If I understand correctly you're asking if you can use Seam Remoting 3 now without waiting for the full Seam 3 release. The answer is yes - each of the new Seam 3 modules is designed to work independently of the others, at least for their core functionality.
Hello,
@Arbi
I know that Seam Remoting is not in the CDI spec and, thus, it is not supported in Weld. However, I know also that Seam 3 could work on top of Weld (or another CDI implementation). So my question was more like: “Is it possible to use each module (when it is available) independently of the others as Weld extension?”
@Shane
I think you have understood me right. My concerns were that Seam 3 distribution will contain some common packages/classes (in seam3-core.jar or something) to all modules that will ensure the possibility of using Seam 3 modules as Weld extensions. As I understand from your answer it is not the case and each module can be used at the time it is ready.
Excuse me if my question was not appropriate from technical point of view but I am not familiar with the internals of the technologies.
Thank you for your answers!
Exactly, and the answer is that definitely expect you to be able to use a module in isolation.
No, it's a great question, and something we definitely need to make clear!
Seam modules can be used in isolation, as we release each one!