-
1. Re: Breaking change
gavin.king Dec 29, 2005 9:05 AM (in response to gavin.king)By the way, I am following a policy of choosing very conservative default behaviors, hence, @In defaults to (required=true, create=false) and @Begin defaults to (join=false).
The idea here is that Seam applications will fail early, with meaningful messages and so be that much easier to debug. -
2. Re: Breaking change
drapierwim Jan 3, 2006 6:15 PM (in response to gavin.king)As a result of my http://www.jboss.com/index.html?module=bb&op=viewtopic&t=74806
earlier post I didn't know we could make suggestions for the join() name.
First the join confused me of thinking that it can be 'joined' with else...(silly me)
so I'm thinking of
reuseConversation ... maybe to long but direct to the point
reuse ... probally to abstract(you could ask yourself reuse what?)
same(Conversation) ... I don't know
unique(Conversation)
single... prrf
maybe previous is more like it for me
@Begin(unique=true) reads like 'Begin an unique conversation'
Took me some time for thinking an posting this, so don't shoot me if it's a silly answer -
3. Re: Breaking change
gavin.king Jan 3, 2006 6:25 PM (in response to gavin.king)It is more a question of propagation, than of "reuse".
And I don't think "unique" really captures it :)
It's actually analogous to Transaction Required.