Hi,
>
> If you just use the JAXP API, the JBoss code should work with
> both. The only notable omission from JAXP is a standard way
> to write out
> XML files from a Document, but you could encapsulate that and have it
> detect the current parser and do the right thing. Then a user can use
> whatever parser they prefer for their application, and JBoss shouldn't
> care. Ain't standards great? :)
>
The other (?) glitch I've hit is that the ant configs and run scripts all
hard code the xml jar files. Thus I plan to try and make these independant
too - by just adding everything in the appropriate lib directory to the
path.... does this sound ok?
...where will this can of worms lead... ;-)
Chris
================================================================================================
This electronic message (email) and any attachments to it are subject to copyright and
are sent for the personal attention of the addressee. Although you may be the named
recipient, it may become apparent that this email and its contents are not intended
for you and an addressing error has been made. This email may include information that
is legally privileged and exempt from disclosure. If you have received this email in
error, please advise us immediately and delete this email and any attachments from
your computer system.Rabobank International is the trading name of Coöperatieve
Centrale Raiffeisen-Boerenleenbank B.A. which is incorporated in the Netherlands.
Registered with the Registrar of Companies for England & Wales No. BR002630 and
regulated by the SFA for the conduct of investment business in the UK.
The presence of this footnote also confirms that this email has been automatically
checked by Rabobank International for the presence of computer viruses prior to it
being sent, however, no guarantee is given or implied that this email is virus free
upon delivery.
