You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Willem jiang <wi...@gmail.com> on 2013/04/12 05:10:37 UTC
Re: Xalan bundle issues… needthoughts…
I'm not sure how many people will use the xalan-serializer bundle, but let these two bundle exports the same packages is not a good way to go.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Thursday, April 11, 2013 at 10: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?
>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com