[JBoss JIRA] (JBTM-1470) hudson build script copies over the wrong integration jar
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1470?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-1470:
----------------------------------------
This feature is no longer required so I will resolve it by removing the option to conditionally build the AS (ie I will remove the env variable AS_BUILD)
> hudson build script copies over the wrong integration jar
> ---------------------------------------------------------
>
> Key: JBTM-1470
> URL: https://issues.jboss.org/browse/JBTM-1470
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 5.0.0.M2
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M2
>
>
> The JIRA is low priority because it does not effect CI builds.
> scripts/hudson/narayana.sh has a variable called BUILD_AS. If this is set to zero then the AS will not be built but after a narayana build the script will copy over the final jts jars to the AS modules folder (provided the AS directory is present) - this feature is useful for developer testing to avoid a full rebuild of the AS). There are 2 bugs:
> - the name is still referring to the old jbossjts.XXX.jar name
> - the jars should only be copied if BUILD_AS is set to zero
> Note that other subsystem jars generated by a narayana build (such as xts) are not copied over.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1470) hudson build script copies over the wrong integration jar
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-1470:
--------------------------------------
Summary: hudson build script copies over the wrong integration jar
Key: JBTM-1470
URL: https://issues.jboss.org/browse/JBTM-1470
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build System
Affects Versions: 5.0.0.M2
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Minor
Fix For: 5.0.0.M2
The JIRA is low priority because it does not effect CI builds.
scripts/hudson/narayana.sh has a variable called BUILD_AS. If this is set to zero then the AS will not be built but after a narayana build the script will copy over the final jts jars to the AS modules folder (provided the AS directory is present) - this feature is useful for developer testing to avoid a full rebuild of the AS). There are 2 bugs:
- the name is still referring to the old jbossjts.XXX.jar name
- the jars should only be copied if BUILD_AS is set to zero
Note that other subsystem jars generated by a narayana build (such as xts) are not copied over.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1467) Create a set of Koans for using Compensations
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1467?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1467:
--------------------------------
Description:
In the spirit of http://rubykoans.com/, but to learn how to use compensations.
In the long term we should use a Java EE Koan 'runner'. In the short term, try using Arquillian with some broken tests. We could do something to intercept logs for an appropriate error message to present the user.
Might also be worth having Arquillian stop on a failed test to prevent too many failures swamping the user.
was:
In the spirit of http://rubykoans.com/, but to learn how to use compensations.
In the long term we should use a Java EE Koan 'runner'. In the short term, try using Arquillian with some broken tests.
> Create a set of Koans for using Compensations
> ---------------------------------------------
>
> Key: JBTM-1467
> URL: https://issues.jboss.org/browse/JBTM-1467
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: TXFramework, XTS
> Reporter: Paul Robinson
>
> In the spirit of http://rubykoans.com/, but to learn how to use compensations.
> In the long term we should use a Java EE Koan 'runner'. In the short term, try using Arquillian with some broken tests. We could do something to intercept logs for an appropriate error message to present the user.
> Might also be worth having Arquillian stop on a failed test to prevent too many failures swamping the user.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1469) Move TXBridge quickstart into JDF
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1469:
-----------------------------------
Summary: Move TXBridge quickstart into JDF
Key: JBTM-1469
URL: https://issues.jboss.org/browse/JBTM-1469
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: TxBridge, XTS
Reporter: Paul Robinson
TXBridge is now supported, so we can move one or more of the quickstarts across to JDF. We should first run this by Pete and get a JDF Jira created, then link this one through.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1446) Prepare Quickstarts for Release
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1446?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1446:
--------------------------------
Original Estimate: 2 days (was: 1 day)
Remaining Estimate: 2 days (was: 1 day)
> Prepare Quickstarts for Release
> -------------------------------
>
> Key: JBTM-1446
> URL: https://issues.jboss.org/browse/JBTM-1446
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> * The tag should reference the latest release, rather than a snapshot
> * Check the TXFramework/readme.md to make sure it is current and to remove the link to the old pre-built AS7+TS.
> * General check over looking for things that won't work with a tagged/released AS7+Narayana.
> * Move quickstarts into XTS, REST or TXBridge.
> * Rename existing QS as raw or remove if no longer applicable.
> * Upgrade the TXBridge one to use TXF and move into XTS?
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1446) Prepare Quickstarts for Release
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1446?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1446:
--------------------------------
Description:
* The tag should reference the latest release, rather than a snapshot
* Check the TXFramework/readme.md to make sure it is current and to remove the link to the old pre-built AS7+TS.
* General check over looking for things that won't work with a tagged/released AS7+Narayana.
* Move quickstarts into XTS, REST or TXBridge.
* Rename existing QS as raw or remove if no longer applicable.
* Upgrade the TXBridge one to use TXF and move into XTS?
was:
* The tag should reference the latest release, rather than a snapshot
* Check the TXFramework/readme.md to make sure it is current and to remove the link to the old pre-built AS7+TS.
* General check over looking for things that won't work with a tagged/released AS7+Narayana.
> Prepare Quickstarts for Release
> -------------------------------
>
> Key: JBTM-1446
> URL: https://issues.jboss.org/browse/JBTM-1446
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> * The tag should reference the latest release, rather than a snapshot
> * Check the TXFramework/readme.md to make sure it is current and to remove the link to the old pre-built AS7+TS.
> * General check over looking for things that won't work with a tagged/released AS7+Narayana.
> * Move quickstarts into XTS, REST or TXBridge.
> * Rename existing QS as raw or remove if no longer applicable.
> * Upgrade the TXBridge one to use TXF and move into XTS?
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1391) Prepare a blog post to introduce the TXFramework
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1391?page=com.atlassian.jira.plugin.... ]
Paul Robinson edited comment on JBTM-1391 at 2/14/13 10:01 AM:
---------------------------------------------------------------
Outstanding issues:
* Clarify @DataManagement and maybe pull this out into a separate blog post.
* Remove refrence to TXFramework, instead positioning it as API improvements to other technologies, allowing those technologies take centre stage.
* Consider pulling out the details into separate posts and make this an overview. Difficult to have an overview of TXF without showing code as it sounds kind of abstract.
* Comment that JTA will be pure JTA soon. Only use bridge example.
was (Author: paul.robinson):
Outstanding issues:
* Clarify @DataManagement and maybe pull this out into a separate blog post.
* Consider playing down TXFramework, instead positioning it as API improvements to other technologies, allowing those technologies take centre stage.
* Consider pulling out the details into separate posts and make this an overview. Difficult to have an overview of TXF without showing code as it sounds kind of abstract.
> Prepare a blog post to introduce the TXFramework
> ------------------------------------------------
>
> Key: JBTM-1391
> URL: https://issues.jboss.org/browse/JBTM-1391
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Documentation, TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 4 hours, 40 minutes
> Remaining Estimate: 1 day, 4 hours
>
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-400) JTA for Compensations
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-400?page=com.atlassian.jira.plugin.s... ]
Paul Robinson updated JBTM-400:
-------------------------------
Description:
We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
was:Needs serious discussions within the team.
> JTA for Compensations
> ---------------------
>
> Key: JBTM-400
> URL: https://issues.jboss.org/browse/JBTM-400
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Transaction Core, XTS
> Reporter: Mark Little
>
> We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
> It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1468) Support pure-JTA client and server for WS-AT and REST-AT
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1468:
-----------------------------------
Summary: Support pure-JTA client and server for WS-AT and REST-AT
Key: JBTM-1468
URL: https://issues.jboss.org/browse/JBTM-1468
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
This allows the Client and server application to just use the JTA APIs, whilst having the distribution done over WS-AT or REST-AT.
To do this we need to:
# Remove @Transactional annotation. We then need to use some other mechanism to support the (optional) WS-AT participants that want to use annotations.
# Client side JTA->REST-AT bridge. Needs implementing.
# Server side REST-AT->JTA bridge. Needs integrating into code base.
# Update the TXBridge quickstarts to use this and move them out.
--
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
13 years, 1 month