Thanks for your hints - however: it still does not work.
First: I did not find any log messages about "buildServiceFromClass" or
"buildServiceFromWSDL" in catalina.out.
Second:
I replaced the configuration in cxf-servlet.xml
<jaxws:endpoint id="FooService"
implementor="#fooService"
address="/FooService">
</jaxws:endpoint>
with a new one like:
<jaxws:endpoint id="FooService"
implementor="#fooService"
wsdlLocation="wsdl/main.wsdl"
createdFromAPI="false"
address="/FooService">
</jaxws:endpoint>
The service seems to start but when I try to access the service and to read
the URL, I get a text saying "No service was found." There are no error
messages in catalina.out however.
Any hints? Thanks in advance.
--
Uwe Maurer
Software Architect / SIS OIBKV
____EnBW Systeme Infrastruktur Support GmbH
Tel.: +49 (7 21) 63- 1 45 17
Mobil: +49 (175) 2 28 98 34
mailto:[EMAIL PROTECTED]
> -----Ursprüngliche Nachricht-----
> Von: Daniel Kulp [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 13. Mai 2008 17:49
> An: [email protected]
> Betreff: Re: CXF delivers transformed WSDL on ?wsdl Request
>
>
>
> In the catalina.out file or other log file, can you look for lines
> that look something like:
>
> May 12, 2008 1:06:07 PM
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> buildServiceFromClass
>
> or
>
> May 12, 2008 1:06:07 PM
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> buildServiceFromWSDL
>
>
> The second is what we want to see. In the first case, it
> builds the
> WSDL based on the annotations in the class and such. The second
> should be using the wsdl properly. If you see the
> buildServiceFromClass form, you'll need to update the spring config
> (or annotations) to specify the wsdlLocation.
>
>
> Dan
>
>
>
>
> On May 13, 2008, at 8:52 AM, Maurer Uwe wrote:
>
> > Hi,
> >
> > I am developing a "contract first" webservice using CXF on Tomcat.
> > The WSDL
> > file is originally built by SAP Netweaver and consists of
> three files:
> >
> > ./main.wsdl
> > - defines <wsdl:service> and imports
> ./bindings/Http_document.wsdl
> > via <wsdl:import> ./bindings/Http_document.wsdl
> > - defines <wsdl:binding> and imports
> > ../porttypes/Http_fooservice_document.wsdl
> > ./porttypes/http_fooservice_document.wsdl
> > - defines <wsdl:types>
> >
> > I impleneted my service using a JAXB binding generated from the
> > WSDL2Java
> > tool. I deploy the three files in a war in WEB-INF/wsdl
> directory. The
> > service itselfs runs - BUT:
> >
> > A request with parameter ?wsdl returns a different WSDL
> file than the
> > original. There are only two files left:
> >
> > One defining <wsdl:service> and <wsdl:types> and another
> includes one
> > defining <wsdl:binding>. Also some names (Faults) differ. This leads
> > to
> > compatibility problems with the service clients.
> >
> > Can anyone explain this behaviour to me?
> > How can I manage, that the original WSDLs are delivered
> through the ?
> > wsdl
> > request?
> >
> > Yours,
> > Uwe
>
> ---
> Daniel Kulp
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
>
>
>
>
