You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Tom Schroedl (JIRA)" <ji...@apache.org> on 2007/10/04 23:45:50 UTC
[jira] Created: (CXF-1088) aop wrapping service classes breaks cxf
aop wrapping service classes breaks cxf
---------------------------------------
Key: CXF-1088
URL: https://issues.apache.org/jira/browse/CXF-1088
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.
[jira] Resolved: (CXF-1088) document handling of case where spring
aop breaks wsdl generation
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schroedl resolved CXF-1088.
-------------------------------
Resolution: Fixed
I see that some help on this was added to the FAQ section on the CXF website. Closing this issue out.
> document handling of case where spring aop breaks wsdl generation
> -----------------------------------------------------------------
>
> Key: CXF-1088
> URL: https://issues.apache.org/jira/browse/CXF-1088
> Project: CXF
> Issue Type: Improvement
> 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 (for database transactions). 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 an independent java client application:
> org.apache.cxf.interceptor.Fault: No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one 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.
[jira] Commented: (CXF-1088) aop wrapping service classes breaks
cxf
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532780 ]
Daniel Kulp commented on CXF-1088:
----------------------------------
jaxws:endpoint has an implementorClass attribute which should work similarly.
> aop wrapping service classes breaks cxf
> ---------------------------------------
>
> Key: CXF-1088
> URL: https://issues.apache.org/jira/browse/CXF-1088
> 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 one 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.
[jira] Updated: (CXF-1088) document handling of case where spring
aop breaks wsdl generation
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schroedl updated CXF-1088:
------------------------------
Summary: document handling of case where spring aop breaks wsdl generation (was: document and improve handling of case where spring aop breaks wsdl generation)
> document handling of case where spring aop breaks wsdl generation
> -----------------------------------------------------------------
>
> Key: CXF-1088
> URL: https://issues.apache.org/jira/browse/CXF-1088
> Project: CXF
> Issue Type: Improvement
> 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 (for database transactions). 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 an independent java client application:
> org.apache.cxf.interceptor.Fault: No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one 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.
[jira] Updated: (CXF-1088) document and improve handling of case
where spring aop breaks wsdl generation
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schroedl updated CXF-1088:
------------------------------
Description:
Wsdl generation fails when my service interfaces are wrapped using Spring AOP (for database transactions). 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 an independent java client application:
org.apache.cxf.interceptor.Fault: No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one 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
was:
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 one 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
Summary: document and improve handling of case where spring aop breaks wsdl generation (was: aop wrapping service classes breaks cxf)
> document and improve handling of case where spring aop breaks wsdl generation
> -----------------------------------------------------------------------------
>
> Key: CXF-1088
> URL: https://issues.apache.org/jira/browse/CXF-1088
> 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 (for database transactions). 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 an independent java client application:
> org.apache.cxf.interceptor.Fault: No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one 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.
[jira] Updated: (CXF-1088) aop wrapping service classes breaks cxf
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schroedl updated CXF-1088:
------------------------------
Description:
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 one 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
was:
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
> aop wrapping service classes breaks cxf
> ---------------------------------------
>
> Key: CXF-1088
> URL: https://issues.apache.org/jira/browse/CXF-1088
> 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 one 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.
[jira] Commented: (CXF-1088) document handling of case where spring
aop breaks wsdl generation
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532785 ]
Tom Schroedl commented on CXF-1088:
-----------------------------------
Excellent. That works for me too. I've updated the subject to just say that some documentation is needed in this area.
> document handling of case where spring aop breaks wsdl generation
> -----------------------------------------------------------------
>
> Key: CXF-1088
> URL: https://issues.apache.org/jira/browse/CXF-1088
> Project: CXF
> Issue Type: Improvement
> 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 (for database transactions). 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 an independent java client application:
> org.apache.cxf.interceptor.Fault: No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one 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.
[jira] Commented: (CXF-1088) aop wrapping service classes breaks
cxf
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532779 ]
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:
<jaxws:server
id="myService"
serviceClass="my.package.MyServiceImpl"
serviceBean="#myServiceImpl"
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: https://issues.apache.org/jira/browse/CXF-1088
> 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.
[jira] Updated: (CXF-1088) document and improve handling of case
where spring aop breaks wsdl generation
Posted by "Tom Schroedl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Schroedl updated CXF-1088:
------------------------------
Issue Type: Improvement (was: Bug)
> document and improve handling of case where spring aop breaks wsdl generation
> -----------------------------------------------------------------------------
>
> Key: CXF-1088
> URL: https://issues.apache.org/jira/browse/CXF-1088
> Project: CXF
> Issue Type: Improvement
> 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 (for database transactions). 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 an independent java client application:
> org.apache.cxf.interceptor.Fault: No Hibernate Session bound to thread, and configuration does not allow creation of non-transactional one 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.