December 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-855) Create an example showing integration with Tomcat and Spring

by Tom Jenkinson (JIRA)

Create an example showing integration with Tomcat and Spring ------------------------------------------------------------ Key: JBTM-855 URL: https://issues.jboss.org/browse/JBTM-855 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Simple example showing TS in use by tomcat and spring -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
4
0 / 0

[JBoss JIRA] (JBTM-978) Support REST-AT protocol in the TXFramework

by Paul Robinson (Created) (JIRA)

Support REST-AT protocol in the TXFramework ------------------------------------------- Key: JBTM-978 URL: https://issues.jboss.org/browse/JBTM-978 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 This class level annotation allows the class which is the target of lifecycle handler callbacks to be specified. {code} @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.TYPE) public @interface ParticipantService { public Class lifecycleClass() default Default.class; } {code} This field may be overridden in the ServiceRequest annotation itself. If the value of this field is Default.class then the ParticipantService class is used as the default class to resolve POJO lifecycle methods. {code} @Retention(RetentionPolicy.RUNTIME) @Target({ElementType.METHOD, ElementType.TYPE}) public @interface ServiceRequest { public Class lifecycleClass() default Default.class; } {code} If the lifecycleClass attribute is not specified in either place, the class containing the @ServiceInvocation is assumed to also contain the associated Lifecycle Handler methods. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
13
0 / 0

[JBoss JIRA] Created: (JBTM-865) Make sure REST-AT is covered in docbook

by Michael Musgrove (JIRA)

Make sure REST-AT is covered in docbook --------------------------------------- Key: JBTM-865 URL: https://issues.jboss.org/browse/JBTM-865 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.0.M2 Include a section on REST-AT in docbook -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[JBoss JIRA] (JBTM-970) Allow a ServiceRequest to be annotated as read only

by Paul Robinson (Created) (JIRA)

Allow a ServiceRequest to be annotated as read only --------------------------------------------------- Key: JBTM-970 URL: https://issues.jboss.org/browse/JBTM-970 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 This class level annotation allows the class which is the target of lifecycle handler callbacks to be specified. {code} @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.TYPE) public @interface ParticipantService { public Class lifecycleClass() default Default.class; } {code} This field may be overridden in the ServiceRequest annotation itself. If the value of this field is Default.class then the ParticipantService class is used as the default class to resolve POJO lifecycle methods. {code} @Retention(RetentionPolicy.RUNTIME) @Target({ElementType.METHOD, ElementType.TYPE}) public @interface ServiceRequest { public Class lifecycleClass() default Default.class; } {code} If the lifecycleClass attribute is not specified in either place, the class containing the @ServiceInvocation is assumed to also contain the associated Lifecycle Handler methods. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] (JBTM-985) Add WS-TX WS-Policy assertions to generated WSDL

by Paul Robinson (Created) (JIRA)

Add WS-TX WS-Policy assertions to generated WSDL ------------------------------------------------- Key: JBTM-985 URL: https://issues.jboss.org/browse/JBTM-985 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 See the "Policy Assertions" section of the WS-BA and WS-AT specification for what this should implement. Ideally this feature would be turned on/off via an annotation, however we should take a look to see if WS-Policy mandates a particular method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] (JBTM-971) Allow a ServiceRequst method to programaticaly state that it is ReadOnly

by Paul Robinson (Created) (JIRA)

