6 Replies Latest reply on Sep 21, 2011 2:16 PM by paul.robinson

    Txbridge : problem with RPC/Literal style

    web_murali

      Hi Everyone,

       

       

      My Enviroment is :

       

      Jboss 5.1.0 GA

      JBOSSTS_4_7_0_GA

      Built in CXF Stack

       

      I have compile Txbridge.jar from JBOSSTS_4_7_0_GA version.Even the demo applciation of TxBridge that is  txbridge-demo-client.war also not working showing some errors like :

       

       

       

      Transaction Result: Transaction failed! Cause: com.arjuna.wst.SystemException: javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
      
      

       

       

      When I try to run my sample application with TxBridge I am getting the below exception:

       

      Jboss 5.1.0 GA

      JBOSSTS_4_7_0_GA

      CXF 2.4.0(For my application only)

       

       

      org.apache.cxf.interceptor.Fault: Found element arg0 but could not find matching RPC/Literal part
              at org.apache.cxf.binding.soap.interceptor.RPCInInterceptor.handleMessage(RPCInInterceptor.java:171)
              at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
              at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:736)
              at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1563)
              at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1448)
              at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1356)
              at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
              at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:614)
              at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSende
      rInterceptor.java:62)
              at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
              at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:484)
              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:414)
              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:317)
              at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:269)
              at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
              at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
              at $Proxy441.findByPrimaryKey(Unknown Source)
              at foo.service.MuraliServiceImpl.save(MuraliServiceImpl.java:77)
              at foo.service.MuraliServiceImpl$$FastClassByCGLIB$$c98ece00.invoke(<generated>)
              at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
              at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:68
      8)
              at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
              at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
              at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
              at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:621)
      
              at foo.service.MuraliServiceImpl$$EnhancerByCGLIB$$df695a0f.save(<generated>)
              at foo.controller.TestController.TestProcess(TestController.java:111)
              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.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker
      .java:176)
              at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationM
      ethodHandlerAdapter.java:436)
              at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerA
      dapter.java:424)
              at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:790)
              at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719)
              at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644)
              at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:549)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
              at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
              at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
              at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
              at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
              at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
              at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.jav
      a:126)
              at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java
      :70)
      

       

       

      Thanks in advanced,

       

      Macin

        • 1. Re: Txbridge : problem with RPC/Literal style
          paul.robinson

          Macin,

           

          We are no longer supporting Jboss 5.1.0 GA or JBossTS 4.7.0. Also, the TxBrdge was only tested with JBoss Native Web services, so there may well be issues.

           

          JBoss 7.0.1 contains JBossTS 4.15.3 which was tested with CXF and is also currently under active development. Are you able to upgrade to JBoss 7.0.1 to see if you are having the same problem?

           

          Thanks,

           

          Paul.

          • 2. Re: Txbridge : problem with RPC/Literal style
            web_murali

            Thank you Paul Robinson

             

            I have tried to deploy demo application of TxBridge (ie:. txbridge-demo-service.jar , txbridge-demo-client.war) on Jboss AS 7.0.1 AS without luck. Is there any procedure to  deploy JBossTS 4.15.3 demo application on Jboss AS 7. Please help me on this.

             

            Thanks in advance,

            Macin

            • 3. Re: Txbridge : problem with RPC/Literal style
              paul.robinson

              Macin,

               

              Which version of the JBossTS distribution did you take the bridge demo from (bistro service)? It has to be the same version to that which is running in JBoss. In this case you need to take the demo from "JBossTS 4.15.0" in order to deploy it into JBoss AS 7.0.1.

               

              You may notice a discrepancy between the version numbers, 4.15.0 vs 4.15.3. Basically the minor revision number represents a bug fix release which is not made into a community release. This shouldn't cause you any problems.

               

              Thanks,

               

              Paul.

              • 4. Re: Txbridge : problem with RPC/Literal style
                paul.robinson

                Macin,

                 

                You say that you have tried to deploy the demo application without any luck. Are you having difficulty with the deployment process or are you seeing the same error that you mentioned in the original post?

                 

                Thanks,

                 

                Paul.

                • 5. Re: Txbridge : problem with RPC/Literal style
                  web_murali

                  Thanks paul,

                   

                  I have successfully implemented JTA transactions in my application on Jboss6.1.0.When I tried to test JTS transactions on two different Jboss instances I got the following exception

                   

                       com.arjuna.wst.UnknownTransactionException

                   

                  Thanks,

                  Macin

                  • 6. Re: Txbridge : problem with RPC/Literal style
                    paul.robinson

                    Macin,

                     

                    Are you still referring to the same issue or is your latest post referring to something new?

                     

                    I am a little confused, you say you are using "JTS Transactions", but you are receiving a Web service transactions Exception. Do you mean JTS or JTA?

                     

                    JTS is a standard for doing distributed transactions over Corba. JTA is a standard for doing local transactions within a single app server. JBossTS bridges automatically between JTA transactions and JTS transactions in order for you to span many application servers with a single transaction.

                     

                    WS-AT (Atomic Web service transactions) is a standard for doing distributed transactions over Web services. JBossTS can bridge between JTA and WS-AT, but you need to install the TXBridge which you where trying to get working in your original post.

                     

                    Can you clarify you current situation for me please?

                     

                    Thanks,

                     

                    Paul.