I tried importing it all. It worked fine with NT but failed using Windows
2000.
When I reverted to IBM's MO there were no probs.

brgds,
S. Bro


-----Original Message-----
List:     struts-user
Subject:  RE: RE: WTE/Struts parser incompatibilities - pandoras box?
From:     "Jon.Ridgway" <[EMAIL PROTECTED]>
Date:     2001-06-22 13:17:12
[Download message RAW]

Hi,

It has been done both ways by various people on this list. Both seem to
work. So I guess it really doesn't matter. Juts a personal taste thing.

Personally I have trodden all over IBM XML Parser ... project as I want the
latest versions of all org packages and I don't like the mix and match
implicit in bringing only some of the JAXP classes into VA.

Jon.

-----Original Message-----
From: dsf65b y b3763476b3 [mailto:[EMAIL PROTECTED]]
Sent: 22 June 2001 12:41
To: [EMAIL PROTECTED]
Subject: RE: RE: WTE/Struts parser incompatibilities - pandoras box?

I'm aware that the actual name of the project doesn't matter!

What I tried to get across was that if I follow the instruction for
installing a JAXP compatible parser found at:


http://www7.software.ibm.com/vad.nsf/Data/Document2558?OpenDocument&SubMast

I have to create open editions of the IBM's packages:

     org.xml.sax
     org.xml.sax.helpers

which are part of the project "IBM XML Parser for Java 2.0.15".

However, if I leave out *all* the packages starting with "org" when
importing parser.jar
I don't have to do that and it still works! What are the ramifications, if
any, of doing that?

Respectfully,
S. Bro

Reply via email to