, that means the autowebapp-tag doesn't work.
Any ideas?
Regards
Marten Lehmann
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Hello,
after almost comleting Oreilly's Tomcat - The Definitive Guide, the
only thing mentioned there about changing the user tomcat is running as
is to put it into a chroot-environment, whereby the chroot is not as
important as changing the user and group in the same step. Without doing
You could check out the commons-daemon jsvc (ships with TC 5.x, but should
work with 4.1.x as well). It doesn't handle the chroot problem (but, since
Solaris 8, I've almost given up on getting chroot to work). However, it
does handle the port-binding and then changing uid problem.
Thanks. I
? reloadable=true and autoDeploy=true is set everywhere. Am I
doing something wrong or does tomcat simply not look for changes in
.xml-files, but only for changed .war-files and single servlets and
jsp's in directories?
Regards
Marten Lehmann
Hello,
I'm trying to use the commons-daemons package as of 20031204.tar.gz with
jakarta-tomcat-4.1.29, everything should be in the right place, but jsvc
exits with
java.lang.NoSuchMethodException:
org.apache.catalina.startup.BootstrapService.init([Ljava.lang.String;)
at
tomcat 5 was released
just 2 days ago. Can I use my tomcat 4.1.29 setup and configuration
files with tomcat 5 or do I have to look through the manuals and change
several things?
Regards
Marten Lehmann
-
To unsubscribe, e-mail
Hello,
I'm using tomcat-5.0.16 with jsvc to bind tomcat to port 80, but running
it with a different user than root. Startup and running is fine.
Shutdown (in general) also. But when tomcat (or jsvc?) exits, the
following entry always appears in catalina.out:
jsvc.exec error: Service exit with
The jsvc name is a Linux thing, having to do with quirks in Linux
permissions. You can look through the source if you really find this
interesting (it's half decently documentented there :). Jsvc works on a
parent-slave model. The parent sits around to see if the slave has died,
and recieves
Hello,
to offer language-depended websites I want to make a webapp available
through /de/* (german) and /en/* (english). Of course, I don't want to
use two servlet-repositories for that. My idea is, that no matter if
e.g. /en/helloworld or /de/helloworld is requested, a unique
Did you turn on SSI support??
An include-statement doesn't require SSI.
To Sumit: You're using a relative path to the file. Have you tried with
an absolut path to make absolutely sure that's nothing wrong with
permissions or base-paths the relative path relies on? Maybe some
security-rules
Hello,
What about using one centralized servlet that parses
req.getPathInfo(), sets the language as request attribute
and forwards to the real servlet(s) ?
how is a request-forwarding done?
Regards
Marten
-
To unsubscribe,
Hello,
Have a session variable that tracks what language they're using.
I'm not looking for a different solution, but one, that solves my
question. I definitely cannot do anything else than the /de/ or /en/ thing.
Regards
Marten
Hello,
to test dbcp's stacktrace functionality, I didn't close the databases
connection after use. But although I set the abondedTimeout to 60, the
connections are never returned, they are still open and I don't see a
stacktrace, too.
I used the following parameters, as from the howto:
Hello,
maybe this is not the perfect group for my question, but as my problem
appears at the development of JSPs and tomcat is concerned with that, I
hope you can answer it.
I often see the condition
String test = req.getParameter(test);
if (test == null) {
/* string is empty */
} else
Hello,
I was setting fine grained permissions to my webapp, but always an
exception was thrown. So I tried to use
grant {
permission java.security.AllPermission;
};
but even with that, my application doesn't run (which it does without
-security). When calling the site, I get:
Hello,
I don't want to reinvent the wheel. Container managed security is a fine
thing and works well. While it's easy to call a session.invalidate() to
logout of a session in whatever way I like (JSP, Servlet, ...), loggin
in still looks a bit ugly, even with the possibility to define a
Hello,
I have a forward to a jsp-file. This jsp-file needs to know which URI
was requested in the initial request. Currently, I can only see the
requestURI of the forwarded jsp-file. Any ideas?
Regards
Marten
-
To
Hello,
is there a way to force tomcat (or a web-container in general) not to
use cookies to keep track of sessions, but to use url-rewriting with the
;jsessionid=sessID suffix instead?
Regards
Marten
-
To unsubscribe,
Hi,
You need to read SRV.8.4 of the servlet specification.
I read it now. However, it's stated there, that path-related-values
should be overwritten by the container in all request-dispatcher
occurences. This means: include and forward. But for an include, I can
see the original
Hello,
My problem is: the mod_proxy.so , mod_rewrite.so don't appear
anywhere, What do I have to do in order to get these *.so?
if you don't ask the compiler to create them, they aren't created as
shared modules, but are included in the httpd-binary by default. Look at
the output of
Hello,
within the init() of a filter, I'm storing a reference to the
servletContext:
filterConfig.getServletContext().setAttribute(servletContext,
filterConfig.getServletContext());
But when I'm trying to access this attribute in the doFilter-method, I
get a NullPointerException:
Hello,
how can I get the requestURI or pathTranslated without the
context-prefix? Instead of
/newsletter/config/login.jsp
I would like to get returned just
/config/login.jsp
Additionally, while you can enter
//newsletter//config/login.jsp
in the address-field of the browser, it would be
Hello,
I tried to put the following into web.xml:
welcome-file-list
welcome-fileindex.faces/welcome-file
/welcome-file-list
But obviously, this doesn't work, because there is no file index.faces,
but index.jsp. However, if the index.jsp isn't called through
index.faces, the
Hello,
I can start a forward like this e.g. through a filter:
request.getRequestDispatcher(/test.html).forward(request, response);
But how can I check if the ressource really exists?
request.getRequestDispatcher(/test.html) always gives me a
RequestDispatcher reference. Or is it possible to
Hello,
thanks for your class. I'm not usig it (and I guess its partially wrong,
because you can't simply append the welcome-file the the path-info), but
it inspired me to create a better way: Through a filter. I attached the
filter-class, you would integrate it in the web.xml as follows:
Hello,
from within a filter, I'm trying to do the following:
request.getRequestDispatcher(req.getServletPath() +
index.faces).forward(request, response);
This works generally fine. The problem is, that attached filters simply
aren't processed for this request. I have two filters in series,
Hello,
1) You need to be running tomcat 5
2) See SRV.6.2.5 Filters and the RequestDispatcher in the servlet spec -
it discusses exactly what you need to do.
thanks, it works as I expected it to work now.
Regards
Marten
-
27 matches
Mail list logo