MyEclipse Forums
This thread has been locked & this forum has been archived.
Please post new topics to Java EE Development (EJB, JSP, Struts, XDoclet, etc.)
View previous topic Printable version Log in to check your private messages View next topic
Author Message
douglasmhurst
Post subject: JAX-WS Web Service Client Problem  PostPosted: Oct 08, 2011 - 02:07 PM
Registered Member
Registered Member


Joined: Sep 30, 2006
Posts: 274

I created a Web Service in Eclipse using Axis2 version 1.5.4. I deployed it to Tomcat webapps and ran Tomcat, so it's running on 8080.

I went into MyEclipse and ran the SOAP Web Services Explorer. Using the WSDL supplied by Axis2, the Exploer sees the WS I developed in Eclipse with Axis2 and I can test it successfully.

When I try to create a WS Client in MyEclipse using the same WSDL, with the WS running on 8080, it churns for a long period of time, then comes back and tells me the WS is not SOAP 1.2 compliant.

What's that all about? There's no reason why it should do that if the Explorer works perfectly?
 
 View user's profile Send private message  
Reply with quote Back to top
support-tony
Post subject:   PostPosted: Oct 10, 2011 - 07:44 AM



Joined: Mar 09, 2011
Posts: 916

Douglas,

Did you test the SOAP 1.2 interface from the web services explorer, or SOAP 1.1? Your web service created with eclipse may not have SOAP 1.2 compliance. Can you check?

If you still have problems could you attach a screen shot of the error you get with MyEclipse, to help us get a visual. Also clear the .log file, recreate the problem and attach the log file, along with the screenshot and the WSDL file that you're using to create the client.

Can I ask why you're creating the service in eclipse and the client in MyEclipse? You can use MyEclipse to create both the service and the client.

_________________
Tony
MyEclipse Support
 
 View user's profile Send private message  
Reply with quote Back to top
douglasmhurst
Post subject:   PostPosted: Oct 10, 2011 - 02:35 PM
Registered Member
Registered Member


Joined: Sep 30, 2006
Posts: 274

I'm attaching the WSDL. If I can, I'll also attach the error message as a .jpg screen capture. I believe I successfully added them both.
 
 View user's profile Send private message  
Reply with quote Back to top
douglasmhurst
Post subject:   PostPosted: Oct 10, 2011 - 02:40 PM
Registered Member
Registered Member


Joined: Sep 30, 2006
Posts: 274

I'm trying to attach the WSDL also. I'm renaming it to .txt so it can be attached.
 
 View user's profile Send private message  
Reply with quote Back to top
douglasmhurst
Post subject:   PostPosted: Oct 10, 2011 - 03:51 PM
Registered Member
Registered Member


Joined: Sep 30, 2006
Posts: 274

to answer your other question, At work, our WSs are developed using Axis2 and are deployed on WebSphere App Server 6.1.0.31.

Out clients should be able to use any valid SOAP means to produce a WS client provided the WSDL is valid. I assure you this WSDL is a valid 1.2 SOAP WSDL.
 
 View user's profile Send private message  
Reply with quote Back to top
douglasmhurst
Post subject:   PostPosted: Oct 10, 2011 - 05:43 PM
Registered Member
Registered Member


Joined: Sep 30, 2006
Posts: 274

I just discovered that if I continue on with the generation, even with the errors, and ignore the warning about ...

SOAP port "FPProcessHttpSoap12Endpoint": uses a non-standare SOAP 1.2 binding.

... that I can create a Class that uses the output to successfully connect to the Axis2 based Web Service.

So, I guess you can close this issue, but there's no reason to get those errors on a valid WSDL... just because it wasn't produced from within MyEclipse.
 
 View user's profile Send private message  
Reply with quote Back to top
support-tony
Post subject:   PostPosted: Oct 11, 2011 - 04:11 AM



Joined: Mar 09, 2011
Posts: 916

Douglas,

Thanks for the posts and attachments. I should have mentioned that the client wizard allows you to ignore some potential problems. Some tools and frameworks tend to be more tolerant of standards issues than others, but there could, of course, be problems with the validation.

I quickly generated an Axis2 service on the eclipse JEE platform and the MyEclipse web services explorer reported that SOAP 1.2 was not supported, although the 1.1 interface worked fine. I'll check this out a bit more, with the WSDL you supplied and will post if I find anything.

_________________
Tony
MyEclipse Support
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 6 Hours
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.
View previous topic Printable version Log in to check your private messages View next topic
Powered by PNphpBB2 © 2003-2004 The PNphpBB Group
Credits