"Robles, Rogelio" <[EMAIL PROTECTED]> writes:
>These are my finding regarding this specific topic.
Thank you for testing!
>After testing pure .EAR and .WAR deployments with JBoss+Tomcat
>and Tomcat, it seems that Turbine has a problem reading the configuration
>files.
>The deployment scenarios that I tested for a typical Turbine webapp were:
>JBoss+Tomcat (3.0, 4.0.6)
>-------------------------
>.EAR
>.WAR
>.WAR (with web.xml containing properties=WEB-INF/conf/TR.props instead of
>/WEB-INF..)
>.WAR manually expandend (*)
>Tomcat (4.1.18)
>---------------
>.WAR (using the maven tomcat goals for cmd line deployment, remove, reload,
>etc., )
>.WAR (with web.xml containing properties=WEB-INF/conf/TR.props instead of
>/WEB-INF..)
>.WAR (dropped into the webapps folder) (*)
>The items marked with (*) resulted in a succesfully running Turbine webapp,
>the rest always produced:
>(!) NOTICE: Turbine: init() failed:
>org.apache.turbine.services.InitializationException:
>Can't load file null/WEB-INF/conf/TurbineResources.properties
Ok. So we get "null" as base path and we must work there.
>The first solution that I found, which I haven't had the time to test it but
>I want to
>share what I found, is that we need to replace the
>javax.ServletContext.getRealPath() calls by
>javax.ServletContext.getResource() or
>javax.ServletContext.getResourceAsStream() as needed in
>org.apache.turbine.Turbine.
>Because the documentation that I found says:
[...]
Will look into this. Thanks. Can you, however, still open an
issue with the issue tracker so this doesn't get lost?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
