Hi, Jan -
The fix I provided (patch) merely fixed the NullPointerException, I imagine
the naming bit for the service lookup is elsewhere. My config used HTTP
(REST) binding, not SOAP, so I didn't have a WSDL to worry about :-).
Good luck!
Brice
On 6/15/07, Jan Jordan <[EMAIL PROTECTED]> wrote:
Hi all
we encounter a really strange behaviour while integrating cxf in our
application (spring, Hibernate, jetty etc):
In our spring applicationContext we have beans like this:
<bean id="vendorManager" parent="txProxyTemplate">
<property name="target">
<bean class="dw.fbi.service.impl.VendorManagerImpl">
<property name="vendorDao" ref="vendorDAO"/>
</bean>
</property>
</bean>
And some transaction stuff:
<bean id="txProxyTemplate" abstract="true"
class="org.springframework.transaction.interceptor.TransactionProxyFacto
ryBean">
<property name="transactionManager"><ref
bean="transactionManager"/></property>
<property name="transactionAttributes">
<props>
<prop key="save*">PROPAGATION_REQUIRED</prop>
<prop key="remove*">PROPAGATION_REQUIRED</prop>
<prop key="*">PROPAGATION_REQUIRED,readOnly</prop>
</props>
</property>
</bean>
In the cxf.xml we have a jaxws endpoint like this, referencing the
vendorManager bean:
<jaxws:endpoint
id="vendorManagerService"
implementor="#vendorManager"
address="/VendorManagerService"
>
</jaxws:endpoint>
In the logfile i get the following messages on starftup:
15.06.2007 14:02:02
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
INFO: Creating Service $Proxy24Service from class $Proxy24
In the page in the webbrowser the service ist listet with "$Proxy24Port"
having a wsdl-link to
"http://localhost:8080/services/VendorManagerService?wsdl";
Which causes an exception on the ?wsdl request:
"org.apache.cxf.transport.http.WSDLQueryException:
COULD_NOT_PROVIDE_WSDL"
This happens only when i use a bean which is connected to:
org.springframework.transaction.interceptor.TransactionProxyFactoryBean
If i omit the reference to the transactionproxy stuff it works ok, but
of course i would like to use the transactionManager.
We thought that the folling issue is connected to this:
http://www.mail-archive.com/[email protected]/msg00662.html
But i am not sure if this is fixed or even if it is the real reason. We
tried to fix it like Brice Ruth proposed, but there was no change in the
outcome.
Any ideas?
Best regards
Jan Jordan
--
Brice Ruth, FCD
Software Engineer, Madison WI
