Hi,
I've recently started using JibX - really useful, thank you.
But, of course, I have a question. I sense there may be several ways to
accomplish what I wish to do and I would appreciate guidance on the
"best practice" way. Here is what I would like to accomplish:
I have a complex, custom Java object. I receive an xml representation of
it (actually a subset of it.) I can parse the subset without a problem.
I now wish to produce another xml representation of it (same object) but
publishing different facets of it. Structurally the resultant xml would
look different than the input xml: meta data inserted, aggregation
performed, some field elided.
In this specific situation, it makes sense to maintain a single object
with multiple views. Is there a "best practice" jibx approach?
Thanks,
Bill
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
