August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1488) Implement the REST-JDI specification

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1488?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1488: ----------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Implement the REST-JDI specification > ------------------------------------ > > Key: JBTM-1488 > URL: https://issues.jboss.org/browse/JBTM-1488 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.0.0.Final > > > https://community.jboss.org/wiki/CompensatingRESTfulTransactions/ -- 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

10 years, 9 months

1
0
0 / 0

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

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-971?page=com.atlassian.jira.plugin.s... ] Paul Robinson resolved JBTM-971. -------------------------------- Assignee: Paul Robinson Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) Resolution: Done Applies to AT support which is being dropped in favour of JTA bridging. In which case ReadOnly is notified via the XA mechanism. > 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: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Labels: TXFramework > Fix For: 5.0.0.M5 > > > This method can be called from a web service method while a transaction is active to notify the framework that no changes have been made during execution of the service method. This is a useful alternative to annotating the ServiceRequest as ReadOnly as it allows the business logic to decide at runtime if modifications were made. > {code} > public interface Control > { > public void readOnly(); > } > {code} -- 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

10 years, 9 months

1
0
0 / 0

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

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-971?page=com.atlassian.jira.plugin.s... ] Paul Robinson reopened JBTM-971: -------------------------------- > 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: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Labels: TXFramework > Fix For: 5.0.0.M5 > > > This method can be called from a web service method while a transaction is active to notify the framework that no changes have been made during execution of the service method. This is a useful alternative to annotating the ServiceRequest as ReadOnly as it allows the business logic to decide at runtime if modifications were made. > {code} > public interface Control > { > public void readOnly(); > } > {code} -- 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

10 years, 9 months

1
0
0 / 0

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

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-971?page=com.atlassian.jira.plugin.s... ] Paul Robinson resolved JBTM-971. -------------------------------- Resolution: Won't Fix > 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: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Labels: TXFramework > Fix For: 5.0.0.M5 > > > This method can be called from a web service method while a transaction is active to notify the framework that no changes have been made during execution of the service method. This is a useful alternative to annotating the ServiceRequest as ReadOnly as it allows the business logic to decide at runtime if modifications were made. > {code} > public interface Control > { > public void readOnly(); > } > {code} -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1390) Update BaseCrashTest to use global arguments

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1390?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1390: -------------------------------- Priority: Minor (was: Major) > Update BaseCrashTest to use global arguments > -------------------------------------------- > > Key: JBTM-1390 > URL: https://issues.jboss.org/browse/JBTM-1390 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > > Ideally we should only have the byteman, memory and ipv6 args in a single place (root pom.xml). However, these are hardcoded in the BaseCrashTest of the XTS recovery tests. > These should be using the values set in the pom. > {code} > protected String BytemanArgs = "-Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dorg.jboss.byteman.verbose -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.byteman.transform.all -javaagent:target/test-classes/lib/byteman.jar=script:target/test-classes/scripts/@BMScript@.txt,boot:target/test-classes/lib/byteman.jar,listener:true"; > protected String iPv6Args = "-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.bind.address=[::1] -Djboss.bind.address.management=[::1] -Djboss.bind.address.unsecure=[::1] "; > {code} -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1523) Try to have XTS enabled in standalone-full.xml

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1523?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1523: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Try to have XTS enabled in standalone-full.xml > ---------------------------------------------- > > Key: JBTM-1523 > URL: https://issues.jboss.org/browse/JBTM-1523 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Application Server Integration, XTS > Reporter: Paul Robinson > Fix For: 6.0.0.Final > > > The problem is that XTS currently increases boot time by about 50%. Therefore it has to live in its own configuration. > If we can reduce this boot cost, we may be able to get it included in standalone-full.xml. > I think the main problem is the time it takes to register all the XTS Web Service endpoints. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1415) TXFramework: Allow servlet-name to be anything in web.xml

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1415?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1415: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > TXFramework: Allow servlet-name to be anything in web.xml > --------------------------------------------------------- > > Key: JBTM-1415 > URL: https://issues.jboss.org/browse/JBTM-1415 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Fix For: 6.0.0.Final > > > Removes a restriction imposed by JBTM-1408. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-974) Allow callback invocation for multiple business method invocations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-974?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-974: ------------------------------- Summary: Allow callback invocation for multiple business method invocations (was: Allow single lifecycle invocation for multiple ServiceRequest invocations) > 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 > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Labels: TXFramework > Fix For: 5.0.0.Final > > > 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 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-974) Allow callback invocation for multiple business method invocations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-974?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-974: ------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > 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 > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Labels: TXFramework > Fix For: 6.0.0.Final > > > 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 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1515) Investigate the overhead of bridging JTA to WS-AT when not needed

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1515?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1515: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Investigate the overhead of bridging JTA to WS-AT when not needed > ----------------------------------------------------------------- > > Key: JBTM-1515 > URL: https://issues.jboss.org/browse/JBTM-1515 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Fix For: 6.0.0.Final > > > When using default context propagation, a subordinate WS-AT transaction will be created for Web service calls made within a JTA transaction. This is wasteful if the target service does not enlist any participants in this transaction. > We should measure the overhead that this imposes and take steps to reduce/remove it. -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2013