DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21131>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21131 Using Jetspeed with J2SE 1.4.2-beta breaks portlets ------- Additional Comments From [EMAIL PROTECTED] 2003-07-04 10:30 ------- I think the jre will not work because tomcat overrides the mechanism with "-Djava.endorsed.dirs=xxx", but I'm not completely sure. Re: the workaround, I would agree with you if the problem was not for a "-beta" version of the jdk and we were not trying to release a non beta version of jetspeed 1 ASAP. There is no clean cut solution, as the JAXP and TRAX parsers supplied with the JDK are often buggy or lack features needed. This is a well known problem in cocoon, for instance. They use a leading edge TRAX transformer. The clean solution would be either: - update our xerces and xalan jars to versions which do not conflict with this jdk (but they could conflict with the one in 1.4.0 or 1.4.x...) - remove them completely and use whatever comes with jdk or the servlet container (but I think 1.3.1 has JAXP but no TRAX inside, and people using other servlet containers can get different versions) Both approaches need extensive testing (matrix with jdk and servlet container versions), and can fail if people has an endorsed xerces/xalan already (for instance, because they run cocoon in the same servlet container) This is the reason why I would fix it by documenting the issue carefully in the install document and FAQ. In most deployments you would have a fairly unique environment, due to jdk, servlet container, other webapps differing wildly. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
