Interop is still a bit tricky: What happens if you take the WCF created
wsdl and

back-import this wsdl into WCF using the menu add-service-reference in
visual 

studio to read the just created WSDL file?

 

Are client stubs and server skeletons created and do the work together?

 

BUT

Why not taking the opposite way?

 

What I have found in general doing interop between Axis2/J and WCF 4.0
is, that

creating the service code first using JAXWS / JAXB annotations, then
keep this 

service running and use visual studio to catch the wsdl from a running
service/system 

created me client side stubs perfect. 

 

After that I still can/need to massage the app.config generated for my
stub.dll, 

 

massaging can be done by adding more JAXWS / JAXB and other annotations

(look at provided AXIS2 JAXWS samples), sometimes one is required to
just drop

a parameter for a annotation to make all work. 

 

AND

 

I have to integrate / merge the app.config content of the generated
stub.dll into 

the app.config of the main project; then up on compilation/linking of
the <your-main-app>

you will have a file <your-main-app-name>.exe.config as well as
<your-main-app-name>.exe

 

Josef

 

 

Von: Harish Kumar [mailto:harish_k_s...@yahoo.com] 
Gesendet: Dienstag, 22. Januar 2013 10:00
An: java-user@axis.apache.org
Betreff: Error : No Service found in WSDL

 

 

Hi,

 

      I am using Axis2-1.6.2. I have WSDL file which is generated by
WCF. 

 While i run command wsdl2java, i am getting following error message.
Can any one suggest about how to fix it?

 

Caused by: org.apache.axis2.AxisFault: No service was not found in the
WSDL at f

ile data.wsdl with targetnamespace data

        at
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA

llServices(WSDL11ToAllAxisServicesBuilder.java:115)

        at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat

ionEngine.java:147)

        ... 2 more

 

On other hand, i do not see any error if i load this WSDL in soapUI and
run as MockService.

Looks like there is issue with Axis2.

 

Thanks

 

Reply via email to