Announcement Announcement Module
No announcement yet.
Spring and JAXWS: No mixing of @Webmethod and @Transactional Annotations allowed Page Title Module
Move Remove Collapse
Conversation Detail Module
  • 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.


    • #17
      dma_k, After I add impl="" 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">
      <ws:service bean="#FSECWebService" impl="" />

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

      Feb 5, 2013 6:18:29 PM 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
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
      at java.lang.reflect.Method.invoke(
      at$1.invok e(
      at voke(
      at quest(
      at 59)
      at 8)
      at )


      • #18
        I haven't suggested to add impl="". 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.