299 and nested conversations

[gonorrhea]

In the latest version of 299 spec (051809), I did not see any reference to keyword nest.

Are nested conversations not going to be part of 299 and somehow integrated with 299 (Web Beans) core in Seam 3?

[gavin.king]

A portable extension such as Seam is able to provide nested conversation support.

[luxspes]

And... are there plans fix them so that they stop being ill defined (specially for @PerNestedConversation components)?

Will it be finally possible to do call a component in a parent conversation from a component in a nested conversation?

Or plans for nested conversations are still too far in the future to discuss them now?

[nickarls]

Features can always be discussed. And since contexts and conversation managers are mostly pluggable you can throw in your own if you want features that aren't that useable for trunk.

[luxspes]

So.. that means that nested conversations might be as limited as they are now but it will be easier for me to improve nested conversations?

[luxspes]

Nicklas Karlsson wrote on May 19, 2009 22:05:


Features can always be discussed.

Silly me thinking that actually meant that some discussion was going to actually happen here. :'(

[gonorrhea]

Francisco Peredo wrote on May 27, 2009 18:19:

Nicklas Karlsson wrote on May 19, 2009 22:05:


Features can always be discussed.

Silly me thinking that actually meant that some discussion was going to actually happen here. :'(

Try participating in the JCP/JSR discussions (via email).  Why don't they have forums for JSR discussions?  what a joke Java is...

[nickarls]

Yes, I definitely think you should switch to RoR. Java is dead.

[nickarls]

Actually, didn't see that someone had written something here.

Well, Pete probably has the last word on what goes in but my guess would be

1. No nested conversations in the first release of Seam 3


2. A nested conversation manager will probably be provided at some point.


3. You should be able to plug in a nested conversation manager that does what you want (as long as WB allows for it)

[luxspes]

Nicklas Karlsson wrote on May 28, 2009 12:31:


Actually, didn't see that someone had written something here.

Well, Pete probably has the last word on what goes in but my guess would be

No nested conversations in the first release of Seam 3

Hopefully, after many headaches, I avoided them, but what about those that didn't?

A nested conversation manager will probably be provided at some point.

You should be able to plug in a nested conversation manager that does what you want (as long as WB allows for it)

Do you think there will be any impediments for me to alter nested conversations behavior to work like this without patching Seam code?

Do you think it will be possible to create a custom conversation manager that replaces the default as proposed here and be able to create my own ScopeType.TEMP_CONVERSATION or create a custom NavigationManager  as proposed by Tim Evers but without the need to patch Seam code?

[nickarls]

Again, my guess would be those will be pluggable