April 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1016) Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1016: ----------------------------------- Summary: Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code Key: JBTM-1016 URL: https://issues.jboss.org/browse/JBTM-1016 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 I've found many bugs in the XTS crash recovery tests that where due to changes being made to the XTS code without updating the byteman scripts. The problem is that these inconsistencies often go unnoticed when the tests run, until you notice a failure in the test. A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI. -- 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, 2 months

3
19
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, 2 months

3
4
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, 2 months

3
6
0 / 0

[JBoss JIRA] (JBTM-1105) Setup client side interceptors based on WS-Policy in WSDL

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1105: ----------------------------------- Summary: Setup client side interceptors based on WS-Policy in WSDL Key: JBTM-1105 URL: https://issues.jboss.org/browse/JBTM-1105 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Reporter: Paul Robinson Assignee: Paul Robinson Priority: Minor Fix For: 5.0.0.Final If the Service WSDL specifies a WS-Policy assertion, we know that WS-AT or WS-BA is required/supported and we should be able to setup this handler chain automatically. Another benefit is that we can catch, on the client side, the situation where no WS-AT or WS-BA transaction context is present. Currently we leave it up to the service to detect and as a result we have no control over how this fault will be propagated back to the client. For example, a WrongStateException could be thrown when the service tries to enlist a participant and a transaction is not present. The Client may receive a generic fault message back or, in this case some or all of the WrongStateException. In either case, the developer of the Client is unlikely to realise that this is due to there not being a transaction present when the service was invoked. If the service mandates a WS-AT or WS-BA transaction, but none is present, then the client handler throws a suitable exception explaining what went wrong. If the service supports (i.e. it is optional) a WS-AT or WS-BA transaction, then the interceptor ignores the situation where non exists. CXF seems to have a plugin point for adding WS-Policy assertion handlers. This could be the right integration point for this feature. This is to be investigated. -- 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, 2 months

1
1
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, 2 months

3
6
0 / 0

[JBoss JIRA] (JBTM-1110) TXFramework Blog posts

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1110: ----------------------------------- Summary: TXFramework Blog posts Key: JBTM-1110 URL: https://issues.jboss.org/browse/JBTM-1110 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.1.Final -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (JBTM-1108) REST-AT -> JTA Bridge

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1108: ----------------------------------- Summary: REST-AT -> JTA Bridge Key: JBTM-1108 URL: https://issues.jboss.org/browse/JBTM-1108 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.1.Final -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (JBTM-1109) JTA -> REST-AT Bridge

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1109: ----------------------------------- Summary: JTA -> REST-AT Bridge Key: JBTM-1109 URL: https://issues.jboss.org/browse/JBTM-1109 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.1.Final -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1107) Recovery Support in TXFramework

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1107: ----------------------------------- Summary: Recovery Support in TXFramework Key: JBTM-1107 URL: https://issues.jboss.org/browse/JBTM-1107 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.1.Final -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1052) Support Web services with a webservices.xml present in TXFramework

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1052: ----------------------------------- Summary: Support Web services with a webservices.xml present in TXFramework Key: JBTM-1052 URL: https://issues.jboss.org/browse/JBTM-1052 Project: JBoss Transaction Manager Issue Type: Feature Request 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 -- 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, 2 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2012