[JBoss Seam] - Re: Nested conversations and transaction management
by FabBoco
Christian,
tank you very much for your answers. Now everything is clearer.
Since every call to a SFSB method is performed into a different database transaction, my final question is how can I manage transactions so that two or more SFSB methods are executed into the same transaction ?
What I am trying to do is very simple:
1) I start an input form for the Entity Bean A
2) From the input form I open a pop up window in which I can choose items from EB B or I can create new items
3) When I close the pop up the A form is update (so that the back entity bean)
4) If I cancel the operation I would like that the B items would not be saved to the database
I though that a long-running conversation would be the solution. It is not.
Now, I still think that I have to execute A and B methods into a single (user) transaction but where I can open and commit it ?
Any other solution that doesn't involve an explicit transaction management ?
Regards
Fab.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042362#4042362
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042362
17 years, 2 months
[JBoss Seam] - Re: Mathematical captcha & Email obfuscator
by petemuir
"Homer J." wrote : What do you mean with explicit & implicit attributes? Is it bad that the email tags are derived from the obfuscator tags?
The spec suggests
anonymous wrote : The render-independent characteristics of a user interface component are represented as JavaBean component properties, following JavaBeans naming conventions . Specifically, the method names of the getter and/or setter methods are determined using standard JavaBeans component introspection rules,
- i.e. attributes should have getters and setters (this is a convention we follow with other JSF components in Seam). It's fine to back the getters and setters with the attributes map if you like.
anonymous wrote : Regarding the EL: if you do something like:
| <s:email value="#{user.email}" /> it will work so I'm not sure what you mean.
Sorry, you are right, I'm not familiar with the attribute map - it's cleverer than I thought!
anonymous wrote : Regarding nested tag support: while I theoretically agree with you there is not much point in it because now both tags are derived from HtmlOutputText
I think the email one needs to be based conceptually on h:outputLink, which does allow nested text
anonymous wrote : and therefore behave in a similar way. E.g.:
|
| So everything in the body is rendered before the tags - which can be done by simply writing it before the tag too.
Yes, you are right. This is broken imo ;) - might be worth "fixing" it...
anonymous wrote : Last but not least you said that the default behavior of the email tag should be to do no obfuscation.
Up to you :) - that was my initial reaction, but I really don't have strong feelings!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042354#4042354
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042354
17 years, 2 months