Lou Amodeo wrote:
Along these same lines, I am looking to emit, as a file, the WSDL required
for client development. This needs to be emitted prior to the start of the
service so obtaining it from ?wsdl is not feasible. It appear that the
post-processing is applied to the WSDLDefinition rather than the byte stream
populated by Java2WSDLBuilder containing the wsdl document. Is there a way
to write out the WSDL document containing the post-processing with the
assumption that the post-processing on the WSDLDefinition is essential from
a clients perspective?
The steps to do this would be as follows:
1. Start with the WSDL interface contract.
2. From this, you can get the WSDL interface.
3. From this, you can get the Tuscany WSDLDefinition.
4. From this, you can get the WSDL4J Definition.
5. Create a WSDLWriter using
javax.wsdl.factory,WSDLFactory.newInstance().newWSDLWriter().
6. Use the WSDLWriter to write the Definition to a Writer or
an OutputStream.
Simon
On 1/30/08, Scott Kurz <[EMAIL PROTECTED]> wrote:
I was looking over the runtime Java2WSDLHelper code to get some
understanding of it.
After we build the WSDL with the call to: builder.generateWSDL();
I was wondering what we're doing post-gen to the WSDL types section?
What's the code calling readInlineSchemas() doing?
Is that code in there purely to collect the schema information to
build Tuscany interface/operation/model objects? Or is there
maybe an issue/bug in the Axis2 J2W that we're massaging over?
Hopefully someone who knows wouldn't mind explaining that at a bit of
a higher level.
Thanks,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
