Yes :) .. you are 100% right and it is working now. I have found it
yesterday but it was already very late and I did not post what was the
solution.

Before I was confused with Ate Douma post saying:
--------------------------------------------------------------------------------------------------------------------
The difficulty is that the right configuration depends on the version of Tomcat.
With Tomcat version <= 5.5.23 this attribute requires value "true":

 useContextClassLoader="true"

With Tomcat veresion >= 5.5.27 (and >= 6.0.18) you need to configure
value "false":

 useContextClassLoader="false"
--------------------------------------------------------------------------------------------------------------------

It happens that it is other way around and JetSpeed2 on Tomcat 5.5.27
should have
  useContextClassLoader="true"

To confirm it you can see bug report from :
https://issues.apache.org/jira/browse/JS2-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel



Thank you all for your time and help.

Cheers.

--
Jan




2009/5/14 Michael Stanley <[email protected]>:
  It does appear (at
> least in my case) that 5.5.27 requires true and 5.5.23 requires false.
>
> <5.5.27-HOME>/conf/Catalina/localhost/jetspeed.xml:
>
> <Realm className="org.apache.catalina.realm.JAASRealm"
>         appName="Jetspeed"
>
> userClassNames="org.apache.jetspeed.security.impl.UserPrincipalImpl"
>
> roleClassNames="org.apache.jetspeed.security.impl.RolePrincipalImpl"
>         useContextClassLoader="true"
>         debug="0"/>
>
> <5.5.23-HOME>/conf/Catalina/localhost/jetspeed.xml:
>
> <Realm className="org.apache.catalina.realm.JAASRealm"
>         appName="Jetspeed"
>
> userClassNames="org.apache.jetspeed.security.impl.UserPrincipalImpl"
>
> roleClassNames="org.apache.jetspeed.security.impl.RolePrincipalImpl"
>         useContextClassLoader="false"
>         debug="0"/>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to