I am working on a system that needs to update a web service (WS) and a database (DB) within a single transaction. Since the WS is non transactional, I make an update to the DB first, then make a call to the WS; if the WS succeeds the DB update is committed (DBC).
Details:
Client makes a call to a stateless session bean. The ssb uses container managed transactions.
The session bean updates an entity bean.
The session bean then makes a call to the web service.
This approach works well except in the following scenario: If there is a network problem during DBC the WS and DB get out of sync.
Does anyone know if it is possible to configure JBoss to continue to retry the DBC in the event of a network problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033421#4033421
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033421
I am working on a system that needs to update a web service (WS) and a database (DB) within a single transaction. Since the WS is non transactional, I make an update to the DB first, then make a call to the WS; if the WS succeeds the DB update is committed (DBC).
Details:
Client makes a call to a stateless session bean. The ssb uses container managed transactions.
The session bean updates an entity bean.
The session bean then makes a call to the web service.
This approach works well except in the following scenario: If there is a network problem during DBC the WS and DB get out of sync.
Does anyone know if it is possible to configure JBoss to continue to retry the DBC in the event of a network problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033420#4033420
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033420
thanks fernando, got it now - (a single row that is :)
I did not know that Set could not be used: I had read this in the seam documentation:
| @DataModel
|
| @DataModel("variableName")
|
| Exposes an attribute of type List, Map, Set or Object[] as a JSF DataModel into the scope of the owning component (or the EVENT scope if the owning component is STATELESS). In the case of Map, each row of the DataModel is a Map.Entry.
|
| . . .
|
| | And infered (wrongly) that Set was also supported directly.
| |
| | So, it should probably work if I obtain the Set from the parent bean (where I 'out' it) and 'out' the detail Set as a DataModel using Seam Annotation.
| |
| | Am I on the right track?
| |
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033414#4033414
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033414