-
-
2. Re: Flex and Weld integration
Where can I see a current list of all the
things
that will be addressed in Seam3? -
3. Re: Flex and Weld integration
In everyone who uses Seam's brains? Seriously, it changes all the time, as we see new ideas we like. You should start a list, collecting all the things you hear.
-
4. Re: Flex and Weld integration
Just for information, there is a (very) early Weld integration with Flex in GraniteDS 2.1 RC1.
It's obviously not finished, but we already have a relatively complete example application.
Here what's available :
- Call a named Weld bean from Flex
- Support for conversations (same client side API as the Seam integration)
- Observe Weld events from Flex
- Remote data validation using JSR-303
- All other 'generic' stuff from GraniteDS inherited from the EJB3 and Seam integrations : data paging, Flex-side support for JPA detached entities, asynchronous data push...
All this works with JBoss 5.2 and GlassFish V3 (since build 70).
We have not yet grasped everything what could be done for a Flex / JCDI integration, but we'll try to get something solid for our final 2.1 due early january. Don't hesitate to propose your suggestions if you are interested. We really feel that Flex + JEE6 can be an extremely powerful combination to build complex RIA.
As a side note, the SPI does not contain anything to setup/close a conversation context so this part will work only with Weld for now.
See more details here.
-
5. Re: Flex and Weld integration
As a side note, the SPI does not contain anything to setup/close a conversation context so this part will work only with Weld for now.Yes, this is a known issue. We decided not to do it in 1.0, even though we knew it was going to be a problem for folks like you.
You could package your own implementation of the scope @ConversationScoped (you can steal Weld's, probably). But yeah, the EG is well aware that this is not ideal.
-