Re: [ebxmlms-develop] Hermes 0.9.3.0 with Tomcat 4.1.18 fails to start - Anything new?

[Patrick Y. <kc...@ce...>]

RE: [ebxmlms-develop] Hermes 0.9.3.0 with Tomcat 4.1.18 fails to start - =
Anything new?Peter, relax. We just want to know more about your =
environment. You know, we just want to ensure there is no =
mis-understanding here.

For your information, the error message you get is not generated by us. =
It is from the XML security library. Please check =
http://xml.apache.org/security/install.html for more information.

We are trying to repeat your problem here, that's why we need to know =
exactly the setting of your tomcat. By the way, we have just tried to =
setup in Tomcat 4.1.18 LE release, and it is ok. And we will try Tomcat =
4.1.18 full release soon.

Sigh, -Patrick
  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: 'ebx...@li...'=20
  Sent: Wednesday, March 12, 2003 9:51 AM
  Subject: RE: [ebxmlms-develop] Hermes 0.9.3.0 with Tomcat 4.1.18 fails =
to start - Anything new?


  Blast, I swear I did that to get it working in the first place.=20

  Sigh.=20

  PJDM=20
  --=20
  Peter Mayne=20
  Technology Consultant=20
  Spherion Technology Solutions=20
  Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602=20
  T: 61 2 62689727  F: 61 2 62689777=20

  > -----Original Message-----=20
  > From: Ng Chi Yuen [Cyng] [mailto:cy...@cs...]=20
  > Sent: Tuesday, 11 March 2003 9:54 PM=20
  > To: 'ebx...@li...'=20
  > Subject: RE: [ebxmlms-develop] Hermes 0.9.3.0 with Tomcat=20
  > 4.1.18 fails to start - Anything new?=20
  >=20
  >=20
  > Hi,=20
  >=20
  > > However, today, I tried to reliably send a signed message,=20
  > which resulted in=20
  > > the following in msh.log:=20
  > >=20
  > > 2003-03-11 15:48:44,194 ERROR [Thread-7]: Since it seems=20
  > that nobody reads=20
  > > our installation notes, we must do it in the exception=20
  > messages. Hope you=20
  > > read them. You did NOT use the endorsed mechanism from JDK=20
  > 1.4 properly;=20
  > > look at <http://xml.apache.org/security/install.html> how=20
  > to solve this=20
  > > problem. Original message=20
  > > was "tried to access field=20
  > org.apache.xpath.XPathContext.m_dtmManager from=20
  > > class =20
  > org.apache.xml.security.transforms.implementations.FuncHereContext"=20
  > > Is there a way around this, or do I just give up and stick=20
  > with Tomcat 4.0.6=20
  > > (which successfully reliably sends signed messages in the=20
  > brief testing I've=20
  > > been doing so far)?=20
  >=20
  >         Have you put xalan.jar in $TOMCAT_HOME/common/endorsed and=20
  > $JAVA_HOME/jre/lib/endorsed? Apache XML security library somehow =
needs=20
  > this patch in order to make it work under tomcat-4.1.x.=20
  >=20
  > Regards,=20
  > CY=20
  >=20
  > --------------------------------------------------------------=20
  > --------------=20
  > Ng Chi Yuen, CY.       cy...@ce...      =20
  > http://www.cecid.hku.hk/=20
  > Technology Officer,=20
  > Centre for=20
  > E-Commerce Infrastructure Development,=20
  > The University of Hong Kong=20
  > --------------------------------------------------------------=20
  > --------------=20
  >=20
  >=20
  >=20
  > -------------------------------------------------------=20
  > This sf.net email is sponsored by:ThinkGeek=20
  > Welcome to geek heaven.=20
  > http://thinkgeek.com/sf=20
  > _______________________________________________=20
  > ebxmlms-develop mailing list=20
  > ebx...@li...=20
  > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop=20
  >=20

The information contained in this email and any attachments to it:

(a) may be confidential and if you are not the intended recipient, any =
interference with,=20
use, disclosure or copying of this material is unauthorised and =
prohibited; and

(b) may contain personal information of the recipient and/or the sender =
as defined=20
under the Privacy Act 1988 (Cth). Consent is hereby given by the =
recipient(s) to=20
collect, hold and use such information and any personal information =
contained in a=20
response to this email, for any reasonable purpose in the ordinary =
course of=20
Spherion's=20
business, including forwarding this email internally or disclosing it to =
a third party. All=20
personal information collected by Spherion will be handled in accordance =
with=20
Spherion's Privacy Policy. If you have received this email in error, =
please notify the=20
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s) =
supplied in=20
this email and any attachments without first entering into a contractual =
agreement with=20
Spherion. You further agree not to divulge any information contained in =
this document=20
to any person(s) or entities without the express permission of Spherion.