Description Rick Barkhouse 2012-01-12 14:53:40 EST

When using the Sun JAXB implementation, users specified a custom IDResolver as follows:

unmarshaller.setProperty("com.sun.xml.bind.IDResolver", new MyIDResolver());
or
unmarshaller.setProperty(IDResolver.class.getName(), new MyIDResolver());

where IDResolver is com.sun.xml.bind.IDResolver, and MyIDResolver is an implementation of that interface.

For MOXy, an equivalent interface was created, org.eclipse.persistence.jaxb.IDResolver, and the user's custom resolver class must implement that MOXy interface.

If we want the user to be able migrate to MOXy from the Sun JAXB without having to change any code at all, we will have to include the com.sun.xml.bind interface in MOXy as well, so that we can use it in our own code.  We will then have to ask the user to implement a Sun interface to get the benefits of this feature.

We have the same issue with the upcoming NamespacePrefixResolver -- how are we going to handle these?


MOXy IDResolver - Bug 360249