+1 for #2, it's the easiest/quickest way. Regards JB
On 04/11/2013 04:03 PM, Daniel Kulp wrote:
There is currently a problem with the Xalan bundle that I'd like to get resolved, but I'm not sure what is the "best" way to resolve it. I'd like some thoughts. The problem is that the xalan bundle also includes the org.apache.xml.serialize packages and exports them and such, but it does NOT include the updated/modified ObjectFactory that is needed in that package to allow it to work properly in OSGi. There are (at least) two possible avenues to fix this: 1) Proper fix is likely to remove that package entirely from the xalan bundle and have it import it from the xalan-serializer bundle. However, I think some of the existing features.xml's and other applications and such that have been pulling in Xalan are likely not also pulling in the xalan-serializer bundle since it was never needed before. Thus, it's kind of not really backwards compatible. They would need to update a few things. 2) Copy the ObjectFactory from xalan-serializer bundle into the xalan bundle. This pretty much keeps the xalan bundle "as is", but allows it to work in OSGi. Personally, I don't really like #2, but it would have the least impact. Thoughts?
-- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
