Re: [bpel-dev] Parsing BPEL+WSDL specifications

[Damien Thivolle <damien.thivolle@xxxxxxxx>]

Simon D Moser a écrit :
> Hi Damien,

Simon, Milinda, thank you for your answers.


> alternatively, if you have specific requirements against the tree that you
> want to get out of this, you could also take the BPEL EMF model (available
> from the BPEL Designer Project). I parses a BPEL XML into an EMF in-memory
> model, and then you can write a "translation" yourself to whatever tree
> format you need. However, I agree with Milinda, if what you are looking for
> is an abstract syntax tree like in any modern compiler, you can probably go
> with the ODE BPEL compiler (but no one on this mailing list is probably
> familiar enough with this thing, so it's really the best option to repeat
> this question on the ODE mailing list).

I know about that EMF metamodel. It is the first solution I looked at 
but the BPEL metamodel and the WSDL metamodel come from two different 
projects, BPEL Designer and WST, so I assumed that I would need to use 
the tools from both projects to parse a BPEL process definition and the 
WSDL definitions it depends on.

Then there is also the problem of the presence of partnerLinkTypes 
definitions in WSDL files included by BPEL definitions. I do not think 
that the WSDL parser from WST understands partnerLinkType definitions so 
I am basically looking for the best off the shelf solution that would 
allow me to get a syntax tree (that includes WSDL definitions) from a 
BPEL process definition.

I will now take a look at the ODE BPEL compiler.

Thank you again and best regards,

--
Damien Thivolle