On Wed, 5 Sep 2001, Sam Ruby wrote: > Giacomo wrote: > > > > Well, some of my vision may be overlapping with the Axis vision. But how > > is it related to generate JAXB compliant objects (in general I mean > > objects that can marshall/unmarshall itselfs) for the WSDL types? In my > > opinion this will increase the use in Cocoon, but I have no idea for > > Axis. Such a code generator will enable us to describing SOAP messages > > in general. At my company we've developed a XML Schema to Java toolkit > > to get XMLizable java objects exactly for that (different architecture > > that JAXB though). > > We already have a WSDL to Java code generator. It has primitive XML schema > support today and somebody working on handling more complex cases. > > >> How can I help? > > > > I thought of starting a separate project for that because parts of it > > are not tightly bound to Cocoon2. They can be use in general (XML-Schema > > -> java source according to JAXB). If some Axis people will join we can > > build up a toolset that satisfies all (and now my Avalon bias mind sees > > pluggable generator components :). > > I read you correctly, the intent of Axis is to be such a toolkit. Before > we talk about the segregation into projects, lets figure out what needs to > be done. Sorry, I probably missunderstud your analogy SOAP -> Axis is like Cocoon 1 -> Cocoon 2, and so I thought Axis is the next generation SOAP, not a toolkit for different things like what I've envisioned. Giacomo > > - Sam Ruby > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
