Found the problem, sysdeo Tomcat plugin for Eclipse allows JVM parameters,
ages ago I set up a profiler, and guess what, it uses the commons-lang jar,
an old one. It pays not to forget about these hidden away configurations.
Since I reset the sysdeo plugin config when using Tomcat 5.0 it did not show
up as a problem.

David

-----Original Message-----
From: David Wynter at roamware [mailto:[EMAIL PROTECTED]
Sent: 30 March 2005 18:37
To: Turbine Users List
Subject: RE: 2.3.1 helloworld example not working


The helloworld meta example app works in Tomcat 5.0.28.

So be warned, 2.3.1 does not work in Tomcat 4.1, I have not been able to
find out why not.

David

-----Original Message-----
From: David Wynter [mailto:[EMAIL PROTECTED]
Sent: 30 March 2005 17:26
To: Turbine-User
Subject: 2.3.1 helloworld example not working


I followed the meta instructions, very straightforward they are too. I had
previously tried to port my Turbine 2.3 app across to 2.3.1, see previous
email.

So thought OK lets try the example helloworld application. I get the same
result as for my ported 2.3 app. Could it be that it is Tomcat 4.1.31? I
checked for an earlier version of the commons-lang jar in the directory tree
of my Tomcat 4.1.31 installation, none found. I checked that
org.apache.commons.lang.StringUtils.split(Ljava/lang/String;C)[Ljava/lang/St
ring does exist in the commons-lang-2.0.jar, it does. Will try the Tomcat 5
version next. But who wants to force their users to upgrade to 5 when they
are happily running 4.1?

Root cause

java.lang.NoSuchMethodError:
org.apache.commons.lang.StringUtils.split(Ljava/lang/String;C)[Ljava/lang/St
ring;
        at
org.apache.commons.configuration.PropertiesConfiguration.load(PropertiesConf
iguration.java:305)
        at
org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFile
Configuration.java:190)
        at
org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFile
Configuration.java:157)
        at
org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFile
Configuration.java:124)
        at
org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFile
Configuration.java:63)
        at
org.apache.commons.configuration.PropertiesConfiguration.<init>(PropertiesCo
nfiguration.java:179)
        at org.apache.turbine.Turbine.configure(Turbine.java:306)

So 2.3.1 is unusable in this state. So the question has to be is 2.4 the
only option?

Does anybody care about 2.3.1 any longer?

David


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


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


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

Reply via email to