Name: jl125535			Date: 01/16/2002


FULL PRODUCT VERSION :
java version "1.4.0-beta3"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta3-b84)
Java HotSpot(TM) Client VM (build 1.4.0-beta3-b84, mixed mode)


FULL OPERATING SYSTEM VERSION :

Microsoft Windows 2000 [Version 5.00.2195]

ADDITIONAL OPERATING SYSTEMS :

SP2 installed.


A DESCRIPTION OF THE PROBLEM :
Xalan and Xerces appear to be embedded in rt.jar.

Other bugs (eg 4593175 and 4615582 are about problems
already caused by this), but this bug report is about the
generic "wrong-headedness" (in my view) of this approach.

Surely Xalan and Xerces (possibly in cut down form to
include only the implementations, not the W3C interfaces
which are already within rt.jar) would be more
appropriately placed individually within the extensions
directory. They would then be easily replaceable as bug-
fixes and enhancements are made available.


REGRESSION.  Last worked in version 1.3.1

This bug can be reproduced always.

CUSTOMER WORKAROUND :
According to another bug, placing a different xalan.jar
(and presumably xerces.jar) in the lib directory should
work, and I'm sure changing the bootclasspath would work -
however, I don't believe either of these are as pleasant as
having a jar file already present in the lib/ext directory
and allowing that to be replaced.
(Review ID: 138187) 
======================================================================


###@###.### 2002-02-07

This EOU is out of our scope. Can someone from Jdk 1.4.0 comment on this?

Please change the category & subcategory of it.