Announcement Announcement Module
Collapse
No announcement yet.
Spring and JAXWS: No mixing of @Webmethod and @Transactional Annotations allowed Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Aiming, unfortunately you will have to split your transactional bean from web bean and use dependency injection as eldaaran suggested above.

    Comment


    • #17
      dma_k, After I add impl="fmtc.security.ws.FSECWebService" suggested by you, I no longer get java.lang.IllegalArgumentException: class $Proxy45 has neither @WebSerivce nor @WebServiceProvider annotation and can start the web service.
      <wss:binding url="/services/FSECWebService">
      <wss:service>
      <ws:service bean="#FSECWebService" impl="fmtc.security.ws.FSECWebService" />
      </wss:service>
      </wss:binding>

      But when I test the service, I got a new exception. any solution for this issue?

      Feb 5, 2013 6:18:29 PM com.sun.xml.ws.server.sei.EndpointMethodHandler invoke
      SEVERE: object is not an instance of declaring class
      java.lang.IllegalArgumentException: object is not an instance of declaring class
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at com.sun.xml.ws.api.server.InstanceResolver$1.invok e(InstanceResolver.java:197)
      at com.sun.xml.ws.server.InvokerTube$2.invoke(Invoker Tube.java:132)
      at com.sun.xml.ws.server.sei.EndpointMethodHandler.in voke(EndpointMethodHandler.java:241)
      at com.sun.xml.ws.server.sei.SEIInvokerTube.processRe quest(SEIInvokerTube.java:75)
      at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:5 59)
      at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:51 8)
      at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503 )

      Comment


      • #18
        I haven't suggested to add impl="fmtc.security.ws.FSECWebService". I have suggested to separate you transactional code into a new separate bean, so that you FSECWebService does not have @Transactional annotation. Then you can wire your new transactional bean into FSECWebService in usual way. The example is given by eldaaran above.

        Comment

        Working...
        X