> -----Original Message----- > From: Matt Raible [mailto:[EMAIL PROTECTED] > Sent: 14 January 2004 21:50 > To: 'Cactus Users List' > Subject: RE: cactus ant task on existing container ? > > > No, it doesn't. BTW, it's the responsibility of the container > > to sweep the webapps folder, no? > > I agree, so maybe it's a flaw in Tomcat that it's not doing this when > running it via the <cactus> task?
No, it's normal. <cactus> creates a tomcat configuration in a target dir. It does not put any context xml file there. Thus it's normal tomcat doesn't pick any... :-) > I normally just use <runservertests>, > which works good enough, but I want to expand testing to Resin. Of > course, it looks like this task doesn't support 3.0.x, so I might be > wasting my time, eh? Not long ago, I worked on supporting Resin 3.x but I had a question which never got answered on the resin mailing list (see attached). Would you know the answer by any chance? :-) > > > But, yes, you're right, > > there's currently no attribute in the <tomcat?x> nested > > element to specify a custom context xml file. > > > > If you can point me to the doc explaining what context xml > > files are, I should be able to add support for it quite > > easily. What does it bring compared to server.xml? > > > > It's basically a way to configure your Tomcat server w/o editing the > server.xml. You can just drop your <Context> definition into an XML > file and put it in the webapps directory. It's the same thing as > putting a Context in server.xml. > > http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html > > <quote> > In addition to nesting Context elements inside a Host element, you can > also store them in individual files (with a ".xml" extension) in the > appBase directory for a Host. See Automatic Application Deployment for > more information. > </quote> ok thanks. That should be easy to support. Is this feature also supported in Tomcat 3.x and 5.x? > > Resin has the same ability, but you do have to tell it (in resin.conf) > that you have a separate *.conf file. Sure would be nice if they'd pick > that up automagically. Ok. That will be next. Thanks -Vincent > > Matt > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
--- Begin Message --- Title: Shutting down Resin from command line/java?Let me ask another related question. Actually what I would like is the ability to start Resin from Ant using the <java> task and to stop it also from Ant using also the <java> task. Is that possible?
In the past (Resin 2.0, 2.1) it wasn't as there was no close command line paramtere available. Thus I had to implement a ResinRun class that would start the container, keep a reference to the ResinServer, open a socket to listen for a close command. Then once it got this close command, it would use the ResinServer instance and call close on it.
Is Resin 3.x now supporting shutting it down from the command line/java?
Thanks
-Vincent> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:owner-resin-
> [EMAIL PROTECTED] On Behalf Of Vincent Massol
> Sent: 01 November 2003 23:05
> To: [EMAIL PROTECTED]
> Subject: [Resin 3.x] New way to start Resin programatically?
>
> Hi,
>
> I have been starting Resin 2.0 and 2.1 from Java (embedded). So far I
> have been using the following:
>
> --> Resin 2.0:
>
> ResinServer server = new ResinServer(args, true);
> server.init(true);
> server.close();
>
> --> Resin 2.1:
>
> ResinServer server = new ResinServer(args, true);
> server.init(null);
> server.close();
>
> --> Resin 3.x:
>
> It seems this has changed in Resin 3.x. Looking at the source code, it
> seems I have to do the following:
>
> Resin resin = new Resin(args);
> resin.init();
>
> However, I'm not sure how to stop Resin programmatically? Should I do
> the following:
>
> resin.getServer().destroy();
>
> Is that correct? I haven't tried yet but wanted to get confirmation I'm
> on the right track. Also, is there any documentation about embedding
> Resin 3.x anywhere? I could not find it.
>
> Thanks
> -Vincent
--- End Message ---
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
