I've been thinking about how StAX would fit with Woden. There are two possible designs:
1. Woden use StAX to read WSDL 2.0 & XSD, and builds up a complete Component Model. There is no DOM in memory but there is a complete Component Model in memory. 2. Woden uses StAX to read WSDL 2.0 & XSD, but does not build up a Component Model in memory. Instead, Woden fires a Component Model event stream that Axis2 listens to and does whatever is needed. There is no Component Model build up in memory here. What is the requirement from Axis2? On 3/23/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Sanjiva Weerawarana wrote: > > > I'd love to get off WOM and get onto Woden but we have two key needs to > > do that: Woden needs to have a StaX (or AXIOM) builder and it must > > support WSDL 1.1 also. > > > > > WSDL 1.1 is really a need for ServiceMix too, but I guess we will be > able to keep both wsdl4j and > woden at the same time until Woden handles WSDL 1.1. > > Btw, I 'm wondering about the need for a StaX based Woden parser. > AFAIK, even WS-Commons > XMLSchema only supports DOM, and I do not really see the need for a StaX > based WSDL parser. > This would of course alleviate the need to build the DOM in memory, but > apart from that ... > And having a parser based on AXIOM would imho not be a good idea, as it > would put a strong > dependency on AXIOM in the public interfaces. > > Cheers, > Guillaume Nodet > > > --------------------------------------------------------------------- > 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]
