On 7/17/07, Jochen Mader <[EMAIL PROTECTED]> wrote: > I also agree with the opinion that a code generator would harm the > overall readability of everything. > If people want to have XSLT I'd propose a JAXB approach. > With JAXB we could annotate the java classes we already have and > generate XSLT documents from these annotations. > The advantage of this would be that all XML-elements are bound to beans > and changes to the XSLT can be done while editing the source code. > The resulting XSLT can then be used by any other XSLT capable language. > > Cheers > Jochen >
Beans? Can you elaborate on this approach (if possible use the Common Tongue as some of us aren't Java guys). Are you suggesting scattering some of the code generation across many Java classes? Since presumably the Java code (and therefore these XSLT fragments) is generated initially from llrpdef.xml I am not sure how that resolves any maintainability problems. This is getting too abstract, I need an example :-) -- John. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
