RE: tomcat 5.0.19, jetspeed 1.4, jdk 1.4.2, SAX problem again

2004-03-24 Thread Gerry Reno
Will, JDK 1.4.2 includes an old xml parser within the jdk. You have to override this by some mechanism. Easiest way is to put the correct parser in tomcats common/endorsed and restart tomcat. If that's not working then something new may be wrong but I doubt it. I don't have 5.0.19 so I can't

RE: tomcat 5.0.19, jetspeed 1.4, jdk 1.4.2, SAX problem again

2004-03-24 Thread Will Saxon
> -Original Message- > From: Gerry Reno [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 24, 2004 9:46 PM > To: Jetspeed Users List > Subject: Re: tomcat 5.0.19, jetspeed 1.4, jdk 1.4.2, SAX problem again > > > Will, > Somehow an incorrect version of xml parser/transformer is > bei

Re: tomcat 5.0.19, jetspeed 1.4, jdk 1.4.2, SAX problem again

2004-03-24 Thread Gerry Reno
Will, Somehow an incorrect version of xml parser/transformer is being found in your classpath. I opened a bug on this with jetspeed and with sun a while back. After putting files into common/endorsed try restarting your container. Also make sure that you don't have any xml parser/transformers

tomcat 5.0.19, jetspeed 1.4, jdk 1.4.2, SAX problem again

2004-03-24 Thread Will Saxon
I am running the above configuration on FreeBSD 5.2.1-RELEASE. FreeBSD installs Tomcat to /usr/local/jakarta-tomcat5.0, and jetspeed to /usr/local/jakarta-tomcat5.0/webapps/jetspeed. I have read through the archives and bugzilla to find solutions for the error: problem in SAX transform: org.ap

JSR 168 Portalserver comparion

2004-03-24 Thread Oliver Pfau
Hi, in the context of a JRS 168 and portalserver comparison I have a few questions regarding jetspeed supports jetspeed... 1. the validation of preference values ? 2. the sharing of preference attributes among users ? 3. buffering (caching of the portlet container, if I understood it correctly)