Team,
We had previously discussed implementing a default JAXB context resolver to
better hand JAXB contexts. As far as I can tell, there are no default
"system" context resolvers loaded in WINK; only the context resolvers
defined by an application are available. For JAXB, however, it might make
sense to provide a default.
As a proof of concept, I put a context resolver in wink-common at
org.apache.wink.common.contexts.resolver.JAXBContextResolver
And added the following to
wink-common/src/main/resources/META-INF/core/wink-providers
# Context Resolvers
org.apache.wink.common.contexts.resolver.JAXBContextResolver
I poked around in the debugger a bit just to see how everything got loaded
up. It looked to me like the context resolvers were loaded in the correct
order. My sample also picked up the right provider with this context
resolver in place as well.
I'd like to hear opinions on this... or if you wish, I can work on building
up a sample to demonstrate value. I figured I'd pose the idea here on the
mailing list instead of a Jira to get a sense of what we want or need.
I think the value-add is that JAXB has a very standardized way of
processing data, and it's clear when we should be working with JAXB
objects, so an app should not necessarily be responsible for including
their own JAXB context resolver.
Any thoughts, concerns, objections?
Thanks..
mike
