[xmlc] Re: Issues with XMLC 2.3.2

This is a multi-part message in MIME format...

------------=_1299518023-30467-14636
Content-Type: text/plain;charset=iso-8859-1; format="flowed"
Content-Transfer-Encoding: quoted-printable

I can look into using your patch for #1 (or something like it) for the ne=
xt=20
XML release.=A0 I think the primary issue here is that we've maintained a=
=20
dependency on JDK1.3, which does not have java.net.URI.=A0 I've tried to=20
maintain this minimum dependency as long as Xerces does so.=A0 Plus it ma=
kes for=20
easy testing because JDK1.3 doesn't add any of its own XML libraries.=A0 =
It's=20
easy to dictate the version without getting buggy JDK1.4 XML behavior.=A0=
 But I=20
think most of the world has moved on to JDK1.5+, so maybe XMLC should too=
 at=20
some point?

I'll have to test #2.=A0 Not sure how quickly I'll be able to get to this=
,=20
though.=A0 But I'll try and spend some time this week on it.

Jake

On Mon, 07 Mar 2011 13:56:15 +0100
=A0Sasa Bojanic <[email protected]> wrote:
> Hi,
>=20
> I'm trying to upgrade our applications that use XMLC 2.3.1 to the newes=
t=20
>XMLC version.
> Our applications are deployed both under the Tomcat 6.0.29 application=20
>server and Enhydra application server (based on Tomcat 6.0.29).
>=20
> There are two issues I faced:
>=20
> 1) when deploying under the Tomcat, XMLC JAR files are placed together =
with=20
>the application JAR files into application's WEB-INF\lib folder (so=20
>application classloader is used to load them). In this case, XMLC can't =
load=20
>resources (*.html and *.xmlc files) from JAR file. When resources are no=
t in=20
>the JAR file but unpacked into WEB-INF\classes folder everything works.
>=20
> After "patching" the method getPathURLFromClasspath() from=20
>XMLCDeferredParsingFactory to add:
>=20
>=A0=A0=A0=A0=A0=A0 if (srcURL !=3D null && srcURL.toString().indexOf(".j=
ar") >=3D 0) {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 try {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0String mdurl =3D srcURL.=
toString();
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0srcURL =3D new URL("jar:=
"
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 + mdurl.substring(0, mdurl.indexOf(".jar"))=20
>+ ".jar!/"
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 + mdurl.substring(mdurl.indexOf(".jar") +=20
>4));
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 } catch (Exception ex) {
>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0}
>=A0=A0=A0=A0=A0=A0 }
>=20
> after the line:
>=20
>=A0=A0=A0=A0=A0=A0 URL srcURL =3D fDynamicClassLoader.getResource(path);
>=20
> it works fine.
>=20
> 2) when deploying under Enhydra application server or under Tomcat, but=
=20
>instead of putting XMLC JAR files into application's WEB-INF\lib, we put=
 it=20
>into Tomcat's lib folder, XMLC can't find resources no matter if resourc=
es=20
>are inside JAR file or unpacked, and it can't find it even in the case I=
 put=20
>application's JAR file into Tomcat's lib folder.
>=20
> Is it a bug in XMLC? Can somebody help?
>=20
> Regards,
> Sasa.
>=20


------------=_1299518023-30467-14636
Content-Type: text/plain; charset="UTF-8"; name="message-footer.txt"
Content-Disposition: inline; filename="message-footer.txt"
Content-Transfer-Encoding: quoted-printable


--
You receive this message as a subscriber of the [email protected] mailing list=
.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=3Dhelp
OW2 mailing lists service home page: http://www.ow2.org/wws

------------=_1299518023-30467-14636--