I wouldn't say this is the recommended way to do it, but it's a perfectly valid approach. You can either start from the wsdl and schema as you are (which is what I'm doing) or you can start from the java side and generate the wsdl and schema. Both are valid approaches. I have found that since I'm using Doc Literal, I'm better off to hand write my wsdl and schema. If you were using RPC, you might want to consider starting with Java. Axis seems to do a very clean job of generating the appropriate wsdl and schema from java classes if you are using RPC.
-----Original Message----- From: Marepalli, Somesh [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 10:25 AM To: [EMAIL PROTECTED] Subject: RE: Axis and XML schema.... The approach we have been trying has been to use Apache Axis 1.1. The way we are currently attempting this is as follows: a) Define an initial WSDL document for web service operations using the XML schema b) Use Apache Axis to generate service interface and bean classes c) Implement service layer logic d) Publish and deploy it again using Axis Is this the recommended way per your experience.... -----Original Message----- From: Heitzeg, Bill [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 10:22 AM To: [EMAIL PROTECTED] Subject: RE: Axis and XML schema.... I have had good luck with operations built using a wsdl and a schema, but I've never been able to get attributegroup to work. I think it's an Axis bug. I haven't spent a huge amount of time on it, since I didn't really need it. From what I can tell Axis doesn't generate the java datatypes for attributegroup, but it does generate the type mapping for them in the wsdd. Other than that problem, I've been able to generate good skeleton code using schemas and a wsdl. I hope this helps. Bill Heitzeg -----Original Message----- From: Marepalli, Somesh [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 10:11 AM To: [EMAIL PROTECTED] Subject: Axis and XML schema.... Hi: I am trying to work with an elaborate XML schema which uses type derivation, attributeGroup etc in the XML schema language... I am using Axis with my WSDL spec to define operations using the schema types...I find the following problems: a) Axis seems to be ignoring valid XML schema constructs like attributeGroup when generating the Java bean classes b) Is Axis well -suited for operations build around an XML schema types...What is the correct way to leverage both. At present, it looks like we are using the schema types to generate bean classes and not for any validation. Any advice here would help... regards Somesh Marepalli [EMAIL PROTECTED]
