[JBoss JIRA] Created: (JBTM-803) The WSDLs of the WS-C services are present both in ws-c11.jar e wstx.jar
by Mauro Molinari (JIRA)
The WSDLs of the WS-C services are present both in ws-c11.jar e wstx.jar
------------------------------------------------------------------------
Key: JBTM-803
URL: https://jira.jboss.org/browse/JBTM-803
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 4.13.0
Reporter: Mauro Molinari
Priority: Minor
The WSDLs of the WS-C services (wsat-coordinator-binding and wscoor-activation-binding) are located in two places, in ws-c11.jar but also in wstx.jar.
They have been put in the ws-c11 jar so the coordinator service classes (also in this jar) can find them. But also in wstx11.jar so the client classes (also in wstx11.jar) can find them.
However, since all the XTS JARs at the moment are needed on each part of the system (Client, Coordinator, Participant), it's useless (and confusing) to have these WSDLs in both places.
I personally suggest to keep the ones in ws-c11.jar, so that they are easily recognizable as the counterparts of the WS-T services WSDLs in ws-t11.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBTM-799) Provide a way to configure the WS-C and WS-T service endpoint URLs/paths
by Mauro Molinari (JIRA)
Provide a way to configure the WS-C and WS-T service endpoint URLs/paths
------------------------------------------------------------------------
Key: JBTM-799
URL: https://jira.jboss.org/browse/JBTM-799
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 4.13.0
Reporter: Mauro Molinari
As of now, the paths to get to the exposed service endpoints of the different WS-C and WS-T services is hard coded, based on the JBossAS/JBossWS convention of using the path <war-name>/<service-name> (where <war-name> is the name of the war containing the service). For instance, the ActivationService URL is expected to be http://bindAddress:bindPort/ws-c11/ActivationService.
However, if you want to deploy to another environment (for instance: your own web application, running on Tomcat with CXF), you may want (or you may even be forced) to change the endpoint URLs as you like.
Since with CXF (and, in general, with JAX-WS) you are free to expose a webservice with the URL you prefer, the best would be to make XTS configurable in this sense.
Every component (Client, Participant, Coordinator) should be improved to let the user specify the URL at which he wants to expose the corresponding webservices (i.e.: for WS-AT, it's the CompletionInitiator on the Client, the Participant on the Participant, the Coordinator, CompletionCoordinator, Activation and Registration on the Coordinator). More precisely, since the bindAddress and bindPort are already settable, just the path part should be made configurable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBTM-800) Recovery manager not initialised when deploying just the Coordinator
by Mauro Molinari (JIRA)
Recovery manager not initialised when deploying just the Coordinator
--------------------------------------------------------------------
Key: JBTM-800
URL: https://jira.jboss.org/browse/JBTM-800
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 4.13.0
Reporter: Mauro Molinari
If you deploy just the Coordinator component of XTS and you follow the configuration guidelines, you may be providing just the following recovery manager configuration entries in xts-properties.xml:
<entry key="org.jboss.jbossts.xts.recovery.coordinatorRecoveryModule1">org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule</entry>
<entry key="org.jboss.jbossts.xts.recovery.coordinatorRecoveryModule2">org.jboss.jbossts.xts.recovery.coordinator.at.SubordinateATCoordinatorRecoveryModule</entry>
However, in this way, after the Coordinator has started, you get the following NullPointerException:
Exception in thread "Periodic Recovery" java.lang.NullPointerException
at org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule.processTransactionsStatus(ATCoordinatorRecoveryModule.java:280)
at org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule.periodicWorkSecondPass(ATCoordinatorRecoveryModule.java:121)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371)
This is because the recovery manager is currently initialized by the ATParticipantRecoveryModule, which is expected to be made available just on the Participant component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBTM-798) Package the XTS service and initialisation classes in a JAR, rather than in the SAR
by Mauro Molinari (JIRA)
Package the XTS service and initialisation classes in a JAR, rather than in the SAR
-----------------------------------------------------------------------------------
Key: JBTM-798
URL: https://jira.jboss.org/browse/JBTM-798
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 4.13.0
Reporter: Mauro Molinari
As of now, the binary distribution of XTS provides the following classes in jbossxts.sar:
org.jboss.jbossts.XTSService
org.jboss.jbossts.XTSServiceMBean
org.jboss.jbossts.initialisation.*
org.jboss.jbossts.logging.*
As discussed in the forum, in order to make XTS easily deployable outside JBossAS it would be convenient to move these classes into one of the already existing JARs (jbossxts-api.jar?) or in a new one (jbossxts-service.jar?). Then, this JAR should be included in the SAR, if it's not already.
In this way, the SAR would become just a facility to deploy XTS in JBossAS, but the user could deploy it also on another application server (Tomcat for instance) just by deploying the XTS JARs and providing the necessary configuration wiring.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBTM-797) orb setup drops exceptions
by Jonathan Halliday (JIRA)
orb setup drops exceptions
--------------------------
Key: JBTM-797
URL: https://jira.jboss.org/browse/JBTM-797
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Recovery
Affects Versions: 4.13.0
Reporter: Jonathan Halliday
Assignee: Jonathan Halliday
Fix For: 4.14.0
When the specified orb (actually OA) port is in use the orb setup will fail, leave the orb/oa in an unusable state, print a warning but not be detectable or recoverable programatically. This sucks for the test suite, since it's not uncommon for rec mgr startup to fail due to the O/S not having recycled ports from a previous test process. This situation should be detectable and retryable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Commented: (JBTM-77) Make UserTransaction Serializable/Referenceable
by Misty Stanley-Jones (JIRA)
[ https://jira.jboss.org/browse/JBTM-77?page=com.atlassian.jira.plugin.syst... ]
Misty Stanley-Jones commented on JBTM-77:
-----------------------------------------
Release Note:
Cause: <classname>UserTransaction</classname> was not serializable or referencable.
Consequence: <classname>UserTransaction</classname> did not align with the JTA specifications.
Fix: <classname>UserTransaction</classname> is now serializable and referencable.
Resolution: <classname>UserTransaction</classname> now complies with the JTA.
> Make UserTransaction Serializable/Referenceable
> -----------------------------------------------
>
> Key: JBTM-77
> URL: https://jira.jboss.org/browse/JBTM-77
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Affects Versions: 4.2
> Reporter: Mark Little
> Assignee: Jonathan Halliday
> Priority: Minor
> Fix For: 4.14.0
>
>
> JTA says we should be. Doesn't affect embedding in AS, but for strict compliane we should update the implementation.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months