[JBoss JIRA] (JBTM-1974) Qa tests needs the narayana build being done with parameter idlj-enabled to work
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1974?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1974:
--------------------------------
Issue Type: Task (was: Feature Request)
> Qa tests needs the narayana build being done with parameter idlj-enabled to work
> --------------------------------------------------------------------------------
>
> Key: JBTM-1974
> URL: https://issues.jboss.org/browse/JBTM-1974
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.0.0.M5
> Reporter: Ondra Chaloupka
> Priority: Minor
>
> When qa tests should be built without compilation errors the prior narayana build has to be run with parameter -Didlj-enabled=true
> In the way like
> ./build.sh clean install -Prelease -DskipTests -Didlj-enabled=true
> This fact should be at least documented in REAME.
> Plus it would be nice to avoid this dependence (or put idlj-enabled parameter which activates a profile as default).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (JBTM-1789) Simplify deploy plugin configuration and don't deploy uber (shaded) jars
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1789?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1789:
--------------------------------
Issue Type: Task (was: Feature Request)
> Simplify deploy plugin configuration and don't deploy uber (shaded) jars
> ------------------------------------------------------------------------
>
> Key: JBTM-1789
> URL: https://issues.jboss.org/browse/JBTM-1789
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Build System
> Reporter: Paul Gier
> Assignee: Tom Jenkinson
> Fix For: 6.later
>
>
> There is currently configuration of the maven deploy plugin in several modules to either deploy or not deploy artifacts and poms to the Maven repo. The configuration could be simplified using properties, and the uber jars (generated by the shade plugin) should not be deployed to the Maven repository.
> Here is the current deployment status and proposed for the modules.
> ||Module Name||Current Deployment||Proposed||
> | Narayana: all | deployed | deployed |
> | Narayana: common | deployed | deployed |
> | Narayana: Arjunacore | deployed | deployed |
> | Narayana: ArjunaCore arjuna | deployed | deployed |
> | Narayana: ArjunaCore txoj | deployed | deployed |
> | Narayana: ArjunaCore arjunacore | deployed | {color:red} skipped {color} |
> | Narayana: ArjunaJTA | deployed | deployed |
> | Narayana: ArjunaJTA jta | deployed | deployed |
> | Narayana: ArjunaJTA cdi | skipped | {color:red} deployed {color} |
> | Narayana: ArjunaJTA jdbc | skipped | {color:red} deployed {color} |
> | Narayana: ArjunaJTA narayana-jta | deployed | {color:red} skipped {color} |
> | Narayana: XTS | deployed | deployed |
> | Narayana: XTS byteman_support | deployed | deployed |
> | Narayana: XTS WSAS | skipped | skipped |
> | Narayana: XTS WSAS xts-test-servlet | skipped | skipped |
> | Narayana: XTS WS-C | skipped | skipped |
> | Narayana: XTS WSCF | skipped | skipped |
> | Narayana: XTS WS-T | skipped | skipped |
> | Narayana: XTS WSTX | skipped | skipped |
> | Narayana: XTS recovery | skipped | skipped |
> | Narayana: XTS bridge | skipped | skipped |
> | Narayana: XTS sar | skipped | skipped |
> | Narayana: XTS jbossxts | deployed | deployed |
> | Narayana: XTS localjunit | skipped | skipped |
> | Narayana: XTS localjunit unit | skipped | skipped |
> | Narayana: XTS WSTX11-interop | skipped | skipped |
> | Narayana: XTS WSTFSC07-interop | skipped | skipped |
> | Narayana: XTS localjunit xtstest | skipped | skipped |
> | Narayana: XTS localjunit crash-recovery-tests | skipped | skipped |
> | Narayana: ArjunaJTS | deployed | deployed |
> | Narayana: ArjunaJTS idl | skipped | {color:red} deployed {color} |
> | Narayana: ArjunaJTS idl jacorb | skipped | {color:red} deployed {color} |
> | Narayana: ArjunaJTS orbportability | skipped | {color:red} deployed {color} |
> | Narayana: ArjunaJTS jts | skipped | {color:red} deployed {color} |
> | Narayana: ArjunaJTS jtax | skipped | {color:red} deployed {color} |
> | Narayana: ArjuntaJTS narayana-jts-jacorb | deployed | {color:red} skipped {color} |
> | Narayana: ArjunaJTS integration | deployed | deployed |
> | Narayana: rest-tx | deployed | deployed |
> | Narayana: rest-tx util | deployed | deployed |
> | Narayana: rest-tx tx (RESTful API for Atomic Transactions) | deployed | deployed |
> | Narayana: rest-tx webservice | skipped | skipped |
> | Narayana: rest-tx integration | deployed | deployed |
> | Narayana: txbridge | deployed | deployed |
> | Narayana: fileio | deployed | deployed |
> | Narayana: STM | skipped | skipped |
> | Narayana: txframework | deployed | deployed |
> | Narayana: narayana-full | skipped | skipped |
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (JBTM-974) Allow callback invocation for multiple business method invocations
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-974?page=com.atlassian.jira.plugin.s... ]
Gytis Trikleris closed JBTM-974.
--------------------------------
Fix Version/s: (was: 6.later)
Resolution: Out of Date
> Allow callback invocation for multiple business method invocations
> ------------------------------------------------------------------
>
> Key: JBTM-974
> URL: https://issues.jboss.org/browse/JBTM-974
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Compensations
> Reporter: Paul Robinson
> Labels: TXFramework
>
> By setting the 'single' attribute on a Lifecycle Handler Annotation (such as @Prepare or @Compensate) identifies whether more than one callback can be registered for the lifecycle method in response to multiple invocations of the ServiceRequest method. If it is true then the lifecycle method will be called once to the ServiceRequest method. If it is false then the lifecycle method will be called once in response to each (non-read only) call to the ServiceRequest method. The default is 'false'.
> Annotation:
> {code}
> @Retention(RetentionPolicy.RUNTIME)
> @Target(ElementType.METHOD)
> public @interface Compensate
> {
> public boolean single() default false;
> }
> {code}
> Example:
> {code}
> @ServiceRequest
> public void addToBasket()
> {
> //Add another item to the basket.
> }
> @Compensate(single=true)
> public void emptyBasket()
> {
> //Empty every item from the basket
> }
> {code}
> In this example the @ServiceRequest may be invoked many times to add many items to the basket. The @Compensate method is only needed to be invoked once as the basket can be emptied in one operation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (JBTM-845) Datagrid Objectstore
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-845?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson resolved JBTM-845.
--------------------------------
Assignee: Tom Jenkinson
Resolution: Won't Fix
James Brearly did analysis on this in his thesis and the outcome was that split brain would severely impact the comprehensiveness of the solution.
> Datagrid Objectstore
> --------------------
>
> Key: JBTM-845
> URL: https://issues.jboss.org/browse/JBTM-845
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Components: Recovery
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
>
> Create an objectstore that uses infinispan or jgroups for replication of volatile data
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months