Hi Pavel,
Thanks for your reply and sorry the question I asked is vague.
My aim:
I have a Java lib project (let's call it A) which takes care of biz logic
and also includes all JAXB beans.
I also have another project (let's call it B) that calls methods in project
A( the method output is always JAXB beans) and handles Restful Web Services.
It is basically a thin wrap of the Java lib.
Now I am building the third project (let's call it C) which requires a
slightly different set of xml/json output. So the idea solution for me is to
not have all JAXB annotations embedded in the JAXB bean code but in an
external file shipped with project B or C.
Any suggestions?
--
View this message in context: http://jersey.576304.n2.nabble.com/Does-Jersey-support-jaxb-external-customization-tp5316922p5329965.html
Sent from the Jersey mailing list archive at Nabble.com.