You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "gengshaoguang (JIRA)" <tu...@ws.apache.org> on 2007/10/22 07:55:50 UTC
[jira] Created: (TUSCANY-1861) Improve binding.ws over jms global
transaction aware
Improve binding.ws over jms global transaction aware
----------------------------------------------------
Key: TUSCANY-1861
URL: https://issues.apache.org/jira/browse/TUSCANY-1861
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Axis Binding Extension
Affects Versions: Java-SCA-Next
Environment: jdk1.6 svn trunk
Reporter: gengshaoguang
Hello every one:
I make this proposal to improve one step closer to sca1.0 global transaction support.
Currently, Tuscany's distributed reference work over jms is provided by axis2's jms feature. But unfortunately, axis2 doesn't provide a feature of transactional ws invoke.
So we must do something here.
Detail:
1.replace <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener"> inside axis2.xml with an new one, like shown in the diagram.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1861) Improve binding.ws over jms global
transaction aware
Posted by "gengshaoguang (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gengshaoguang updated TUSCANY-1861:
-----------------------------------
Attachment: TM-Related-Object.png
JCAReceiver or JCAMessageListener is responsible for host instance of transactional object.
As shown in the diagram, a ResourceAdapter is the key to make soap over jms manageable under a global transaction. ResourceAdapter needs other object to complete a TM lifecycle.
> Improve binding.ws over jms global transaction aware
> ----------------------------------------------------
>
> Key: TUSCANY-1861
> URL: https://issues.apache.org/jira/browse/TUSCANY-1861
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-Next
> Environment: jdk1.6 svn trunk
> Reporter: gengshaoguang
> Attachments: axis2-substitute.png, TM-Related-Object.png
>
>
> Hello every one:
> I make this proposal to improve one step closer to sca1.0 global transaction support.
> Currently, Tuscany's distributed reference work over jms is provided by axis2's jms feature. But unfortunately, axis2 doesn't provide a feature of transactional ws invoke.
> So we must do something here.
> Detail:
> 1.replace <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener"> inside axis2.xml with an new one, like shown in the diagram.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1861) Improve binding.ws over jms global
transaction aware
Posted by "gengshaoguang (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gengshaoguang updated TUSCANY-1861:
-----------------------------------
Attachment: TM-secquence-in-axis2.png
This diagram shows the invoke/relay secquence of a soap over jca.
When any exception occurs, the JCAMessageListener just use TransactionManager.setRollbackOnly.
> Improve binding.ws over jms global transaction aware
> ----------------------------------------------------
>
> Key: TUSCANY-1861
> URL: https://issues.apache.org/jira/browse/TUSCANY-1861
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-Next
> Environment: jdk1.6 svn trunk
> Reporter: gengshaoguang
> Attachments: axis2-substitute.png, TM-Related-Object.png, TM-secquence-in-axis2.png
>
>
> Hello every one:
> I make this proposal to improve one step closer to sca1.0 global transaction support.
> Currently, Tuscany's distributed reference work over jms is provided by axis2's jms feature. But unfortunately, axis2 doesn't provide a feature of transactional ws invoke.
> So we must do something here.
> Detail:
> 1.replace <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener"> inside axis2.xml with an new one, like shown in the diagram.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-1861) Improve binding.ws over jms global
transaction aware
Posted by "gengshaoguang (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gengshaoguang updated TUSCANY-1861:
-----------------------------------
Attachment: axis2-substitute.png
Currently, axis2 has a declared TransportListener handling soap message over jms, this listener has multiple JMSConnectionFactory associated. Each of them deal with a concrete MessageListener to handle the inward message with void onMessage(Message msg).
What we will have to do is first subclass the above JMSListener and override its start method.
Then, implement another MessageListener, to replace the JMSMessageReceiver, and use JCA instead of direct consumer in its onMessage(*).
> Improve binding.ws over jms global transaction aware
> ----------------------------------------------------
>
> Key: TUSCANY-1861
> URL: https://issues.apache.org/jira/browse/TUSCANY-1861
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-Next
> Environment: jdk1.6 svn trunk
> Reporter: gengshaoguang
> Attachments: axis2-substitute.png
>
>
> Hello every one:
> I make this proposal to improve one step closer to sca1.0 global transaction support.
> Currently, Tuscany's distributed reference work over jms is provided by axis2's jms feature. But unfortunately, axis2 doesn't provide a feature of transactional ws invoke.
> So we must do something here.
> Detail:
> 1.replace <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener"> inside axis2.xml with an new one, like shown in the diagram.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Resolved: (TUSCANY-1861) Improve binding.ws over jms global
transaction aware
Posted by "Raymond Feng (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raymond Feng resolved TUSCANY-1861.
-----------------------------------
Resolution: Won't Fix
The patch is for the documents. I'll load them into the wiki instead.
> Improve binding.ws over jms global transaction aware
> ----------------------------------------------------
>
> Key: TUSCANY-1861
> URL: https://issues.apache.org/jira/browse/TUSCANY-1861
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-Next
> Environment: jdk1.6 svn trunk
> Reporter: gengshaoguang
> Fix For: Java-SCA-Next
>
> Attachments: axis2-substitute.png, TM-Related-Object.png, TM-secquence-in-axis2.png
>
>
> Hello every one:
> I make this proposal to improve one step closer to sca1.0 global transaction support.
> Currently, Tuscany's distributed reference work over jms is provided by axis2's jms feature. But unfortunately, axis2 doesn't provide a feature of transactional ws invoke.
> So we must do something here.
> Detail:
> 1.replace <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener"> inside axis2.xml with an new one, like shown in the diagram.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org