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.<br>
<br>-Adrian<br><br><div class="gmail_quote">On Fri, Jul 17, 2009 at 5:38 PM, Vladimir Blagojevic <span dir="ltr"><<a href="mailto:vblagoje@redhat.com">vblagoje@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 7/17/09 5:16 PM, Bill Burke wrote:<br>
> Wouldn't it be better to write a javadoc-like generator that<br>
> introspected for JAXB and Inifispan annotations instead of writing your<br>
> own XML parser and schema generator? Or maybe I'm misunderstanding your<br>
> post.<br>
><br>
> In other words, use JAXB for marshalling/unmarshalling/schema<br>
> generation. Use inifinispan javadoc generator for documentation.<br>
><br>
</div>I looked around a bit more to see that now in JAXB 2.x we have<br>
annotations as well :) If we annotate our configuration beans with JAXB<br>
annotations I suppose we can do exactly what you suggest - use JAXB for<br>
marshalling/unmarshalling/schema generation and at the same time use<br>
those annotation in a custom tool that creates reference documentation.<br>
<div class="im">> By creating your own XML parsing you've just complicated the maintenance<br>
> problems for future maintainers of infinispan.<br>
><br>
</div>I agree.<br>
<br>
Cheers,<br>
Vladimir<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</blockquote></div><br>