Hi:
>MIME-Version: 1.0
>Subject: Re: JAXP.next JSR Proposal
>From: Joseph Kesselman <[EMAIL PROTECTED]>
>Date: Thu, 6 Mar 2003 13:31:37 -0500
>X-MIMETrack: Serialize by Router on D01ML243/01/M/IBM(Release 6.0.1 [IBM]|March
4, 2003) at 03/06/2003 13:31:41, Serialize complete at 03/06/2003 13:31:41
>X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
>
>>planning to rename the parser/transformer classes that would go into next
>JDK
>>release. With this change users can override the parser/transformer just
>by
>>putting the latest version in CLASSPATH ( As the names of classes are
>different).
>
>Uhm... Seems to me that this requires more than a class-name change to
>achieve desired behaviors. Can you provide a specific example of what's
>being proposed?
The proposal is to rename the implementation class names and set the default
values of factories to those renamed Class names as part of JDK ( including the
Fallback classnames for factories ).
When user wants to use the updated classes from Apache ( e.g for Xalan ) , they
can then put the updated jar files in the CLASSPATH. And use JAXP defined
mechanisms ( for example by updating <JAVA_HOME>/lib/jaxp.properties ) to set
the Factories to Apache factory classnames.
Please let me know if you see any problem with this approach.
Thanks
-Ramesh
PS: As experiment I tried this approach and things are working as expected.
>
>______________________________________
>Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
>"may'ron DaroQbe'chugh vaj bIrIQbej" ("Put down the squeezebox and nobody
>gets hurt.")
>
