Werner, Adding a data binding to CXF is not quite trivial, but the interfaces required are reasonably well-bounded. If I were going to do it, I'd start by reading the Aegis code (since I rewrote a lot of it), but there's also the xmlbeans binding to look at.
I'm not quite sure where to start in telling you where to start. If I said, 'Check out the current CXF trunk from SVN, and look at the rt/databinding/aegis project,' I don't know if I'd be insulting your intelligence. I could also send along a quick explanation of the major interfaces involved. On the positive side, a Castor binding would be a wonderful thing insofar as it could do wsdl2java, which Aegis cannot. I'm probably being confused about licensing. I'm fairly new to the Apache scene. There are some components (e.g. Xom) that we cannot use in CXF due to Apache licensing rules. --benson On Thu, May 29, 2008 at 3:54 AM, Werner Guttmann <[EMAIL PROTECTED]> wrote: > Hi, > > Benson Margulies wrote: > > I'm a CXF committer and I'm kind of the current foster-parent of the > Aegis > > binding. > > > > Since CXF has to be able to deliver a WSDL, and a WSDL has to include > > schema, we'd need that. I've barely scratched the surface of castor, but > > other than that it looks quite straightforward. > Yes, it does .. ;-). > > Okay, where to start. There's a few tools out there for which there's > some level of Castor integration, e.g. Spring-WS, Apache Cocoon, XFire, > Mule, etc. Most of these tools tend to use the XML data binding > functionality of Castor only. Some of those glue code bits have been > provided by myself .. ;-). > > > If you/we wanted to do wsdl2java, then someone would have to deal with > the > > 'tooling', which is more complex, and connect it to your code generator. > Sure. What would you propose ... ? > > > > there's also the question of license compatibility if you wanted to > > contribute it to CXF. > In what sense ? > > > Please don't say, 'JAXB'-compatible :-) JAXB has a number of unfortunate > > aspects, I'd hope you all do better. > Yes, it has, but you have to make a difference between a specification > and the reference implementation. And yes, you are correct that even the > spec is somewhat ill-designed with regards to some aspects. > > But when I use the term 'JAXB compliance', it does not imply that the > remainder of Castor (nnot covered by the JAXB spec, but very useful) > will vanish .. ;-). > > Werner > > > > On Wed, May 28, 2008 at 4:09 PM, Ralf Joachim <[EMAIL PROTECTED]> > > wrote: > > > >> Hi Benson, > >> > >> you seam to have investigated CXF. > >> > >> What would be required for a CXF binding for Castor? > >> > >> Are you in a position to contribute that? > >> > >> Regards > >> Ralf > >> > >> > >> Benson Margulies schrieb: > >>> I'd certainly test it. > >>> > >>> Changing the subject, I also wonder if someone would like to see a CXF > >>> data binding for Castor. That feature would be an important enabler of > a > >>> code-first Castor data binding for CXF. > >>> > >>> On Wed, May 28, 2008 at 3:12 PM, Joachim Grüneis <[EMAIL PROTECTED] > >>> <mailto:[EMAIL PROTECTED]>> wrote: > >>> > >>> Hello > >>> > >>> currently: not really > >>> > >>> there is a way to create a schema for a XML file... but that isn't > >> the > >>> same then using the Java classes as a base > >>> > >>> one of our Google Summer of Code students is currently working to > >>> implement the feature you like to have... but you have to wait > >>> > >>> do you like to help us? e.g. by testing the new feature? > >>> > >>> Have fun > >>> > >>> Joachim > >>> > >>> 2008/5/28 Benson Margulies <[EMAIL PROTECTED] > >>> <mailto:[EMAIL PROTECTED]>>: > >>> > I've got a set of classes that I'm planning to marshal and > >>> unmarshal with > >>> > with Castor. I don't have any mapping files (yet) -- I'm not very > >>> picky > >>> > about how they get marshalled. > >>> > > >>> > Is there some way to get Castor to spit out an XML Schema so that > >>> I can > >>> > create XML documents in some other tool that can be unmarshalled > >>> into these > >>> > objects? > >>> > > >>> > > >>> > >>> > --------------------------------------------------------------------- > >>> To unsubscribe from this list, please visit: > >>> > >>> http://xircles.codehaus.org/manage_email > >>> > >>> > >>> > >> --------------------------------------------------------------------- > >> To unsubscribe from this list, please visit: > >> > >> http://xircles.codehaus.org/manage_email > >> > >> > >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
