Joerg Heinicke wrote:

On 26.07.2005 22:06, Lars Huttar wrote:

More data:

The above weird behavior with cinclude seems to be tied to Java 1.5.

In the following environments, the weird behavior occurs:


...

So... anybody know why cinclude would misbehave under Java 1.5?
If I were to run Cocoon in a Java debugger (say, in Eclipse or JDB), any hints for finding the problem?


If you have different behaviours with different JVMS it looks like a problem with endorsed dirs. We have two pages about these problems o the wiki:
http://wiki.apache.org/cocoon/NoMoreDtmIdError
http://wiki.apache.org/cocoon/EndorsedLibsProblem

The first one mentions a EnvironmentCheck stylesheet. Try it out and report if the XSLT processor versions change with different JVMs. They should not if the system is configured properly.

Joerg

OK, I've tried it. Here's a table of my results. Note that when running Tomcat 5.5.9, I could not merely which JVMs; for Java 1.4.2 I had to install a compatibility pack, because Tomcat 5.5.9 requires either Java 1.5.* or the compatibility pack. The compatibility pack includes bin/jmx.jar and two jars in common/endorsed: xml-apis.jar and xercesImpl.jar.

*Java version*

        

*Container version*

        

*Cocoon version*

        

*OS*

        

*cinclude bug?*

        

*XSLT processor version*

JDK1.4.2

        

Jetty

        

2.1.7

        

WinXP

        

Yes

        

Xalan Java 2.6.0

JDK1.4.2

        

Tomcat 4.1

        

2.1.7

        

WinXP

        

No

        

Xalan Java 2.4.1

JDK1.4.2

        

Tomcat 4.1

        

2.1.2

        

WinXP

        

No

        

Xalan Java 2.4.1

JDK1.4.2

        

Tomcat 5.0.27

        

2.1.2

        

Win2K

        

No

        

Xalan Java 2.4.1

JDK1.4.2+compat

        

Tomcat 5.5.9

        

2.1.7

        

Mac OSX

        

Yes

        



JDK1.4.2+compat

        

Tomcat 5.5.9

        

2.1.7

        

WinXP

        

Yes

        

Xalan Java 2.4.1

JDK1.5

        

Tomcat 5.5.9

        

2.1.2

        

WinXP

        

Yes

        

Xalan Java 2.5.1

JDK1.5

        

Tomcat 5.5.9

        

2.1.7

        

WinXP

        

Yes

        

Xalan Java 2.6.0

JDK1.5

        

Tomcat 4.1

        

2.1.2

        

WinXP

        

Yes

        

Xalan Java 2.5.1

JDK1.5

        

Tomcat 4.1

        

2.1.7

        

WinXP

        

Yes

        

Xalan Java 2.6.0

JDK1.5

        

Jetty

        

2.1.7

        

WinXP

        

Yes

        

Xalan Java 2.6.0

JRE1.5

        

Tomcat 5.5.9

        

2.1.7

        

WinXP

        

Yes

        




Note that the XSLT processor version *does* change with different JVMs. For example, the combination of Tomcat 4.1 + Cocoon 2.1.7 uses Xalan 2.4.1 if JDK is 1.4.2, but uses Xalan 2.6.0 if JDK is 1.5.
Does this mean I've configured something wrong? If so I'd love to know more.
FYI, my Cocoon 2.1.7 build\webapp\WEB-INF\lib folder has xalan-2.6.1-dev.jar in it, and that's the only xalan jar file I can find in Cocoon or Tomcat.

Any suggestions are welcome.

Lars


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to