Imports WSDL

[Alexis Midon <al...@gmail.com>]

Hi Matthieu,

now I am a little more familiar with Twister, could you give me more 
precisions (requirements) on the feature "import wsdl".
Tell if I misunterstood but the goal is to implement the <import> tag WSDL?

So some wsdl files must be importable and a main wsdl file using these 
definitions deployable?

can you create the corresponding issue in Jira? or may be it is 
http://issues.apache.org/jira/browse/AGILA-11?

Re: Imports WSDL

[Matthieu Riou <mr...@gmail.com>]

Hi,

Actually the goal is to avoïd having to create a WSDL document for
each deployed process. Let's say you have 10 web services and also 10
processes. All your processes use several and sometimes even all of
the web services. Right now you'll have to build 10 other WSDL
documents by copying and pasting the content of your web services WSDL
docs to match those needed by your processes. And then you'll be able
to deploy the aggregated WSDL and the BPEL doc. It would be much
better if the users could simply deploy the WSDL documents of their
web services "as is" and then deploy their process by referencing
these WSDL documents. That would eliminate the cumbersome task of
aggregating the WSDL docs to another doc specific to the process.

To answer to this requirement I can see possibly 2 solutions:

1. Build the "process-specifc WSDL" document by importing the "atomic"
web services docs. You still have to build your "process-specific
WSDL" but it only contains WSDL imports referencing the needed
services definitions.
2. When writing your BPEL process, services (basically messages,
portTypes and operations) are namespace referenced. We could simply
use these namespaces to pick all necessary WSDL docs previously
deployed.

From a user prospective I rather the second solution, as there's even
less XML to write and documents to deal with than in the first one.
Yet I believe we will still need to support WSDL imports as some users
might want to use them.

So if everybody agrees, I believe we should focus on the first
solution first and then when the requirement will be fulfilled,
introduce support for WSDL imports for the users wanting to use them.
What do you think?

Anyway you will have to look into Agila BPEL's deployed module to see
what is happening. A WSDL doc is simply validated and saved upon
deployment. When a BPEL document is deployed, we then try to locate
its WSDL (only one specific doc right now) and with both docs create
the necessary structures in the engine. The algorithm is then based on
delegation. A factory locates the right ???Deployer class depending on
the XML node type, this node-specific deployer does his job and then
calls back the factory if there are any subnodes to process. And so
on...

Let me know if you need more...

Cheers,

Matt.

On 5/16/05, Alexis Midon <al...@gmail.com> wrote:
> 
>  Hi Matthieu,
>  
>  now I am a little more familiar with Twister, could you give me more
> precisions (requirements) on the feature "import wsdl".
>  Tell if I misunterstood but the goal is to implement the <import> tag WSDL?
>  
> So some wsdl files must be importable and a main wsdl file using these
> definitions deployable?
>  
> can you create the corresponding issue in Jira? or may be it is
> http://issues.apache.org/jira/browse/AGILA-11?
>  
>  
>