RE: Loading external schemas into WSDL... (PATCH included)

[Douglas Bitting <Do...@agile.com>]

Tom,

Thanks for the reply.  I did see the static WSDL support.  However, it looked like specifying static WSDL defeated any and all WSDL generation.  There
are certain aspects of the WSDL generation that I do not want to override.  Specifically, the
"/wsdl:definitions/wsdl:service/wsdl:port/wsdlsoap:address" element should always use the request URL as the basis for specifying the location
attribute.  If I specify a static WSDL, then this dynamic generation of the "wsdlsoap:address" element is defeated, which is a significant issue for
me (I'm delivering pre-packaged web services, but don't control where they are deployed).

Perhaps another mechanism for acheiving my goal is to include some directive that indicates that the wsdlsoap:address element should always be
dynamically generated, even if the element is present in statically defined WSDL.

Is one approach better than the other?  I would never describe myself as a WSDL expert, so I couldn't tell if one approach was signicantly more
challenging/risky/useful than the other.

I'm having trouble w/ Bugzilla at the moment, but attached please find the necessary diffs to include the functionality described in my original
email.  Please let me know if you'd like me to also post this to Bugzilla once I'm able...

Please Note: The set of patches attached to this message also contains one other minor fix.  Namely, when setting up the emitter w/in
providers.java.JavaProvider (line ~450 of v1.89), the TypeMapping was always setup for Constants.URI_DEFAULT_SOAP_ENC.  However, I think this is in
error and that it should be setup for style.getEncoding() since the default encoding for doc/lit services is "".

Thanks,
--Doug


-----Original Message-----
From: Tom Jordahl [mailto:tomj@macromedia.com]
Sent: Tuesday, October 22, 2002 6:33 AM
To: 'axis-dev@xml.apache.org'
Subject: RE: Loading external schemas into WSDL...


Doug,

We already provide a way for services to specify a static WSDL file in place of the generated version, which may meet the needs of people like
yourself who would like to customize the WSDL in various ways.

That being said, I don't have any real objection to giving users the ability to add include schemas in generated WSDL.  

Note that I recently added an --extraClasses switch and API to the WSDL generator to generate Schema for extra Java classes, but did NOT add this
option to the service WSDD.  Perhaps it needs to be added to the WSDD, and that would satisfy 90% of the cases.

--
Tom Jordahl
Macromedia Server Development



-----Original Message-----
From: Douglas Bitting [mailto:Douglas.Bitting@agile.com]
Sent: Saturday, October 19, 2002 12:22 PM
To: axis-dev@xml.apache.org
Subject: Loading external schemas into WSDL...


Hi.

I have a question about how to go about including externally-generated schemas into the Axis-generated WSDL.  Basically, I've put together a
thoroughly-documented (via annotations) schema, which I'd like to physically include in the WSDL Axis generates.  However, I'm not exactly sure how
best to go about this.

I've put together some modifications that allow for the following WSDD construct:

  <service name="..." ...>
    <parameter name="wsdlInputSchema" value="<some-url-here>"/>
  ...

This causes the referenced schema to be physically included into the generated WSDL.  Is there already some support for this type of thing in Axis
that I didn't see?  Am I going about this in an odd fashion?  Should I do it differently?

If the above mechanism turns out to be a good way to handle this, I'll be happy to submit the modifications.  What do you guys think about this?

Cheers,
--Doug

Doug Bitting
Agile Software
1 Almaden Blvd
San Jose, CA  95113
(408) 999-7120