Re: Tomcat Module Still Broken

Does it make sense to add an abstraction layer on top of web container (WebContainer, JettyWebContainerImpl, TomcatWebContainerImpl, etc), let a factory decide (upon run) which container is declared by user. This way, user will be able to choose the container without a rebuild. (Which users do

More features in tomcat module

Hi, Just committed the latest changes to the tomcat module that let deploy webapps and run them! Really, it's now possible. Just uncomment the sections in the just-committed files and voila - Apache Tomcat 5.5.4 will run itself and deployed webapps. I remember about updating

RE: [jira] Updated: (GERONIMO-478) Deployer must not echo password when prompting

Sorry about that. I've attached another patch to the issue on JIRA. I couldn't figure out how to delete the previous one. The correct patch is bigger in size. -Chandresh -Original Message- From: Dain Sundstrom [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 2:58 PM To: [EMAIL

Re: Tomcat Module Still Broken

The problem is tomcat and jetty have fundamentally different designs and architectures, so any abstraction would limit both. The nice thing about the gbean architecture is it was designed to allows components to not agree on a common design. Regardless of this discussion, I don't think we

Re: Tomcat Module Still Broken

Dain Sundstrom [EMAIL PROTECTED] writes: I know that running two web servers seems cool, but would any (sane) user actually need (not want) to do this? I feel that a reasonable solution is to have separate distributions for tomcat and jetty. +1. Sanjiva.

Suggestion for tomcat builder, was Re: jetty-deployer branch will be merged back to trunk shortly

On Dec 7, 2004, at 3:21 PM, Jacek Laskowski wrote: Alan D. Cabrera wrote: While I agree that we should turn off the tests that break, should we also file a jira issue to make sure that they get turned back on again? +1 1. merge to trunk now and disable axis tests +1 (as I'm awaiting your

jetty-deployer branch is merged back into trunk

This was a fairly large svn operation, so I'm a little worried about whether I broke anything, despite testing ok on my machine. Please report problems. thanks david jencks

Re: Suggestion for tomcat builder, was Re: jetty-deployer branch will be merged back to trunk shortly

David Jencks wrote: I've been thinking about tomcat a bit, even though I know nothing whatsoever about what's inside:-) So do I! :) The jetty builder really doesn't do anything jetty specific any more (except construct one set of redundant security info, that Alan and I are hoping to figure out

[jira] Commented: (GERONIMO-478) Deployer must not echo password when prompting

[ http://nagoya.apache.org/jira/browse/GERONIMO-478?page=comments#action_56397 ] Hiram Chirino commented on GERONIMO-478: The password hiding strategy that the patch uses is not very optimal since it is continously updating the screen to

Documentation Update

I believe I've caught up with the feedback I've received on the existing content. So this update is just to let you know that the existing material has been updated. There were a lot of relatively minor changes, but the more significant ones include: - added some background on the

[jira] Closed: (GERONIMO-473) Jetty module builder should completely configure web app context and servlet holder gbeans

[ http://nagoya.apache.org/jira/browse/GERONIMO-473?page=history ] David Jencks closed GERONIMO-473: - Resolution: Fixed Fix Version: 1.0-M4 Development in djencks/jetty-deployer1/trunk branch has been merged back into trunk. Jetty module

Re: Build/Test failed

I did a maven m:co a couple of days back and I do a maven m:update before I build. I did not specifically check whether the two modules (tanql and openejb) are in sync. I assume, m:update gets the latest source for both the modules and that they are in sync. Is that a safe assumption? There are

[jira] Closed: (GERONIMO-488) jetty dispatch handling doesn't set component context, tx, or security properly in geronimo

[ http://nagoya.apache.org/jira/browse/GERONIMO-488?page=history ] David Jencks closed GERONIMO-488: - Resolution: Fixed Fix Version: 1.0-M4 I've implemented an interceptor-like stack for these operations called from enterScope and leaveScope.

RE: [jira] Updated: (GERONIMO-478) Deployer must not echo password when prompting

Yes it is. Being a first time contributer I didn't know the steps. Could you point me to the pasge that says how to do it or to an existing .java file that does a similar thing. -Chandresh From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [jira] Updated:

[jira] Created: (GERONIMO-524) axis module is not consistent with new jetty deployer

axis module is not consistent with new jetty deployer - Key: GERONIMO-524 URL: http://nagoya.apache.org/jira/browse/GERONIMO-524 Project: Apache Geronimo Type: Improvement Components: webservices Versions:

[jira] Commented: (GERONIMO-524) axis module is not consistent with new jetty deployer

[ http://nagoya.apache.org/jira/browse/GERONIMO-524?page=comments#action_56408 ] Aaron Mulder commented on GERONIMO-524: --- I think there are 2 -builder modules necessary. 1) that deploys web services (servers) based on EJBs or JAX-RPC servlets