Still a bit confused with it...
When I put class files into WEB-INF/classes, Tomcat reports something
like this:
DependManager: Added
/home/httpd/html/binarix.dev/WEB-INF/classes/com/binarix/velocity/PumpServlet.class
class com.binarix.velocity.PumpServlet
Jim Cheesman wrote:
I have to back this statement up - jar reloading on TC4/Win2000 is a risky
business, to say the least. Sometimes it works, sometimes not... I wonder
if it's anything to do with the server checking for a new jar at the same
time as the filesystem overwrites the old one?
Bojan Smojver wrote:
Still a bit confused with it...
When I put class files into WEB-INF/classes, Tomcat reports something
like this:
DependManager: Added
/home/httpd/html/binarix.dev/WEB-INF/classes/com/binarix/velocity/PumpServlet.class
class
I looked through the source code and in the documentation of the Loader
to see if the change of web.xml will cause an application reload in TC4
when relaodable is set to true, but I couldn't find anything that would
tell me that explicitly.
I'm sure this is the case in TC3.3, I was just trying
Craig R. McClanahan wrote:
On Wed, 12 Sep 2001, Bojan Smojver wrote:
Date: Wed, 12 Sep 2001 10:40:21 +1000
From: Bojan Smojver [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Tomcat User List [EMAIL PROTECTED]
Subject: TC4: web.xml and reloading
I looked through the source
Huaxin wrote:
A little bit off topic, sorry about that.
I see most of the examples using EJB from Servlet.
However, is there any example of using JSP with
EJB directly? (without too much scriplet, and
hopefully more efficient than create a bean to
interact with the EJB)
thanks a lot
Remy Maucherat wrote:
My question was about web.xml, not the classes and jars (that's
explained in Loader docs). If web.xml changes, TC3.3 will dump the app
and reload because web.xml gets stored in the DependManager (from
memory). Does TC4 behave the same?
No web.xml reloading in TC
Remy Maucherat wrote:
Remy Maucherat wrote:
My question was about web.xml, not the classes and jars (that's
explained in Loader docs). If web.xml changes, TC3.3 will dump the app
and reload because web.xml gets stored in the DependManager (from
memory). Does TC4 behave the
Craig R. McClanahan wrote:
When you set an application's Context entry to say reloadable='true',
Tomcat starts a background task that watches for changes to *any* class
that was originally loaded from /WEB-INF/classes or /WEB-INF/lib. If such
a change is detected, the app will be reloaded.
SongDongsheng wrote:
My question is:
1) Can TC4 work with jboss ?
2) is so, how can I do it ?
Thanks,
Dongsheng Song
Although I don't use that combination, I don't see any reason why not.
Unless, of course you want to run them in the same JVM. JBoss manual
mentions that Catalina
Remy Maucherat wrote:
Essentially, yes.
JAR reloading is not very reliable on my Windows box, though (and you can't
remove JARs; but strangely you can ovewrite them). Sometimes, the changes
get picked up, sometimes they do not. I have yet to find the reasons for
this, unfortunately :-(
Maybe you can use application init parameters instead?
Bojan
Viktors Krebss wrote:
Hello,
Does anyone know how can I access servlet init parameters form another
servlet ?
I mean I can access servlet context (context-param ) using
getServletContext().getContext(/some_servlet)
but what
Maybe you can use getRemoteUser, isUserInRole, getUserPrincipal etc.
from HttpServletRequest interface to find out who's logged on?
Once the user is authenticated, you'll always get its info from the
above and Tomcat will make sure that this guy is part of the correct
session. Does that answer
What's the actual error message?
Maybe you can print out the SQL statement to see if the syntax is OK. It
could be invalid SQL. Are you running this under Windows NT/2000 or
9x/ME? Maybe the user Tomcat runs under doesn't have access rights on
this database?
I don't really use Access, I'm just
It's explained in the server.xml file... Promise to brush up on my
reading skills :-)
Bojan
Bojan Smojver wrote:
I've been looking through the docos to find how to bind Tomcat's
connectors of Tomcat itself to just a single IP address (ie. 127.0.0.1),
which is handy for securing
I've been looking through the docos to find how to bind Tomcat's
connectors of Tomcat itself to just a single IP address (ie. 127.0.0.1),
which is handy for securing it. Couldn't find anything...
Can someone point me in the right direction?
Bojan
I've posted to this list a few days ago a message related to the
compilation problems of mod_webapp. It seems that the versions that come
with b2 and b3 of Tomcat 4.0 are screwed (even after cleaning double new
lines in Makefiles). I didn't have the patience to go through the code
to determine
is wa_connection.c. Since the
WebAppConnection has been defined in the first pass, it won't accept the
same one in the second pass because it checks for duplicate connections.
Bojan
Bojan Smojver wrote:
I've posted to this list a few days ago a message related to the
compilation problems
Anyone out there had any luck compiling the mod_webapp? Even after
removing double new lines from the Makefiles, there is a whole heap of
compilation error messages (mostly undeclared stuff)...
And if mod_webapp is not ready, can mod_jk be used with Tomcat 4.0?
Configuration:
RedHat Linux 7.0
Try to put the plugin in ~/.netscape/plugins instead.
Bojan
"Robert B. Easter" wrote:
cd /usr/local/netscape/plugins
ln -s /usr/local/j2sdk1.3.0/jre/plugin/i386/javaplugin.so javaplugin.so
In tomcat's conf directory there is a file called tomcat-users.xml.
There are a few user accounts already there (Tomcat 3.2.1), one is
called 'tomcat', having a role 'tomcat' (a bit confusing but Java
Servlet API Spec 2.2 might clear that up for you). Next set you web.xml
file up. Something like:
I've been trying for a while to implement the init parameters for JSP
engine mentioned in Tomcat FAQ's but without much luck.
First, I think the 'org.apache.jasper.runtime.JSPServlet' is wrong,
there is no such class in Tomcat 3.2.1. It should probably be
'org.apache.jasper.servlet.JspServlet'
I just compiler the attached file into a class, put the class into the
webserver.jar (to avoid changing CLASSPATH for testing) and modified
server.xml file with:
ContextInterceptor
className="tc3.JasperOptions"
sendErrToClient="false"
keepgenerated="false"
/
after the WebXmlReader
I didn't actually say that the configuration works. It'll be some time
before I know that for sure. But it does compile and link :-)
If I understand correctly, DSO is described in Apache INSTALL file as
optional.
I have seen references in the jk code to dl related functions (and
actually -ldl
I've noticed that there aren't any instructions about compiling and then
statically linking mod_jk.so into Apache (mod_jk HOWTO from Tomcat 3.2).
Is this intentional (ie. do you want to move people away from doing
that) or is it just missing because most people prefer DSO?
I've been able to
25 matches
Mail list logo
