January 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-986: ------------------------------- Description: When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: {code} BindingProvider bindingProvider = (BindingProvider) client; List<Handler> handlers = new ArrayList<Handler>(1); handlers.add(new JaxWSHeaderContextProcessor()); bindingProvider.getBinding().setHandlerChain(handlers); {code} This is not very user friendly. This could be done using a JAX-WS feature passed to the Client-side port. We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... The feature should be "enabled" by default providing the feature is enabled in the XTS server config. The quickstarts also need updated to use this. was: When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: {code} BindingProvider bindingProvider = (BindingProvider) client; List<Handler> handlers = new ArrayList<Handler>(1); handlers.add(new JaxWSHeaderContextProcessor()); bindingProvider.getBinding().setHandlerChain(handlers); {code} This is not very user friendly. This could be done using a JAX-WS feature passed to the Client-side port. We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > The feature should be "enabled" by default providing the feature is enabled in the XTS server config. > The quickstarts also need updated to use this. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-986: ------------------------------- Description: When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: {code} BindingProvider bindingProvider = (BindingProvider) client; List<Handler> handlers = new ArrayList<Handler>(1); handlers.add(new JaxWSHeaderContextProcessor()); bindingProvider.getBinding().setHandlerChain(handlers); {code} This is not very user friendly. This could be done using a JAX-WS feature passed to the Client-side port. We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... was: When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: {code} BindingProvider bindingProvider = (BindingProvider) client; List<Handler> handlers = new ArrayList<Handler>(1); handlers.add(new JaxWSHeaderContextProcessor()); bindingProvider.getBinding().setHandlerChain(handlers); {code} This is not very user friendly. This could be done using a JAX-WS feature passed to the Client-side port. > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1416) WSBA Participant Completion quickstart needs rendezvous

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1416?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1416: --------------------------------------- http://172.17.131.2/job/btny-narayana-quickstarts/218 > WSBA Participant Completion quickstart needs rendezvous > ------------------------------------------------------- > > Key: JBTM-1416 > URL: https://issues.jboss.org/browse/JBTM-1416 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 3 days > Remaining Estimate: 3 days > > See: http://172.17.131.2/job/btny-narayana-quickstarts/207 > {noformat} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.quickstarts.wsba.participantcompletion.simple.ClientTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.703 sec <<< FAILURE! > testSuccess(org.jboss.narayana.quickstarts.wsba.participantcompletion.simple.ClientTest) Time elapsed: 2.453 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at org.jboss.narayana.quickstarts.wsba.participantcompletion.simple.ClientTest.testSuccess(ClientTest.java:79) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) > at java.lang.Thread.run(Thread.java:662) > {noformat} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Paul Robinson edited comment on JBTM-986 at 1/9/13 5:11 AM: ------------------------------------------------------------ We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... was (Author: paul.robinson): Here's examples of how @WebServiceRe is used: http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. The default should be "enabled" providing the feature is enabled in the XTS server config. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-986: ------------------------------- Description: When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: {code} BindingProvider bindingProvider = (BindingProvider) client; List<Handler> handlers = new ArrayList<Handler>(1); handlers.add(new JaxWSHeaderContextProcessor()); bindingProvider.getBinding().setHandlerChain(handlers); {code} This is not very user friendly. This could be done using a JAX-WS feature passed to the Client-side port. was: When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: {code} BindingProvider bindingProvider = (BindingProvider) client; List<Handler> handlers = new ArrayList<Handler>(1); handlers.add(new JaxWSHeaderContextProcessor()); bindingProvider.getBinding().setHandlerChain(handlers); {code} This is not very user friendly. This could be done using a JAX-WS feature passed to the Client-side port. The default should be "enabled" providing the feature is enabled in the XTS server config. > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Paul Robinson commented on JBTM-986: ------------------------------------ We should also consider having the default to be "enabled" providing the feature is enabled in the XTS server config. > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1227) StAX is not available on Android

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1227?page=com.atlassian.jira.plugin.... ] Gytis Trikleris edited comment on JBTM-1227 at 1/9/13 5:05 AM: --------------------------------------------------------------- Implementations for system libraries, such as StAX, can be added to the application's library. However, to build such applications "--core-library" flag has to be added to dx script. Therefore, application can be built only with ant. I wrote simple application which uses JBossTS build which does not have tweaks for Android i.e. it requires StAX even from Android. Application's repository is on github: https://github.com/Gytis/jbossts-on-android Also, based on all the info I found, Android does not provide functionality to access application files directly by path, unless file is in cache. However, JBossTS reads its properties in such way. So I wrote a small library to extract file (e.g. arjuna-properties.xml) from assets directory and place it in cache. Its repository on github: https://github.com/Gytis/android_asset_cache was (Author: gytis): Implementations for system libraries, such as StAX, can be added to the application's library. However, to build such applications "--core-library" flag has to be added to dx script. Therefore, application can be built only with ant. I wrote simple application which uses JBossTS build which does not have tweaks for Android i.e. it requires StAX even from Android. Application's repository is on github: https://github.com/Gytis/jbossts-on-android Also, based on all the info I found, Android does not provide functionality to access application files directly by path, unless file is in cache. However, JBossTS reads its properties in such way. So I wrote small library to extract file (e.g. arjuna-properties.xml) from assets directory and place it in cache. > StAX is not available on Android > -------------------------------- > > Key: JBTM-1227 > URL: https://issues.jboss.org/browse/JBTM-1227 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Common > Affects Versions: 4.16.4, 5.0.0.M1 > Environment: Android 2.3.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > > StAX is not available. Since we use it for property configuration, the system fails to run unmodified. There is an equivalent implementation (XmlPullParser) but it is likely other JBoss projects will suffer from this issue. > See http://www.ibm.com/developerworks/library/x-android/ for more details. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1338) Provide an async commit feature hanging off UserTransactionImple

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1338?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1338: ------------------------------------- Glad you got this working, Ales! The thing I didn't point out here (but did in my blog entry) is that this was added to an internal package meaning that the API could in theory be altered should that become necessary. As we know you are using this we will of course consult you and the feature is unlikely to vary too much and we will deprecate the old API before altering it giving you as much time as you need to move over to its final home should a move be required. We can consider a rollbackAsync also, please feel free to raise a Jira if you would like us to add this. > Provide an async commit feature hanging off UserTransactionImple > ---------------------------------------------------------------- > > Key: JBTM-1338 > URL: https://issues.jboss.org/browse/JBTM-1338 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.3, 5.0.0.M2 > > > Equivalent of https://github.com/capedwarf/capedwarf-blue/blob/master/datastore/src/mai... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1338) Provide an async commit feature hanging off UserTransactionImple

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/JBTM-1338?page=com.atlassian.jira.plugin.... ] Ales Justin commented on JBTM-1338: ----------------------------------- OK, got it working. final class AsyncTxHelper { private static final String GET_TM = "getTransactionManager"; private static final String COMMIT_ASYNC = "commitAsync"; static Future<Void> commit(Object tx) { if (tx != null) { try { if (tx instanceof TransactionManager) { tx = ReflectionUtils.invokeStaticMethod(tx.getClass(), GET_TM); } return (Future<Void>) ReflectionUtils.invokeInstanceMethod(tx, COMMIT_ASYNC); } catch (Exception ignore) { } } return null; } > Provide an async commit feature hanging off UserTransactionImple > ---------------------------------------------------------------- > > Key: JBTM-1338 > URL: https://issues.jboss.org/browse/JBTM-1338 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.3, 5.0.0.M2 > > > Equivalent of https://github.com/capedwarf/capedwarf-blue/blob/master/datastore/src/mai... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1338) Provide an async commit feature hanging off UserTransactionImple

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/JBTM-1338?page=com.atlassian.jira.plugin.... ] Ales Justin commented on JBTM-1338: ----------------------------------- Same with java:comp/UserTransaction. > Provide an async commit feature hanging off UserTransactionImple > ---------------------------------------------------------------- > > Key: JBTM-1338 > URL: https://issues.jboss.org/browse/JBTM-1338 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.3, 5.0.0.M2 > > > Equivalent of https://github.com/capedwarf/capedwarf-blue/blob/master/datastore/src/mai... -- 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, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2013