I'd like this api to capture the full xml infoset if possible.
What I mean is that there are places in the bpel schema where extensions
are permitted (attributes and/or elements), and I think it could be
usefull to keep then (instead of just ignoring them).
So I think both modules could be enhanced ...
Alternatively, this could be easily handled by an xml / object mapping
tool like jaxb2 (or xmlbeans) ...
Jaxb2 is very simple, generates nice pojos (this is not the case with
xmlbeans) and afaik, both handles unspecified extensions to schemas...
Or even a stax based parsing would be great (sax is such a nightmare
compared to pull parsing..).
Guillaume
Matthieu Riou wrote:
Hi,
In parrallel with the discussion on integration API I wanted to
suggest working on the BPEL parser (takes XML and spits out objects)
and the BPEL object model (produced by the parser, used by the
compiler that will produce something close to the internal engine
model).
This is a fairly neutral part as it should just stick to the spec so I
guess that's a good point to start. PXE seems to have two simple
modules for that, using SAX for parsing. As a starting point we could
take these and import them from scratch to trunk.
What do you think?
Cheers,
Matthieu.
