Re: [Axis 1.4] Eclipse does not like WSDL
Because it's difficult to always generate perfect WSDL. The Java2WSDL tool is a crutch. You occasionally need to edit the generated WSDL. I strongly recommend that you switch to "wrapped" style. In Java2WSDL, specify the following two switches: -y, --style WRAPPED The style of binding in the WSDL, either DOCUMENT, RPC, or WRAPPED.-u, --use LITERAL The use of items in the binding, either LITERAL or ENCODED AnneOn 6/19/06, Neil Aggarwal <[EMAIL PROTECTED]> wrote: Annie: This WSDL was generated from Axis 1.4, not by me. Why would Axis generate bad code in the WSDL? Neil --Neil Aggarwal, JAMM Consulting, (214)986-3533, www.JAMMConsulting.comFREE! Valuable info on how your business can reduce operating costs by17% or more in 6 months or less! http://newsletter.JAMMConsulting.com From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] Sent: Monday, June 19, 2006 7:44 PMTo: axis-user@ws.apache.org Subject: Re: [Axis 1.4] Eclipse does not like WSDL There are a couple of minor errors with the WSDL.1- you never reference the "http://lang.java" namespace, therefore there's no need to declare it or import it. You don't specify a schemaLocation for the namespace, hence you get the schema_reference error. I'd remove it. 2- Fault messages should always be defined as literal elements rather than encoded types. But Axis is forgiving and manages to encode it for you anyway.I don't understand why Eclipse is complaining about the SAXException type, because it appears to be defined properly, although perhaps it's objecting to the fact that you didn't provide a schemaLocation for the " http://schemas.xmlsoap.org/soap/encoding/" namespace.I strongly encourage you to not use SOAP encoding, though. I suggest you switch to wrapped document/literal. Anne On 6/16/06, Neil Aggarwal <[EMAIL PROTECTED]> wrote: > Please post the WSDLI am attaching it here.--Neil Aggarwal, JAMM Consulting, (214)986-3533, www.JAMMConsulting.comFREE! Valuable info on how your business can reduce operating costs by 17% or more in 6 months or less! http://newsletter.JAMMConsulting.com- To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis 1.4] Eclipse does not like WSDL
Annie: This WSDL was generated from Axis 1.4, not by me. Why would Axis generate bad code in the WSDL? Neil --Neil Aggarwal, JAMM Consulting, (214)986-3533, www.JAMMConsulting.comFREE! Valuable info on how your business can reduce operating costs by17% or more in 6 months or less! http://newsletter.JAMMConsulting.com From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 7:44 PMTo: axis-user@ws.apache.orgSubject: Re: [Axis 1.4] Eclipse does not like WSDL There are a couple of minor errors with the WSDL.1- you never reference the "http://lang.java" namespace, therefore there's no need to declare it or import it. You don't specify a schemaLocation for the namespace, hence you get the schema_reference error. I'd remove it. 2- Fault messages should always be defined as literal elements rather than encoded types. But Axis is forgiving and manages to encode it for you anyway.I don't understand why Eclipse is complaining about the SAXException type, because it appears to be defined properly, although perhaps it's objecting to the fact that you didn't provide a schemaLocation for the " http://schemas.xmlsoap.org/soap/encoding/" namespace.I strongly encourage you to not use SOAP encoding, though. I suggest you switch to wrapped document/literal. Anne On 6/16/06, Neil Aggarwal <[EMAIL PROTECTED]> wrote: > Please post the WSDLI am attaching it here.--Neil Aggarwal, JAMM Consulting, (214)986-3533, www.JAMMConsulting.comFREE! Valuable info on how your business can reduce operating costs by 17% or more in 6 months or less! http://newsletter.JAMMConsulting.com-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 1.4] Eclipse does not like WSDL
There are a couple of minor errors with the WSDL.1- you never reference the "http://lang.java" namespace, therefore there's no need to declare it or import it. You don't specify a schemaLocation for the namespace, hence you get the schema_reference error. I'd remove it. 2- Fault messages should always be defined as literal elements rather than encoded types. But Axis is forgiving and manages to encode it for you anyway.I don't understand why Eclipse is complaining about the SAXException type, because it appears to be defined properly, although perhaps it's objecting to the fact that you didn't provide a schemaLocation for the " http://schemas.xmlsoap.org/soap/encoding/" namespace.I strongly encourage you to not use SOAP encoding, though. I suggest you switch to wrapped document/literal. Anne On 6/16/06, Neil Aggarwal <[EMAIL PROTECTED]> wrote: > Please post the WSDLI am attaching it here.--Neil Aggarwal, JAMM Consulting, (214)986-3533, www.JAMMConsulting.comFREE! Valuable info on how your business can reduce operating costs by 17% or more in 6 months or less! http://newsletter.JAMMConsulting.com-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 1.4] Eclipse does not like WSDL
> Please post the WSDL I am attaching it here. -- Neil Aggarwal, JAMM Consulting, (214)986-3533, www.JAMMConsulting.com FREE! Valuable info on how your business can reduce operating costs by 17% or more in 6 months or less! http://newsletter.JAMMConsulting.com FileUpload.wsdl Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis 1.4] Eclipse does not like WSDL
Is the WSDL rpc/encoded or wrapped document/literal ? If it is rpc/encoded does it contain "soapenc:string" vs. "xsd:string" for the type attribute value Use the -T 1.1 option on the Java2WSDL to generate JAX-RPC style. -Original Message-From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]Sent: Friday, 16 June 2006 10:42 AMTo: axis-user@ws.apache.orgSubject: Re: [Axis 1.4] Eclipse does not like WSDLPlease post the WSDL. On 6/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote: Hello:I deployed a simple web service using Axis 1.4 on Tomcat 5.5.17.When I downloaded the WSDL into a project to build a clientusing the Eclipse IDE, I get these errors from Eclipse:schema_reference.4: Failed to read schema document 'http://lang.java ',because 1) could not find the document; 2) the document could not be read;3) the root element of the document is not .The part 'fault' has an invalid value 'SAXException' defined for its type. Type declarations must refer to valid values defined in a schema.They dont seem to interfere with using the WSDL. I can generatemy classes and write the client just fine.Any ideas on these?Thanks, Neil--Neil Aggarwal, JAMMConsultingwww.JAMMConsulting.com, 214-986-3533- To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 1.4] Eclipse does not like WSDL
Please post the WSDL.On 6/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:Hello:I deployed a simple web service using Axis 1.4 on Tomcat 5.5.17.When I downloaded the WSDL into a project to build a clientusing the Eclipse IDE, I get these errors from Eclipse:schema_reference.4: Failed to read schema document 'http://lang.java ',because 1) could not find the document; 2) the document could not be read;3) the root element of the document is not .The part 'fault' has an invalid value 'SAXException' defined for its type. Type declarations must refer to valid values defined in a schema.They dont seem to interfere with using the WSDL. I can generatemy classes and write the client just fine.Any ideas on these? Thanks, Neil--Neil Aggarwal, JAMMConsultingwww.JAMMConsulting.com, 214-986-3533- To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
