Raul,
till all the major app servers are moved off of JDK1.3 (for production
environment), we cannot stop supporting it. So, here's my +1 to
support 1.3 at least for a bit more time.
thanks,
dims
On Fri, 1 Oct 2004 15:13:38 +0200, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> On 30/09/2004, at 22:15, Joris Wijlens wrote:
>
> > Hi,
> >
> > Is version 1.2 still going to be compatible with jre 1.3. I tried to
> > compile HEAD from CVS (30-sep-2004) with a sdk 1.3 compiler and got
> > these messages:
> >
> > [javac]
> > D:
> > \workspace\xml_sec_cvs\src\org\apache\xml\security\c14n\implementations
> > \CanonicalizerBase.java:82: cannot resolve symbol
> > [javac] symbol : constructor RuntimeException
> > (java.lang.String,java.lang.Exception)
> > [javac] location: class java.lang.RuntimeException
> > [javac] throw new RuntimeException("Unable to create nullNode",e);
> > [javac] ^
>
>
> Ok, I'll see in the jdk 1.3 there is no Exception(String reason,
> Exception rootException) constructor, that's way it fails compilling it
> won't very dificult to fix poorly, but if we don't want to loose
> information when running in 1.4 we'll need something like tomcat is
> used with one class that wraps the diferences between the jdks.
> Anyhow I'll don't know how big is the interest of supporting jre 1.3
> please raise your hands/email so I can see if worth the effort of doing
> more or less hacky for xml-sec 1.2 or we do right but for latter
> version.
>
> Regards,
>
> Raul
> http://r-bg.com
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
