Ah, the incredibly messy JSR-299 issue... About everything about it is done badly. JSF 2.0 is going to depend on it to support some of the annotation and conversation scope. While JSR-299 activates conversation only when JSF is present, lovely circular dependency isn't it? Most of the times I close my eyes and try to convince myself that JSR-299 does not exist or was done correctly earlier in Java life so that the various dependencies and separation of concerns could be correct. Like conversation scope should have been a custom scope implemented by JSF, this would have resulted in 2 advantages, correct dependency structure, and out-of-the-box conversation support in JSF.
Anyway, a parameter switch sounds like a good idea. ~ Simon On Wed, Aug 5, 2009 at 5:18 AM, Matthias Wessendorf <[email protected]>wrote: > my friend Mark Struberg pointed me to this interesting thread: > => http://markmail.org/thread/ml6l26r7twgab53c > > > -Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf >
