Yoav Shapira wrote:
Hi,
Slight juxtaposition of your message:
This certainly seems a lot more limited than the way it worked in TC
5.0. I wonder if I need to file this as a bug or a feature enhancement.
If you have any ideas, I'd love to hear them.
second step that I don't want to do since some of the web app code
internally uses a hardcoded gridsphere web app name).
Idea: Don't hard-code the app name, use ServletContext.getContextName
as needed instead.
Great idea-- where can I find this method
ServletContext.getContextName? It appears non-existent. There is a
method ServletContext.getServletContextName() but that returns the
description as defined in the web.xml and there is a
ServletConfig.getServletName() but that returns the servlet name, I need
a method that will give me the web application name programatically.
Previously I've used getServletPath("") and parse out the last file
separation character but it seems kind of hackish.
Suggestion: Don't file this as a bug or feature enhancement, it's not
likely to change, as many of us see this as an improvement in
enforcement and convention over 5.0.
Hmm, can you tell me where this convention is defined anywhere? This
is not just a problem for my portal but a few others out there that have
presented instructions that no longer work. If say three portal projects
including Pluto and Jetspeed claim this is a problem can it be
considered a bug?
Thanks, Jason
Yoav
On 12/19/05, Jason Novotny <[EMAIL PROTECTED]> wrote:
Hi Yoav,
I tried the context without the Logger element and unfortunately it
still does not work. Based on some other responses I received it seems
there are only two options to modify the context of my webapp from
http://localhost:8080/gridsphere to http://localhost:8080/portal:
1) copy "gridsphere.xml" containing my context fragment to "portal.xml"
AND rename the webapplication from "gridsphere" to "portal". (It's the
2) Create a context like this:
<Context path="/portal" docBase="/somedir/gridsphere" debug="0"
reloadable="false" crossContext="true"/>
where the web application is then moved outside of the Tomcat webapps/
directory. I don't want to do this either since for the same reasons as
1, I reference some files using the hardcoded gridsphere web app directory.
Thanks for your time, Jason
Yoav Shapira wrote:
Hi,
<Context path="/portal" docBase="gridsphere" debug="0"
reloadable="false" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_gridsphere_log." suffix=".txt" timestamp="true"/>
</Context>
Loggers are gone and invalid in 5.5. A similar context.xml fragment
without the Logger sub-element works fine for me in 5.5.12.
Yoav
--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com
---------------------------------------------------------------------
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]
