tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rex Wang <rwo...@gmail.com>
Subject Re: DO NOT REPLY [Bug 50462] xalan import should not be optional in maven-bundle-plugin
Date Wed, 22 Dec 2010 06:28:38 GMT
2010/12/22 Jeremy Boynes <jboynes@apache.org>

> On Dec 21, 2010, at 6:15 PM, bugzilla@apache.org wrote:
>
> > https://issues.apache.org/bugzilla/show_bug.cgi?id=50462
> >
> > --- Comment #3 from Rex Wang <rwonly@gmail.com> 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).
>
I also don't find JXPATH in maven repo.. However, you also can use the
servicemix bundled one:
http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.commons-jxpath,
But that is not the least version 1.3.


>
> 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?
>

I am not very familiar with XPATH. Do you mean the approach like spi?
IIUC, xalan implements the spi of javax.xml.transform.TransformerFactory and
javax.xml.xpath.XPathFactory. So if xalan is in the path, we can choose it
as the xpath implementation. I am not sure if jaxen and jxpath implement the
spi either.
Why not move to the standard api in jdk instead of defining new apis and
wrappers?

-Rex


>
> Thanks
> Jeremy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>


-- 
Lei Wang (Rex)
rwonly AT apache.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message