Hi, Pradeep.
In Tuscany, we normalize the interface definitions from different IDLs such
as Java, WSDL 1.1 and potentially WSDL 2.0, CORBA IDL into the
Interface/Operation model. There is code in Tuscany to populate these models
from a WSDL file (using WSDL4J).
I assume the W2J tool would need to build a model for the WSDL first. What I
proposed is to develop the WSDL2Java tool based on the Interface/Operation
model instead of loading the WSDL using a different model. The tool can then
navigate the Interface/Operation to generate the corresponding java
artifacts such as interfaces and methods. But I'm open to alternative ideas.
Thanks,
Raymond
From: Pradeep Fernando
Sent: Monday, March 30, 2009 9:02 AM
To: [email protected]
Subject: Re: GSOC[2009] WSDL2Java tool for Tuscany
hi devs/raymond,
raymond wrote:
The other approach is to start with Tuscany's Interface/Operation/DataType
model. We already have code at runtime to create a neutral Interface for
WSDL portTypes
I went through the source code you have pointed. honestly dont have a clear
idea at the moment. could you please elaborate what you have told in the
last post. It sounds like you are asking me to fetch the data from a kind of
object model that tuscany already has instead from the WSDL itself. this
sounds odd to me. plz correct me if Im wrong .
thanks,
Pradeep Fernando.
