Re: [infinispan-dev] [jboss-dev] Infinispan configuration - all in one solution

You mean JAXB by design or the JAXB implementation you have tried? On Jul 17, 2009, at 14:47, Adrian Cole wrote: The only problem with using jaxb is that it doesn't work in google app engine. Switching to jaxb implies adding another roadblock on the way to gae/j support. This is the only reason I'm not using jaxb for jclouds, even though it would make things simpler. -Adrian On Fri, Jul 17, 2009 at 5:38 PM, Vladimir Blagojevic <vblagoje(a)redhat.com&gt;wrote: > On 7/17/09 5:16 PM, Bill Burke wrote: > > Wouldn't it be better to write a javadoc-like generator that > > introspected for JAXB and Inifispan annotations instead of writing your > > own XML parser and schema generator? Or maybe I'm misunderstanding your > > post. > > > > In other words, use JAXB for marshalling/unmarshalling/schema > > generation. Use inifinispan javadoc generator for documentation. > > > I looked around a bit more to see that now in JAXB 2.x we have > annotations as well :) If we annotate our configuration beans with JAXB > annotations I suppose we can do exactly what you suggest - use JAXB for > marshalling/unmarshalling/schema generation and at the same time use > those annotation in a custom tool that creates reference documentation. > > By creating your own XML parsing you've just complicated the maintenance > > problems for future maintainers of infinispan. > > > I agree. > > Cheers, > Vladimir > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev > _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev