Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=PnlTWuo31kdA73h26xTrUClfIFWd/XyYu4QSlgLvi3ih/prTJi3mdXQxOv2jwIlC;
  h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <43392221.6070702@earthlink.net>
Date: Tue, 27 Sep 2005 06:42:41 -0400
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: Attacking M5
References: <BCBBAF56-57B6-41A9-93EB-2A42945F0F61@visi.com>
 <4338A05C.2020206@earthlink.net>
 <F9E3FEAA-68B3-4BCF-BDD1-DF4867D5BE2F@visi.com>
 <4338A749.5020801@hogstrom.org>
In-Reply-To: <4338A749.5020801@hogstrom.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

In that case then I would assume that this isn't a configuration option 
then but rather part of the install processing.  This way there would 
not be a case where the user could accidentally deploy apps before 
choosing or changing the web container.

Assuming that the container selection is part of the installation then 
it should also address my last concern about "pre-deployed" 
applications.  I suppose we would just make the deployment of these 
applications part of the installation instead of part of the build.

Joe


Matt Hogstrom wrote:
> I think its reasonable to choose one before starting to deploy 
> applications.  Dynamically (easily) switching WebContainers would be 
> nice but I don't think its a must have.  I agree with the easy to choose 
> at initial deployment.
> 
> Matt
> 
> David Blevins wrote:
> 
>> I don't know about others, but I was referring to an easy way to  
>> setup jetty or tomcat just once before people deploy apps.  As far as  
>> pre-deployed apps, no idea how to work that out.
>>
>> -David
>>
>> On Sep 26, 2005, at 6:29 PM, Joe Bohn wrote:
>>
>>> I'm still not sure if I completely understand the approach for  "easy 
>>> switching from Jetty->Tomcat".
>>> - If applications have already been deployed to say Jetty before  the 
>>> switch is made, then are they functional in Tomcat?
>>> - If not, can the same application be deployed in Tomcat such that  
>>> it doesn't affect the Jetty application if the switch is reversed  at 
>>> some time in the future?
>>> - Finally, how are applications that must be "pre-deployed" in each  
>>> container managed (for example example the web console)?
>>>
>>> Joe
>>>
>>> David Blevins wrote:
>>>
>>>> LAST ISSUES
>>>>   - Easy switching from Jetty -> Tomcat
>>>>   - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,   
>>>> ServiceMix=>Hiram, tmpOrb=>Dain)
>>>>   - Version number of some sort in the schemas?
>>>> Is there anything else people think *must* be there to ship?
>>>> THE FINAL STUFF
>>>> Again, we have to run the TCK on the final binary.   It would be   
>>>> great if we could cut the final release by Wednesday and be  
>>>> finished  TCK testing by Friday.  To get there we will have the  
>>>> standard  checklist of stuff to do:
>>>>  1. clean the jira
>>>>  2. create release notes
>>>>  3. update readme files
>>>>  4. Change the version number in etc/project.properties and the  
>>>> plugins
>>>>  5. Create our tag
>>>>  6. Cut and sign the binary and source distributions
>>>> Then it's just test and vote, both take two days and can be done  
>>>> at  the same time.
>>>> Any details I've missed?
>>>> -David
>>>>
>>>
>>> -- 
>>> Joe Bohn
>>> joe.bohn@earthlink.net
>>>
>>> "He is no fool who gives what he cannot keep, to gain what he  cannot 
>>> lose."   -- Jim Elliot
>>>
>>>
>>
>>
>>
>>
> 
> 
> 

-- 
Joe Bohn
joe.bohn@earthlink.net

"He is no fool who gives what he cannot keep, to gain what he cannot 
lose."   -- Jim Elliot