Thanks for the reply Jon.
-----Original Message-----
From: Jon Wingfield
It's part of the core java security model. If a package is
sealed within a jar then packages of the same name cannot
be defined in another jar, or elsewhere on the classpath.
Within the manifest file of the jar file which is being
loaded by your putpr servlet you'll probably have a couple
of lines like:
Name: nu/xom
Sealed: true
The XOM jar that I have (xom-1.0d8.jar) doesn't seal its
packages. So, you need to find the jar which is sealing the
nu.xom package and stop it doing so. (Or work out your xom
dependencies)
I'm guessing its xercesImpl jar? Having removed it the error 'went'.
I also got a clue, just import nu.xom.*; rather than individual ones?
Unsure which one cleared the error,
but its OK now.
What the heck do I do if I want xom to validate?
regard sDaveP
--
DISCLAIMER:
NOTICE: The information contained in this email and any attachments is
confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of the
content of it or of any attachment; you are requested to notify the
sender immediately of your receipt of the email and then to delete it
and any attachments from your system.
RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants. However, it
cannot accept any responsibility for any such which are transmitted.
We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email and
any attachments are those of the author and do not necessarily represent
those of RNIB.
RNIB Registered Charity Number: 226227
Website: http://www.rnib.org.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
