[JBoss JIRA] (JBTM-948) Provide test coverage for WS-AT/XA Bridge Demo Application
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-948?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson closed JBTM-948.
------------------------------
> Provide test coverage for WS-AT/XA Bridge Demo Application
> ----------------------------------------------------------
>
> Key: JBTM-948
> URL: https://issues.jboss.org/browse/JBTM-948
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, Testing, TxBridge
> Affects Versions: 4.15.3
> Reporter: Ivo Studensky
> Assignee: Paul Robinson
> Fix For: 4.16.0.Final
>
>
> The WS_AT/XA bridge demo application which is shipped with JBossTS project at the moment should be shipped with EAP6 too. For this it needs a test coverage. Hence provide a reasonable set of tests for it. The tests should be placed to JBossTS project and it is allowed them to be maven based.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBTM-933) Compress the EIS name in the bqual
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-933?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson closed JBTM-933.
------------------------------
> Compress the EIS name in the bqual
> ----------------------------------
>
> Key: JBTM-933
> URL: https://issues.jboss.org/browse/JBTM-933
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 4.16.0.Beta1
>
>
> Current most of the bqual is consumed by the EIS name (stored uncompressed) leaving little space for future enhancements. This was OK before, but there is potentially a requirement to use some of the bqual to store a node identifier (which, in the gtrid is able to be 36 bytes long).
> Jonathan has pointed out that we can maintain a file somewhere where the user passes us an EIS name of say "foo" and we can add this to the file as integer 1, and so on. This file can be reloaded at startup into a hashmap so that we can still print out the real EIS name even though the XID bqual would only consume 4 bytes now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBTM-1062) JBossTS source jars are empty
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1062?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-1062.
-------------------------------
> JBossTS source jars are empty
> -----------------------------
>
> Key: JBTM-1062
> URL: https://issues.jboss.org/browse/JBTM-1062
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.16.2
> Reporter: Martha Benitez
> Assignee: Tom Jenkinson
> Fix For: 4.16.3
>
>
> The following sources jar files are empty:
> org/jboss/jbossts/jbossjts-integration/4.16.2.Final-redhat-1/jbossjts-integration-4.16.2.Final-redhat-1-sources.jar
> org/jboss/jbossts/jbossxts-api/4.16.2.Final-redhat-1/jbossxts-api-4.16.2.Final-redhat-1-sources.jar
> org/jboss/jbossts/jbossxts/4.16.2.Final-redhat-1/jbossxts-4.16.2.Final-redhat-1-sources.jar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months