Allow a ServiceRequst method to programaticaly state that it is ReadOnly ------------------------------------------------------------------------ Key: JBTM-971 URL: https://issues.jboss.org/browse/JBTM-971 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 The RequestType attribute on the ServiceRequest annotation identifies whether the service request is always read only as far as transactional modifications are concerned or, alternatively, that it may make changes to transactional data. in the latter case the service request method can indicate a read-only outcome by invoking the readOnly method of an injected control. {code} @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.METHOD) public @interface ServiceRequest { public RequestType requestType() default RequestType.MODIFY; } {code} The framework does not normally register lifecycle callbacks for ServiceRequest methods whose request type is READ_ONLY (see the next paragraph for the rider which qualifies this statement). The framework does normally register callbacks for ServiceRequest methods whose request type is MODIFY, on the assumption that the method has performed transactional changes. The latter methods may inhibit registration of lifecycle methods by calling the readOnly() method of an injected transaction control. The reason why it is important to identify READ_ONLY methods is that they affect the way the framework performs PREPARE or COMPLETE processing (as appropriate to the protocol in question). If all ServiceRequest methods in the transaction are READ_ONLY the participant will trigger READ_ONLY or EXIT callbacks, respectively, for these lifecycle events, precluding further involvement in the transaction. If any of the ServiceRequest methods is not READ_ONLY then the framework will trigger PREPARE or COMPLETE callbacks, respectively. Clearly, it would be futile for a READ_ONLY declaration or notification to inhibit registration of callbacks which are triggered by READ_ONLY or EXIT events. So, the framework only registers READ_ONLY or EXIT lifecycle callbacks when they are triggered by READ_ONLY methods or by MODIFY methods which notify their READ_ONLY status using an injected control. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] (JBTM-997) TXFramework build is broken

by Paul Robinson (Created) (JIRA)

TXFramework build is broken --------------------------- Key: JBTM-997 URL: https://issues.jboss.org/browse/JBTM-997 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TXFramework Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson Priority: Critical Fix For: 5.0.0.M2 To reproduce: {code} cd $NARAYANA_HOME/txframework/framework/ mvn clean install {code} Observe: {code} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project txframework: Compilation failure: Compilation failure: [ERROR] /Users/paul/Dropbox/Redhat/backup/dev/JBOSSTS_TRUNK/narayana/txframework/framework/src/main/java/org/jboss/narayana/txframework/api/annotation/transaction/WSBA.java:[21,65] incompatible types [ERROR] found : org.jboss.narayana.txframework.api.configuration.transaction.CompletionType [ERROR] required: org.jboss.narayana.txframework.api.configuration.transaction.CompletionType [ERROR] /Users/paul/Dropbox/Redhat/backup/dev/JBOSSTS_TRUNK/narayana/txframework/framework/src/main/java/org/jboss/narayana/txframework/api/annotation/service/ServiceRequest.java:[32,56] incompatible types [ERROR] found : org.jboss.narayana.txframework.api.configuration.service.RequestType [ERROR] required: org.jboss.narayana.txframework.api.configuration.service.RequestType [ERROR] -> [Help 1] {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

8
21
0 / 0

[JBoss JIRA] (JBTM-1006) Review TXFramework test coverage

by Paul Robinson (Created) (JIRA)

Review TXFramework test coverage -------------------------------- Key: JBTM-1006 URL: https://issues.jboss.org/browse/JBTM-1006 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TXFramework Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson Priority: Minor Fix For: 5.0.0.M2 Only the obvious "happy path" cases are tested at the moment. Need to ensure incorrect developer implementation and configuration is handled correctly. We should also consider taking a copy of the existing XTS tests and modify to use the TXFramework. This could allow us to get some good coverage, relatively quickly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (JBTM-969) Specify external participant lifecycle class on a per ServiceRequest method basis

by Paul Robinson (Created) (JIRA)

Specify external participant lifecycle class on a per ServiceRequest method basis --------------------------------------------------------------------------------- Key: JBTM-969 URL: https://issues.jboss.org/browse/JBTM-969 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 This class level annotation allows the class which is the target of lifecycle handler callbacks to be specified. If this annotation is not specified, the clas contining the @ServiceInvocation is assumed to also contain the associated Lifecycle Handler methods. {code} @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.TYPE) public @interface ParticipantService { public Class lifecycleClass() default Default.class; } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
7
0 / 0

[JBoss JIRA] (JBTM-972) Ensure LifecycleHandlers implemented via an EJB are invoked via the EJB stub and not direct

by Paul Robinson (Created) (JIRA)

Ensure LifecycleHandlers implemented via an EJB are invoked via the EJB stub and not direct ------------------------------------------------------------------------------------------- Key: JBTM-972 URL: https://issues.jboss.org/browse/JBTM-972 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TxBridge Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2011