Re[2]: Moving XMLC to ObjectWeb's SF

Hello Richard,

Barracuda includes some classes that were meant to, eventually, be
moved to the XMLC package.  This hasn't really happened yet.  We
access Xerces implementation packages for much the same reason as XMLC
does; because it needs more access to the DOM than the interfaces
provide.  Of course, there may be ways to workaround this.

The way we should move forward is to figure out what packages use
Xerces implementation classes directly, then figure out which of those
really *need* to access those package rather than the standard
interfaces.  Whatever is left over should probably either be moved to
XMLC, or we should figure out if there are already classes in XMLC
that provide the needed functionality.

Barracuda definitely shouldn't need direct access to XML or DOM
implementation classes.

Jake

Monday, January 27, 2003, 10:35:13 AM, you wrote:

RK> On Monday 27 January 2003 17:09, Christian Cryder wrote:
>> Having come to this conversation late, can someone summarize which packages
>> we're thinking about renaming, just so we can make sure that doesn't cause
>> any grief for Barracuda? 

RK> The org.apache.* packages. Barracuda shouldn't use anything in there, as 
these 
RK> are the Xerces implementation packages.





-- 
Best regards,
 Jacob                            mailto:hoju@xxxxxxxx