cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Schroedl (JIRA)" <>
Subject [jira] Commented: (CXF-1088) aop wrapping service classes breaks cxf
Date Fri, 05 Oct 2007 21:18:51 GMT


Tom Schroedl commented on CXF-1088:

I was able to glean a workaround from posts in mailing list archives. Instead of <jaxws:endpoint>,
I had to use:

     address="/MyService" />

Addressing the impact of Spring AOP proxies on annotations in web service implementation classes
in documentation and examples would be helpful to all.  It would also be good to have <jaxws:endpoint>
support this type of configuration.

> aop wrapping service classes breaks cxf
> ---------------------------------------
>                 Key: CXF-1088
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.0.2
>         Environment: Services deployed to Tomcat 5.5 as webapp. Java 5 codebase.
>            Reporter: Tom Schroedl
> Wsdl generation fails when my service interfaces are wrapped using Spring AOP. If I change
to wrapping my implementation classes, the wsdl can now be generated. However, the following
error occurs when attempting to invoke a service from a separate java client application:
> org.apache.cxf.interceptor.Fault: No Hibernate Session bound to thread, and configuration
does not allow creation of non-transactional on here.
> I have another Spring dispatcher servlet and GWTHandler that is used for handling GWT
requests against the same POJOs. Works fine. I also had it working with XFire and Aegis binding
prior to CXF merger. After upgrade, decided to go with JAX-WS, but have come to the aforementioned
stopping point.
> V/R,
> Tom 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message