Where I work we have a large IT shop and have many schemas that have a lot of duplication. I'm not a big fan of maintaining XML in say an XML repository (since we primarily operate in Java). Instead of an XML repository I'm thinking that it would be easier to maintain JAX-B objects.
I'm wondering if anyone has this kind of setup where you maintain and share JAX-B objects across your enterprise. So if someone was doing a JAX-WS service that needed to use a common object like for example Address, then they would include that common jar via a build tool that can manage dependencies. Address in this case could be built by someone following some ISO standard or it can be an object that is internal to your enterprise that was built by a team inside your organization.
I tried doing various searches but couldn't find anything so I decided to post here to see if I can get any feedback. If anyone could share any pros/cons that are currently doing this I would very much appreciate it!
No comments:
Post a Comment