tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Boynes <>
Subject Re: DO NOT REPLY [Bug 50462] xalan import should not be optional in maven-bundle-plugin
Date Wed, 22 Dec 2010 03:46:01 GMT
On Dec 21, 2010, at 6:15 PM, wrote:

> --- Comment #3 from Rex Wang <> 2010-12-21 21:15:19 EST ---
> (In reply to comment #2)
>> It's marked optional in Maven as it is only needed if someone is using the XML
>> tags.
>> Is there a way to mimic that with the OSGi references?
> Not sure about that.
> At least, IMO, that is not the correct way by using optional:=resolution in
> import-package to achieve the requirement.
> I think the optional:=resolution directive is used to express that if osgi
> framework can not resolve the package, the codes in this bundle may use the
> implementation from itself or from jdk.
> So if the codes have hard dependency to (explicitly import) a package, we
> should not make it as optional resolution.

Perhaps the changes needed to address the performance issue in #27717 are relevant here.
These stem from issues in Xalan's implementation which would also apply if we tried to use
the JDK's implementation. I had a prototype working with Jaxen but the project is pushing
builds to the Maven repos and does not seem very active (like, no-one replied to a recent
committer call) so depending on it could be problematic. I was thinking of using JXPath instead
(from commons).

With multiple options out there, perhaps we could just have taglibs use an interface and provide
wrappers for each as separate modules. if we did that, is that something that could be easily
handled with OSGi?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message