axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From NY...@aol.com
Subject Re: Schema generation in Axis?
Date Thu, 01 Jul 2004 08:55:06 GMT
 
I believe you can use namespaces to do such a thing. Isn't that precisely  
what namespaces are for?
 
I'm not a pro, but I've been hacking away at Axis for some time now and I  
figured I'd give a tiny bit of input.
 
James
 
In a message dated 7/1/2004 8:52:30 AM Eastern Standard Time,  
axis@nospam.websolver.dk writes:

Hi Anne
 
Sorry for interferring in the discussion... hope  it is ok.
 
I am about to define a "schema model",  a collection of schemas with types 
that can be shared across web services, eg.  imported into WSDLs
 
Is it possible for WSDL2Java to generate the  proxy for the schema to one 
package, say org.me.schemamodel,  and the proxy for the service to another 
package, say org.me.ws?
If so, would WSDL2Java take into account  that the proxy for the schema, say 
"user", has already been generated if  two WSDLs imports the schema for "user".
 
Reason for asking is that a someone on the  .NET newgroups discussed this 
earlier...NET (in the current version), doesn't  handle this very well, eg. you 
get a new proxy class each time a  import element in the WSDL is 
processed...You end up having User1Proxy,  User2Proxy, etc...for the same schema...
 
This might be a namespace problem...I  don't know..Do you..Anyone?
 
Thanx in advance...
 
Henrik
 

----- Original Message ----- 
From:  _Anne Thomas  Manes_ (mailto:anne@manes.net)  
To: _axis-user@ws.apache.org_ (mailto:axis-user@ws.apache.org)  
Sent: Thursday, July 01, 2004 2:35  PM
Subject: RE: Schema generation in  Axis?



Currently Axis does  not generate a reusable schema that’s separate from the 
WSDL. Instead it  generates a types section within the WSDL file. If you would 
like the option  of generating a separate schema definition, then you should 
file an  enhancement request. For example, provide a switch on java2wsdl that 
permits  you to generate a separate .xsd file or to use a  specified .xsd 
file. As a result, Axis would  generate a separate .xsd file and then import that  
file into the WSDL using the command that James refers to  below. 
Anne 
 
  
____________________________________
 
From:  NYY96@aol.com [mailto:NYY96@aol.com] 
Sent: Thursday, July 01, 2004 5:10  AM
To: axis-user@ws.apache.org
Subject: Re: Schema generation in  Axis?
 
 
In all likelihood  I did not understand your question, however you can import 
a schema using  the following statement:
 

 
<wsdl:import  namespace="<path to web service namespace>"  
location="<schemaname>.xsd"/>
 

 
James
 

 
In a message dated  7/1/2004 8:07:54 AM Eastern Standard Time, 
jeff.deppen@paytec.com  writes:

All,

I'm  designing/developing multiple web services which share a  common
"library" of data types (classes).  When I deploy the  services, the
Axis-generated WSDL "files" include the complete  definition (schema) of each
type - i.e. each complex type is  "re-defined" in the <wsdl:types><schema>
node.  Now,  here's my question:  is there a way to have Axis generate a
schema  file/definition which is imported by each WSDL instead of  definining
each type (again and again) within each  WSDL?

thanks
jeff

 








Mime
View raw message