You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Hernan Cunico <hc...@gmail.com> on 2006/06/08 19:23:46 UTC

RELEASE-NOTES-1.1

Hi All,
I updated the release notes and it is ready for your review and comments, here is the link

http://cwiki.apache.org/GMOxDOC11/release-notes-11txt.html

Cheers!
Hernan

Re: RELEASE-NOTES-1.1

Posted by Hernan Cunico <hc...@gmail.com>.
Erin Mulder wrote:
> Hernan Cunico wrote:
> 
>>I updated the release notes and it is ready for your review
> 
> 
> Looks good!  A few comments:
> 
> 1) Under system requirements, I think it should mention that Geronimo
> will run fine on Java 5 out of the box, and offer the caveats that it is
> only J2EE-certified on 1.4 and that in particular, you will need to run
> under 1.4 if you enable CORBA support.

Could you work on a line or two to reword this section? Not too sure how to word it as we are 
telling we certified for 1.4 but it works fine with Java 5
> 
> 2) Under "Administration Console Security Configuration", it should
> mention that the username/password can be changed within the console
> itself.  e.g. "This can be changed through the console (in the "Security
> -> Console Realm" section) or by editing <geronimo_home>/var......"

DONE
> 
> 3) Looks like there's a typo in the "Deploying Applications" section.
> It says "<geronimo_home>/bin/java -jar....." instead of just "java
> -jar....."

Where is the typo? you mean we should not mention the directory here?
> 
> 4) In that same section, perhaps worth mentioning that you can run the
> login command in the deployer tool and not have to enter the password
> over and over.  It's kind of a minor detail, but constant retyping of
> passwords could ruin the deployment experience for people.

DONE. Login is a nice feature while testing although for production users may want to keep more 
control on the actual user deploying the apps.
> 
> 5) Under "Choice of Web container", it sounds a little open-ended to say
> "Please download the binary appropriate for your environment."  People
> will wonder what it is that makes one or the other appropriate for their
>  environment.   Not sure how to say it better, but perhaps indicate that
> choosing one at random is fine if you or your company don't already have
> a preference?

This is pretty much untouched from the previous release notes. I rephrased it a little bit but still 
is lacking of a good speech for choosing one container over the other. We have the same problem in 
the documentation, any ideas on how to better articulate the "pros and cons"?
> 
> Cheers,
> Erin
> 

Thanks for the comments.

Cheers!
Hernan

Re: RELEASE-NOTES-1.1

Posted by Erin Mulder <me...@alumni.princeton.edu>.
Hernan Cunico wrote:
> I updated the release notes and it is ready for your review

Looks good!  A few comments:

1) Under system requirements, I think it should mention that Geronimo
will run fine on Java 5 out of the box, and offer the caveats that it is
only J2EE-certified on 1.4 and that in particular, you will need to run
under 1.4 if you enable CORBA support.

2) Under "Administration Console Security Configuration", it should
mention that the username/password can be changed within the console
itself.  e.g. "This can be changed through the console (in the "Security
-> Console Realm" section) or by editing <geronimo_home>/var......"

3) Looks like there's a typo in the "Deploying Applications" section.
It says "<geronimo_home>/bin/java -jar....." instead of just "java
-jar....."

4) In that same section, perhaps worth mentioning that you can run the
login command in the deployer tool and not have to enter the password
over and over.  It's kind of a minor detail, but constant retyping of
passwords could ruin the deployment experience for people.

5) Under "Choice of Web container", it sounds a little open-ended to say
"Please download the binary appropriate for your environment."  People
will wonder what it is that makes one or the other appropriate for their
 environment.   Not sure how to say it better, but perhaps indicate that
choosing one at random is fine if you or your company don't already have
a preference?

Cheers,
Erin

Re: RELEASE-NOTES-1.1

Posted by Hernan Cunico <hc...@gmail.com>.
Dave Colasurdo wrote:
> 
>>> 2) In section "Significant Changes"
>>>
>>> -Shared Library Support
>>> -Statement Cache for JDBC drivers
>>> -Dynamic Plugin support
>>> -In-place deployment of exploded applications
>>> -Dependent Package Upgrades (Tomcat, Jetty, etc.)
>>
>>
>> DONE.
> 
> 
> Seems that 3 of the items above are missing from the release notes in 
> the 1.1 rc1 build?

These are now in (http://cwiki.apache.org/confluence/display/GMOxDOC11/RELEASE-NOTES-1.1.TXT). May 
need to elaborate more the last three or four bullets in the "Significant Changes Since the 1.0 
Release" section. Suggestions/comments?
> 
>>>
>>> 3)Also, probably want a new section on "Migrating applications from 
>>> previous releases" that references the existence of the Upgrade tool 
>>> that David J has created (and Lin is documenting) and any other major 
>>> differences that existing users will need to know.  It should link to 
>>> any other migration documentation that we have.
>>
>>
> 
> Didn't see any references/links to the "plan upgrade tool" in the 1.1 
> rc1 release notes?

It is now included in the "Significant Changes Since the 1.0 Release" section.

Cheers!
Hernan
> 
> Thanks
> -Dave-
> 

Re: RELEASE-NOTES-1.1

Posted by Dave Colasurdo <da...@earthlink.net>.
>> 2) In section "Significant Changes"
>>
>> -Shared Library Support
>> -Statement Cache for JDBC drivers
>> -Dynamic Plugin support
>> -In-place deployment of exploded applications
>> -Dependent Package Upgrades (Tomcat, Jetty, etc.)
> 
> DONE.

Seems that 3 of the items above are missing from the release notes in 
the 1.1 rc1 build?

>>
>> 3)Also, probably want a new section on "Migrating applications from 
>> previous releases" that references the existence of the Upgrade tool 
>> that David J has created (and Lin is documenting) and any other major 
>> differences that existing users will need to know.  It should link to 
>> any other migration documentation that we have.
> 

Didn't see any references/links to the "plan upgrade tool" in the 1.1 
rc1 release notes?

Thanks
-Dave-

Re: RELEASE-NOTES-1.1

Posted by Donald Woods <dr...@yahoo.com>.
Guess the exception output could be enhanced to include:
  - the module that failed to load (in case you were using the silent 
output option which doesn't list the modules being loaded)
  - clear statement that the server will now be shutdown because of this 
error
  - hint of how to fix the problem, like editing config.xml

Instead of the current output of -

 >Module 24/24 hello/1.1/war                      Exception in thread 
"main" java.lang.AssertionError: Expected one match for pattern ".", but
got 0 matches
 >        at
 >org.apache.geronimo.kernel.config.ConfigurationUtil.preprocessGBeanData(ConfigurationUtil.java:331)


I agree that you can't just automatically remove the offending 
application, but maybe a configuration option to "continue on error" 
would be useful while you are developing your app, so you can then 
undeploy or redeploy the offending app...


-Donald


Gianny Damour wrote:
> Hi Donald,
> 
> There are very good points. How would you expect the server to behave in 
> such scenarios? Currently the server will simply shut-down and, to some 
> extent, I think that this is a safe behaviour.
> 
> Thanks,
> Gianny
> 
> Donald Woods wrote:
> 
>> What happens in the case that the files no longer exist on the next 
>> server startup?  Two scenarios I'm worried about:
>> 1) files were loaded from an NFS/Samba/SMB share which has become 
>> disconnected
>> 2) Eclipse users who deploy the app into the server, test it, stop the 
>> server and then delete the project and files from Eclipse
>>
>>
>> -Donald
>>
>>
>> Aaron Mulder wrote:
>>
>>> On 6/13/06, Lin Sun <li...@gmail.com> wrote:
>>>
>>>> I am trying to learn what the in-place deployment mean and how to 
>>>> use it.
>>>> My understanding was that users can update the hot deploy files (for
>>>> example, update one jsp file) in the Geronimo_home\deploy directory and
>>>> server will redeploy the change automatically.   This was not 
>>>> working in
>>>> 1.0, as users need to replace the entire directory in the
>>>> Geronimo_home\deploy directory.
>>>
>>>
>>>
>>>
>>> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
>>>
>>> But in 1.1, there is a separate option, which is to not copy your
>>> files to the hot deploy directory at all, but instead use the deploy
>>> tool with a special option to enable an in-place deployment.  This
>>> means that instead of copying your files into the server directory at
>>> all, it will deploy and access them from wherever they currently are.
>>>
>>> Thanks,
>>>    Aaron
>>>
>>>> But after reading your note below, I think I am lost.   Please advise.
>>>>
>>>> Lin
>>>>
>>>> -----Original Message-----
>>>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>>>> Mulder
>>>> Sent: Thursday, June 08, 2006 7:23 PM
>>>> To: dev@geronimo.apache.org
>>>> Subject: Re: RELEASE-NOTES-1.1
>>>>
>>>>  - We should add a point about in-place deployment.  "Geronimo
>>>> supports in-place deployment, which means an archive or directory can
>>>> be deployed without being copied into the Geronimo directory tree."
>>>>
>>>>
>>>>
>>>>
>>>
>>>
> 
> 
> 
> 

Re: RELEASE-NOTES-1.1

Posted by Gianny Damour <gi...@optusnet.com.au>.
Hi Donald,

There are very good points. How would you expect the server to behave in 
such scenarios? Currently the server will simply shut-down and, to some 
extent, I think that this is a safe behaviour.

Thanks,
Gianny

Donald Woods wrote:

> What happens in the case that the files no longer exist on the next 
> server startup?  Two scenarios I'm worried about:
> 1) files were loaded from an NFS/Samba/SMB share which has become 
> disconnected
> 2) Eclipse users who deploy the app into the server, test it, stop the 
> server and then delete the project and files from Eclipse
>
>
> -Donald
>
>
> Aaron Mulder wrote:
>
>> On 6/13/06, Lin Sun <li...@gmail.com> wrote:
>>
>>> I am trying to learn what the in-place deployment mean and how to 
>>> use it.
>>> My understanding was that users can update the hot deploy files (for
>>> example, update one jsp file) in the Geronimo_home\deploy directory and
>>> server will redeploy the change automatically.   This was not 
>>> working in
>>> 1.0, as users need to replace the entire directory in the
>>> Geronimo_home\deploy directory.
>>
>>
>>
>> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
>>
>> But in 1.1, there is a separate option, which is to not copy your
>> files to the hot deploy directory at all, but instead use the deploy
>> tool with a special option to enable an in-place deployment.  This
>> means that instead of copying your files into the server directory at
>> all, it will deploy and access them from wherever they currently are.
>>
>> Thanks,
>>    Aaron
>>
>>> But after reading your note below, I think I am lost.   Please advise.
>>>
>>> Lin
>>>
>>> -----Original Message-----
>>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>>> Mulder
>>> Sent: Thursday, June 08, 2006 7:23 PM
>>> To: dev@geronimo.apache.org
>>> Subject: Re: RELEASE-NOTES-1.1
>>>
>>>  - We should add a point about in-place deployment.  "Geronimo
>>> supports in-place deployment, which means an archive or directory can
>>> be deployed without being copied into the Geronimo directory tree."
>>>
>>>
>>>
>>>
>>
>>



Re: RELEASE-NOTES-1.1

Posted by Sachin Patel <sp...@gmail.com>.
On Jun 13, 2006, at 3:11 PM, Donald Woods wrote:

> 2) Eclipse users who deploy the app into the server, test it, stop  
> the server and then delete the project and files from Eclipse

Won't be an issue.  For apps running resources directly from the  
workspace/project, these apps will be deployed to a separate config- 
store and will be non-persistant.


-sachin



RE: RELEASE-NOTES-1.1

Posted by Lin Sun <li...@gmail.com>.
Good point!  I shutdown the server and renamed the hello directory.  Then
start the server afterwards.  I saw the following exception when server
attempted to start the hello module.  I didn't see Geronimo server started
at the end but luckily all the important module seemed to be started before
my little hello module, which is the last in var\config\config.xml file.

Module 24/24 hello/1.1/war                      Exception in threa
d "main" java.lang.AssertionError: Expected one match for pattern ".", but
got 0
 matches
        at
org.apache.geronimo.kernel.config.ConfigurationUtil.preprocessGBeanDa
ta(ConfigurationUtil.java:331)
        at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:359)
        at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
rnelConfigurationManager.java:187)
        at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:512)
        at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:493)
        at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
ssByCGLIB$$ce77a924.invoke(<generated>)
        at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java(Inlined
Compil
ed Code))
        at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
Invoker.java(Compiled Code))
        at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java(Inlined Compiled Code))
        at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java(Compiled Code))
        at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java(I
nlined Compiled Code))
        at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
ionInvoker.java(Compiled Code))
        at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
xyMethodInterceptor.java(Compiled Code))
        at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
cerByCGLIB$$f05707cd.startConfiguration(<generated>)
        at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
        at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
        at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)

I guess this error can be improved in the future releases, but for 1.1 user
needs to be good aware of what inPlace means before they use it for 1.1.

I hope this is less of a problem for scenario #2, as I am not aware of the
in-place option to deploy a project in Eclipse/WTP but Sachin can certainly
correct me as I haven't tried the 1.1 version of the Eclipse plugins yet.

Lin

-----Original Message-----
From: Donald Woods [mailto:drw_web@yahoo.com] 
Sent: Tuesday, June 13, 2006 3:12 PM
To: dev@geronimo.apache.org
Subject: Re: RELEASE-NOTES-1.1

What happens in the case that the files no longer exist on the next 
server startup?  Two scenarios I'm worried about:
1) files were loaded from an NFS/Samba/SMB share which has become 
disconnected
2) Eclipse users who deploy the app into the server, test it, stop the 
server and then delete the project and files from Eclipse


-Donald


Aaron Mulder wrote:
> On 6/13/06, Lin Sun <li...@gmail.com> wrote:
> 
>> I am trying to learn what the in-place deployment mean and how to use it.
>> My understanding was that users can update the hot deploy files (for
>> example, update one jsp file) in the Geronimo_home\deploy directory and
>> server will redeploy the change automatically.   This was not working in
>> 1.0, as users need to replace the entire directory in the
>> Geronimo_home\deploy directory.
> 
> 
> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
> 
> But in 1.1, there is a separate option, which is to not copy your
> files to the hot deploy directory at all, but instead use the deploy
> tool with a special option to enable an in-place deployment.  This
> means that instead of copying your files into the server directory at
> all, it will deploy and access them from wherever they currently are.
> 
> Thanks,
>    Aaron
> 
>> But after reading your note below, I think I am lost.   Please advise.
>>
>> Lin
>>
>> -----Original Message-----
>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>> Mulder
>> Sent: Thursday, June 08, 2006 7:23 PM
>> To: dev@geronimo.apache.org
>> Subject: Re: RELEASE-NOTES-1.1
>>
>>  - We should add a point about in-place deployment.  "Geronimo
>> supports in-place deployment, which means an archive or directory can
>> be deployed without being copied into the Geronimo directory tree."
>>
>>
>>
>>
> 
> 


Re: RELEASE-NOTES-1.1

Posted by Donald Woods <dr...@yahoo.com>.
What happens in the case that the files no longer exist on the next 
server startup?  Two scenarios I'm worried about:
1) files were loaded from an NFS/Samba/SMB share which has become 
disconnected
2) Eclipse users who deploy the app into the server, test it, stop the 
server and then delete the project and files from Eclipse


-Donald


Aaron Mulder wrote:
> On 6/13/06, Lin Sun <li...@gmail.com> wrote:
> 
>> I am trying to learn what the in-place deployment mean and how to use it.
>> My understanding was that users can update the hot deploy files (for
>> example, update one jsp file) in the Geronimo_home\deploy directory and
>> server will redeploy the change automatically.   This was not working in
>> 1.0, as users need to replace the entire directory in the
>> Geronimo_home\deploy directory.
> 
> 
> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
> 
> But in 1.1, there is a separate option, which is to not copy your
> files to the hot deploy directory at all, but instead use the deploy
> tool with a special option to enable an in-place deployment.  This
> means that instead of copying your files into the server directory at
> all, it will deploy and access them from wherever they currently are.
> 
> Thanks,
>    Aaron
> 
>> But after reading your note below, I think I am lost.   Please advise.
>>
>> Lin
>>
>> -----Original Message-----
>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>> Mulder
>> Sent: Thursday, June 08, 2006 7:23 PM
>> To: dev@geronimo.apache.org
>> Subject: Re: RELEASE-NOTES-1.1
>>
>>  - We should add a point about in-place deployment.  "Geronimo
>> supports in-place deployment, which means an archive or directory can
>> be deployed without being copied into the Geronimo directory tree."
>>
>>
>>
>>
> 
> 

Re: in-place deployment

Posted by Gianny Damour <gi...@optusnet.com.au>.
Hi Sachin,

Thanks for pointing this problem out. I just tried an in-place 
deployment of a stand-alone EJB module and it (still) does not work. I 
have identified the problem; in a few words, the installation 
(OpenEJBModuleBuilder.install) of in-place and standalone EJB is wrong 
as the target should be URI.create("") and not 
URI.create(module.getTargetPath()).

The work around is to put the EJB within an EAR and deploy in-place the 
EAR. This is not ideal and will be fixed for 1.1.1.

Sorry for this problem.

Thanks,
Gianny

Sachin Patel wrote:

> It should probably be release-noted that in-place deployment does not  
> work with stand-alone ejb jars. (At least the last time I tried it  
> failed).  So it may very well be that it only works for stand- alone 
> .wars or ears containing only web modules.
>
> On Jun 14, 2006, at 8:46 AM, Gianny Damour wrote:
>
>> Hi Lin,
>>
>> I just checked and you can do:
>> $ java -jar bin/deployer.jar help distribute
>>
>> Command-line deployer syntax:
>>    deployer [general options] command [command options]
>>
>> Help for command: distribute
>>
>>    deployer distribute [--inPlace] [--targets target;target;...]
>>             [module] [plan]
>>
>> <...>
>>
>>        If inPlace is provided, the module is not copied to the
>>        configuration store of the selected targets. The targets
>>        directly use the module.
>>
>>
>> The help for the deploy command identifies the --inPlace flag but  
>> does not provide a description for it.
>>
>> Thanks,
>> Gianny
>>
>>
>> Lin Sun wrote:
>>
>>> Thanks.  I executed deploy.bat but didn't see the -inPlace option  
>>> from the
>>> help menu.  Should we add this option to the output of executing  
>>> deploy.bat?
>>>
>>> Then I saw David Jenck's article
>>> (http://opensource.atlassian.com/confluence/oss/display/GERONIMO/ 
>>> Exposing+We
>>> b+Applications+on+distinct+ports), so I figured out I can just call
>>> "deploy.bat deploy --inPlace" to use it.  What I found out is if I  
>>> execute:
>>>
>>> deploy.bat deploy --inPlace path\hello.war
>>>
>>> I got the following error:
>>>    Error: Unable to distribute hello-1.1.war: In place deployment is
>>>    not allowed for packed module
>>>
>>> Then I tried:
>>> deploy.bat deploy --inPlace path\hello
>>> and it worked well.  I did see David used an ear file as the last  
>>> parameter
>>> in the example given in the article...
>>>
>>> Lin
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of  
>>> Aaron
>>> Mulder
>>> Sent: Tuesday, June 13, 2006 2:42 PM
>>> To: dev@geronimo.apache.org
>>> Subject: Re: RELEASE-NOTES-1.1
>>>
>>> On 6/13/06, Lin Sun <li...@gmail.com> wrote:
>>>
>>>> I am trying to learn what the in-place deployment mean and how to  
>>>> use it.
>>>> My understanding was that users can update the hot deploy files (for
>>>> example, update one jsp file) in the Geronimo_home\deploy  
>>>> directory and
>>>> server will redeploy the change automatically.   This was not  
>>>> working in
>>>> 1.0, as users need to replace the entire directory in the
>>>> Geronimo_home\deploy directory.
>>>>
>>>
>>> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
>>>
>>> But in 1.1, there is a separate option, which is to not copy your
>>> files to the hot deploy directory at all, but instead use the deploy
>>> tool with a special option to enable an in-place deployment.  This
>>> means that instead of copying your files into the server directory at
>>> all, it will deploy and access them from wherever they currently are.
>>>
>>> Thanks,
>>>    Aaron
>>>
>>>
>>>> But after reading your note below, I think I am lost.   Please  
>>>> advise.
>>>>
>>>> Lin
>>>>
>>>> -----Original Message-----
>>>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of  
>>>> Aaron
>>>> Mulder
>>>> Sent: Thursday, June 08, 2006 7:23 PM
>>>> To: dev@geronimo.apache.org
>>>> Subject: Re: RELEASE-NOTES-1.1
>>>>
>>>> - We should add a point about in-place deployment.  "Geronimo
>>>> supports in-place deployment, which means an archive or directory  can
>>>> be deployed without being copied into the Geronimo directory tree."
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
> -sachin
>
>
>
>



Re: in-place deployment

Posted by David Jencks <da...@yahoo.com>.
On Jun 14, 2006, at 8:13 AM, Lin Sun wrote:

> I could not get it work with .war file either.   But I do see David  
> Jencks
> gave the following as an example in his article (see link below):
>
> java -jar bin/deployer.jar deploy --inPlace appPerPort.ear
>
> Maybe David got it working at one point or it just work with ear file?

IIRC that was the only example I tried.

thanks
david jencks

>
> Lin
>
> -----Original Message-----
> From: Sachin Patel [mailto:sppatel@gmail.com] On Behalf Of Sachin  
> Patel
> Sent: Wednesday, June 14, 2006 9:11 AM
> To: user@geronimo.apache.org
> Subject: Re: in-place deployment
>
> It should probably be release-noted that in-place deployment does not
> work with stand-alone ejb jars. (At least the last time I tried it
> failed).  So it may very well be that it only works for stand-
> alone .wars or ears containing only web modules.
>
> On Jun 14, 2006, at 8:46 AM, Gianny Damour wrote:
>
>> Hi Lin,
>>
>> I just checked and you can do:
>> $ java -jar bin/deployer.jar help distribute
>>
>> Command-line deployer syntax:
>>    deployer [general options] command [command options]
>>
>> Help for command: distribute
>>
>>    deployer distribute [--inPlace] [--targets target;target;...]
>>             [module] [plan]
>>
>> <...>
>>
>>        If inPlace is provided, the module is not copied to the
>>        configuration store of the selected targets. The targets
>>        directly use the module.
>>
>>
>> The help for the deploy command identifies the --inPlace flag but
>> does not provide a description for it.
>>
>> Thanks,
>> Gianny
>>
>>
>> Lin Sun wrote:
>>
>>> Thanks.  I executed deploy.bat but didn't see the -inPlace option
>>> from the
>>> help menu.  Should we add this option to the output of executing
>>> deploy.bat?
>>>
>>> Then I saw David Jenck's article
>>> (http://opensource.atlassian.com/confluence/oss/display/GERONIMO/
>>> Exposing+We
>>> b+Applications+on+distinct+ports), so I figured out I can just call
>>> "deploy.bat deploy --inPlace" to use it.  What I found out is if I
>>> execute:
>>>
>>> deploy.bat deploy --inPlace path\hello.war
>>>
>>> I got the following error:
>>>    Error: Unable to distribute hello-1.1.war: In place deployment is
>>>    not allowed for packed module
>>>
>>> Then I tried:
>>> deploy.bat deploy --inPlace path\hello
>>> and it worked well.  I did see David used an ear file as the last
>>> parameter
>>> in the example given in the article...
>>>
>>> Lin
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of
>>> Aaron
>>> Mulder
>>> Sent: Tuesday, June 13, 2006 2:42 PM
>>> To: dev@geronimo.apache.org
>>> Subject: Re: RELEASE-NOTES-1.1
>>>
>>> On 6/13/06, Lin Sun <li...@gmail.com> wrote:
>>>
>>>> I am trying to learn what the in-place deployment mean and how to
>>>> use it.
>>>> My understanding was that users can update the hot deploy files  
>>>> (for
>>>> example, update one jsp file) in the Geronimo_home\deploy
>>>> directory and
>>>> server will redeploy the change automatically.   This was not
>>>> working in
>>>> 1.0, as users need to replace the entire directory in the
>>>> Geronimo_home\deploy directory.
>>>>
>>>
>>> That should be true in both 1.0 and 1.1 (if not, I guess it's a  
>>> bug).
>>>
>>> But in 1.1, there is a separate option, which is to not copy your
>>> files to the hot deploy directory at all, but instead use the deploy
>>> tool with a special option to enable an in-place deployment.  This
>>> means that instead of copying your files into the server  
>>> directory at
>>> all, it will deploy and access them from wherever they currently  
>>> are.
>>>
>>> Thanks,
>>>    Aaron
>>>
>>>
>>>> But after reading your note below, I think I am lost.   Please
>>>> advise.
>>>>
>>>> Lin
>>>>
>>>> -----Original Message-----
>>>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of
>>>> Aaron
>>>> Mulder
>>>> Sent: Thursday, June 08, 2006 7:23 PM
>>>> To: dev@geronimo.apache.org
>>>> Subject: Re: RELEASE-NOTES-1.1
>>>>
>>>> - We should add a point about in-place deployment.  "Geronimo
>>>> supports in-place deployment, which means an archive or directory
>>>> can
>>>> be deployed without being copied into the Geronimo directory tree."
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
> -sachin
>
>


RE: in-place deployment

Posted by Lin Sun <li...@gmail.com>.
I could not get it work with .war file either.   But I do see David Jencks
gave the following as an example in his article (see link below):

java -jar bin/deployer.jar deploy --inPlace appPerPort.ear

Maybe David got it working at one point or it just work with ear file?

Lin

-----Original Message-----
From: Sachin Patel [mailto:sppatel@gmail.com] On Behalf Of Sachin Patel
Sent: Wednesday, June 14, 2006 9:11 AM
To: user@geronimo.apache.org
Subject: Re: in-place deployment

It should probably be release-noted that in-place deployment does not  
work with stand-alone ejb jars. (At least the last time I tried it  
failed).  So it may very well be that it only works for stand- 
alone .wars or ears containing only web modules.

On Jun 14, 2006, at 8:46 AM, Gianny Damour wrote:

> Hi Lin,
>
> I just checked and you can do:
> $ java -jar bin/deployer.jar help distribute
>
> Command-line deployer syntax:
>    deployer [general options] command [command options]
>
> Help for command: distribute
>
>    deployer distribute [--inPlace] [--targets target;target;...]
>             [module] [plan]
>
> <...>
>
>        If inPlace is provided, the module is not copied to the
>        configuration store of the selected targets. The targets
>        directly use the module.
>
>
> The help for the deploy command identifies the --inPlace flag but  
> does not provide a description for it.
>
> Thanks,
> Gianny
>
>
> Lin Sun wrote:
>
>> Thanks.  I executed deploy.bat but didn't see the -inPlace option  
>> from the
>> help menu.  Should we add this option to the output of executing  
>> deploy.bat?
>>
>> Then I saw David Jenck's article
>> (http://opensource.atlassian.com/confluence/oss/display/GERONIMO/ 
>> Exposing+We
>> b+Applications+on+distinct+ports), so I figured out I can just call
>> "deploy.bat deploy --inPlace" to use it.  What I found out is if I  
>> execute:
>>
>> deploy.bat deploy --inPlace path\hello.war
>>
>> I got the following error:
>>    Error: Unable to distribute hello-1.1.war: In place deployment is
>>    not allowed for packed module
>>
>> Then I tried:
>> deploy.bat deploy --inPlace path\hello
>> and it worked well.  I did see David used an ear file as the last  
>> parameter
>> in the example given in the article...
>>
>> Lin
>>
>>
>>
>> -----Original Message-----
>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of  
>> Aaron
>> Mulder
>> Sent: Tuesday, June 13, 2006 2:42 PM
>> To: dev@geronimo.apache.org
>> Subject: Re: RELEASE-NOTES-1.1
>>
>> On 6/13/06, Lin Sun <li...@gmail.com> wrote:
>>
>>> I am trying to learn what the in-place deployment mean and how to  
>>> use it.
>>> My understanding was that users can update the hot deploy files (for
>>> example, update one jsp file) in the Geronimo_home\deploy  
>>> directory and
>>> server will redeploy the change automatically.   This was not  
>>> working in
>>> 1.0, as users need to replace the entire directory in the
>>> Geronimo_home\deploy directory.
>>>
>>
>> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
>>
>> But in 1.1, there is a separate option, which is to not copy your
>> files to the hot deploy directory at all, but instead use the deploy
>> tool with a special option to enable an in-place deployment.  This
>> means that instead of copying your files into the server directory at
>> all, it will deploy and access them from wherever they currently are.
>>
>> Thanks,
>>    Aaron
>>
>>
>>> But after reading your note below, I think I am lost.   Please  
>>> advise.
>>>
>>> Lin
>>>
>>> -----Original Message-----
>>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of  
>>> Aaron
>>> Mulder
>>> Sent: Thursday, June 08, 2006 7:23 PM
>>> To: dev@geronimo.apache.org
>>> Subject: Re: RELEASE-NOTES-1.1
>>>
>>> - We should add a point about in-place deployment.  "Geronimo
>>> supports in-place deployment, which means an archive or directory  
>>> can
>>> be deployed without being copied into the Geronimo directory tree."
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>


-sachin



Re: in-place deployment

Posted by Sachin Patel <sp...@gmail.com>.
It should probably be release-noted that in-place deployment does not  
work with stand-alone ejb jars. (At least the last time I tried it  
failed).  So it may very well be that it only works for stand- 
alone .wars or ears containing only web modules.

On Jun 14, 2006, at 8:46 AM, Gianny Damour wrote:

> Hi Lin,
>
> I just checked and you can do:
> $ java -jar bin/deployer.jar help distribute
>
> Command-line deployer syntax:
>    deployer [general options] command [command options]
>
> Help for command: distribute
>
>    deployer distribute [--inPlace] [--targets target;target;...]
>             [module] [plan]
>
> <...>
>
>        If inPlace is provided, the module is not copied to the
>        configuration store of the selected targets. The targets
>        directly use the module.
>
>
> The help for the deploy command identifies the --inPlace flag but  
> does not provide a description for it.
>
> Thanks,
> Gianny
>
>
> Lin Sun wrote:
>
>> Thanks.  I executed deploy.bat but didn't see the -inPlace option  
>> from the
>> help menu.  Should we add this option to the output of executing  
>> deploy.bat?
>>
>> Then I saw David Jenck's article
>> (http://opensource.atlassian.com/confluence/oss/display/GERONIMO/ 
>> Exposing+We
>> b+Applications+on+distinct+ports), so I figured out I can just call
>> "deploy.bat deploy --inPlace" to use it.  What I found out is if I  
>> execute:
>>
>> deploy.bat deploy --inPlace path\hello.war
>>
>> I got the following error:
>>    Error: Unable to distribute hello-1.1.war: In place deployment is
>>    not allowed for packed module
>>
>> Then I tried:
>> deploy.bat deploy --inPlace path\hello
>> and it worked well.  I did see David used an ear file as the last  
>> parameter
>> in the example given in the article...
>>
>> Lin
>>
>>
>>
>> -----Original Message-----
>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of  
>> Aaron
>> Mulder
>> Sent: Tuesday, June 13, 2006 2:42 PM
>> To: dev@geronimo.apache.org
>> Subject: Re: RELEASE-NOTES-1.1
>>
>> On 6/13/06, Lin Sun <li...@gmail.com> wrote:
>>
>>> I am trying to learn what the in-place deployment mean and how to  
>>> use it.
>>> My understanding was that users can update the hot deploy files (for
>>> example, update one jsp file) in the Geronimo_home\deploy  
>>> directory and
>>> server will redeploy the change automatically.   This was not  
>>> working in
>>> 1.0, as users need to replace the entire directory in the
>>> Geronimo_home\deploy directory.
>>>
>>
>> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
>>
>> But in 1.1, there is a separate option, which is to not copy your
>> files to the hot deploy directory at all, but instead use the deploy
>> tool with a special option to enable an in-place deployment.  This
>> means that instead of copying your files into the server directory at
>> all, it will deploy and access them from wherever they currently are.
>>
>> Thanks,
>>    Aaron
>>
>>
>>> But after reading your note below, I think I am lost.   Please  
>>> advise.
>>>
>>> Lin
>>>
>>> -----Original Message-----
>>> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of  
>>> Aaron
>>> Mulder
>>> Sent: Thursday, June 08, 2006 7:23 PM
>>> To: dev@geronimo.apache.org
>>> Subject: Re: RELEASE-NOTES-1.1
>>>
>>> - We should add a point about in-place deployment.  "Geronimo
>>> supports in-place deployment, which means an archive or directory  
>>> can
>>> be deployed without being copied into the Geronimo directory tree."
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>


-sachin



Re: in-place deployment

Posted by Sachin Patel <sp...@gmail.com>.
We should remove this statement or better fix the problem...  
Currently this can't be done, nor currently does it make sense to  
do.  By default yes, it will go though a "attempt" to deploy to all  
targets, but before deploying to a given target, I think it checks  
that the given app hasn't been deployed to any other store.  So an  
app can be deployed to at most one store.

On Jun 14, 2006, at 10:51 AM, Lin Sun wrote:

> If no targets are provided, the module is deployed to all
>         available targets


-sachin



RE: in-place deployment

Posted by Lin Sun <li...@gmail.com>.
Hi Gianny,

Thanks for checking that.  I was expecting to see it under the general
options after I typed deploy.bat to see the usage.   Then I was expecting to
see it after I typed " deploy.bat help deploy".  I did see the option there
but there is no explanation. 


Command-line deployer syntax:
    deployer [general options] command [command options]

Help for command: deploy

    deployer deploy [--inPlace] [--targets target;target;...] [module]
             [plan]


        Normally both a module and plan are passed to the deployer.
        Sometimes the module contains a plan, or requires no plan, in
        which case the plan may be omitted.  Sometimes the plan
        references a module already deployed in the Geronimo server
        environment, in which case a module does not need to be
        provided.

        If no targets are provided, the module is deployed to all
        available targets.  Geronimo only provides one target (ever), so
        this is primarily useful when using a different driver.

It is best that we make them consistent as I seldom use the distribute
command.  The other thing is that I found out the --inPlace option only
accept directory name, and doesn't allow for packed module.  It would be
nice to mention this too, if this is true.

Thanks, 
Lin

-----Original Message-----
From: Gianny Damour [mailto:gianny.damour@optusnet.com.au] 
Sent: Wednesday, June 14, 2006 8:47 AM
To: user@geronimo.apache.org
Subject: Re: in-place deployment

Hi Lin,

I just checked and you can do:
$ java -jar bin/deployer.jar help distribute

Command-line deployer syntax:
    deployer [general options] command [command options]

Help for command: distribute

    deployer distribute [--inPlace] [--targets target;target;...]
             [module] [plan]

<...>

        If inPlace is provided, the module is not copied to the
        configuration store of the selected targets. The targets
        directly use the module.


The help for the deploy command identifies the --inPlace flag but does 
not provide a description for it.

Thanks,
Gianny


Lin Sun wrote:

>Thanks.  I executed deploy.bat but didn't see the -inPlace option from the
>help menu.  Should we add this option to the output of executing
deploy.bat?
>
>Then I saw David Jenck's article
>(http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Exposing+W
e
>b+Applications+on+distinct+ports), so I figured out I can just call
>"deploy.bat deploy --inPlace" to use it.  What I found out is if I execute:
>
>deploy.bat deploy --inPlace path\hello.war
>
>I got the following error:
>    Error: Unable to distribute hello-1.1.war: In place deployment is
>    not allowed for packed module
>
>Then I tried:
>deploy.bat deploy --inPlace path\hello 
>
>and it worked well.  I did see David used an ear file as the last parameter
>in the example given in the article...
>
>Lin
>
>
>
>-----Original Message-----
>From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>Mulder
>Sent: Tuesday, June 13, 2006 2:42 PM
>To: dev@geronimo.apache.org
>Subject: Re: RELEASE-NOTES-1.1
>
>On 6/13/06, Lin Sun <li...@gmail.com> wrote:
>  
>
>>I am trying to learn what the in-place deployment mean and how to use it.
>>My understanding was that users can update the hot deploy files (for
>>example, update one jsp file) in the Geronimo_home\deploy directory and
>>server will redeploy the change automatically.   This was not working in
>>1.0, as users need to replace the entire directory in the
>>Geronimo_home\deploy directory.
>>    
>>
>
>That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
>
>But in 1.1, there is a separate option, which is to not copy your
>files to the hot deploy directory at all, but instead use the deploy
>tool with a special option to enable an in-place deployment.  This
>means that instead of copying your files into the server directory at
>all, it will deploy and access them from wherever they currently are.
>
>Thanks,
>    Aaron
>
>  
>
>>But after reading your note below, I think I am lost.   Please advise.
>>
>>Lin
>>
>>-----Original Message-----
>>From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>>Mulder
>>Sent: Thursday, June 08, 2006 7:23 PM
>>To: dev@geronimo.apache.org
>>Subject: Re: RELEASE-NOTES-1.1
>>
>> - We should add a point about in-place deployment.  "Geronimo
>>supports in-place deployment, which means an archive or directory can
>>be deployed without being copied into the Geronimo directory tree."
>>
>>
>>
>>
>>    
>>
>
>
>
>
>  
>



Re: in-place deployment

Posted by Gianny Damour <gi...@optusnet.com.au>.
Hi Lin,

I just checked and you can do:
$ java -jar bin/deployer.jar help distribute

Command-line deployer syntax:
    deployer [general options] command [command options]

Help for command: distribute

    deployer distribute [--inPlace] [--targets target;target;...]
             [module] [plan]

<...>

        If inPlace is provided, the module is not copied to the
        configuration store of the selected targets. The targets
        directly use the module.


The help for the deploy command identifies the --inPlace flag but does 
not provide a description for it.

Thanks,
Gianny


Lin Sun wrote:

>Thanks.  I executed deploy.bat but didn't see the -inPlace option from the
>help menu.  Should we add this option to the output of executing deploy.bat?
>
>Then I saw David Jenck's article
>(http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Exposing+We
>b+Applications+on+distinct+ports), so I figured out I can just call
>"deploy.bat deploy --inPlace" to use it.  What I found out is if I execute:
>
>deploy.bat deploy --inPlace path\hello.war
>
>I got the following error:
>    Error: Unable to distribute hello-1.1.war: In place deployment is
>    not allowed for packed module
>
>Then I tried:
>deploy.bat deploy --inPlace path\hello 
>
>and it worked well.  I did see David used an ear file as the last parameter
>in the example given in the article...
>
>Lin
>
>
>
>-----Original Message-----
>From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>Mulder
>Sent: Tuesday, June 13, 2006 2:42 PM
>To: dev@geronimo.apache.org
>Subject: Re: RELEASE-NOTES-1.1
>
>On 6/13/06, Lin Sun <li...@gmail.com> wrote:
>  
>
>>I am trying to learn what the in-place deployment mean and how to use it.
>>My understanding was that users can update the hot deploy files (for
>>example, update one jsp file) in the Geronimo_home\deploy directory and
>>server will redeploy the change automatically.   This was not working in
>>1.0, as users need to replace the entire directory in the
>>Geronimo_home\deploy directory.
>>    
>>
>
>That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
>
>But in 1.1, there is a separate option, which is to not copy your
>files to the hot deploy directory at all, but instead use the deploy
>tool with a special option to enable an in-place deployment.  This
>means that instead of copying your files into the server directory at
>all, it will deploy and access them from wherever they currently are.
>
>Thanks,
>    Aaron
>
>  
>
>>But after reading your note below, I think I am lost.   Please advise.
>>
>>Lin
>>
>>-----Original Message-----
>>From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>>Mulder
>>Sent: Thursday, June 08, 2006 7:23 PM
>>To: dev@geronimo.apache.org
>>Subject: Re: RELEASE-NOTES-1.1
>>
>> - We should add a point about in-place deployment.  "Geronimo
>>supports in-place deployment, which means an archive or directory can
>>be deployed without being copied into the Geronimo directory tree."
>>
>>
>>
>>
>>    
>>
>
>
>
>
>  
>



in-place deployment

Posted by Lin Sun <li...@gmail.com>.
Thanks.  I executed deploy.bat but didn't see the -inPlace option from the
help menu.  Should we add this option to the output of executing deploy.bat?

Then I saw David Jenck's article
(http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Exposing+We
b+Applications+on+distinct+ports), so I figured out I can just call
"deploy.bat deploy --inPlace" to use it.  What I found out is if I execute:

deploy.bat deploy --inPlace path\hello.war

I got the following error:
    Error: Unable to distribute hello-1.1.war: In place deployment is
    not allowed for packed module

Then I tried:
deploy.bat deploy --inPlace path\hello 

and it worked well.  I did see David used an ear file as the last parameter
in the example given in the article...

Lin



-----Original Message-----
From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
Mulder
Sent: Tuesday, June 13, 2006 2:42 PM
To: dev@geronimo.apache.org
Subject: Re: RELEASE-NOTES-1.1

On 6/13/06, Lin Sun <li...@gmail.com> wrote:
> I am trying to learn what the in-place deployment mean and how to use it.
> My understanding was that users can update the hot deploy files (for
> example, update one jsp file) in the Geronimo_home\deploy directory and
> server will redeploy the change automatically.   This was not working in
> 1.0, as users need to replace the entire directory in the
> Geronimo_home\deploy directory.

That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).

But in 1.1, there is a separate option, which is to not copy your
files to the hot deploy directory at all, but instead use the deploy
tool with a special option to enable an in-place deployment.  This
means that instead of copying your files into the server directory at
all, it will deploy and access them from wherever they currently are.

Thanks,
    Aaron

> But after reading your note below, I think I am lost.   Please advise.
>
> Lin
>
> -----Original Message-----
> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
> Mulder
> Sent: Thursday, June 08, 2006 7:23 PM
> To: dev@geronimo.apache.org
> Subject: Re: RELEASE-NOTES-1.1
>
>  - We should add a point about in-place deployment.  "Geronimo
> supports in-place deployment, which means an archive or directory can
> be deployed without being copied into the Geronimo directory tree."
>
>
>
>


Re: RELEASE-NOTES-1.1

Posted by Aaron Mulder <am...@alumni.princeton.edu>.
On 6/13/06, Lin Sun <li...@gmail.com> wrote:
> I am trying to learn what the in-place deployment mean and how to use it.
> My understanding was that users can update the hot deploy files (for
> example, update one jsp file) in the Geronimo_home\deploy directory and
> server will redeploy the change automatically.   This was not working in
> 1.0, as users need to replace the entire directory in the
> Geronimo_home\deploy directory.

That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).

But in 1.1, there is a separate option, which is to not copy your
files to the hot deploy directory at all, but instead use the deploy
tool with a special option to enable an in-place deployment.  This
means that instead of copying your files into the server directory at
all, it will deploy and access them from wherever they currently are.

Thanks,
    Aaron

> But after reading your note below, I think I am lost.   Please advise.
>
> Lin
>
> -----Original Message-----
> From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
> Mulder
> Sent: Thursday, June 08, 2006 7:23 PM
> To: dev@geronimo.apache.org
> Subject: Re: RELEASE-NOTES-1.1
>
>  - We should add a point about in-place deployment.  "Geronimo
> supports in-place deployment, which means an archive or directory can
> be deployed without being copied into the Geronimo directory tree."
>
>
>
>

RE: RELEASE-NOTES-1.1

Posted by Lin Sun <li...@gmail.com>.
Hi Aaron,

I am trying to learn what the in-place deployment mean and how to use it.
My understanding was that users can update the hot deploy files (for
example, update one jsp file) in the Geronimo_home\deploy directory and
server will redeploy the change automatically.   This was not working in
1.0, as users need to replace the entire directory in the
Geronimo_home\deploy directory.

But after reading your note below, I think I am lost.   Please advise.

Lin

-----Original Message-----
From: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
Mulder
Sent: Thursday, June 08, 2006 7:23 PM
To: dev@geronimo.apache.org
Subject: Re: RELEASE-NOTES-1.1

 - We should add a point about in-place deployment.  "Geronimo
supports in-place deployment, which means an archive or directory can
be deployed without being copied into the Geronimo directory tree."




Re: RELEASE-NOTES-1.1

Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I'd like to second Erin's comment about the "Deploying Applications"
section.  The following command will not work, I promise.

<geronimo_home>/bin/java -jar deployer.jar help [command]

I also agree that Java 5 compatibility should be emphasized -- perhaps
"Geronimo is certified on Sun's JDK 1.4.2, but aside from the CORBA
features, it should run well on any 1.4.2 or 1.5 JVM."

I also think it's worth mentioning the "login" command in the
Deploying applications section.

In the significant changes section:
 - We should add plugins.  "Geronimo applications, server features,
and integrated products can be distributed as Geronimo plugins.
Plugins are easy to install, automatically download any dependencies,
and do not require server restarts."  Perhaps a separate point for
server cloning.  "Using the plugin infrastructure, applications or
modules can be copied from one Geronimo installation to another (from
developer to developer, test to production, etc.)."

 - For the console point, let's add "JMS resource configuration"

 - The hot deploy exclusion for the repository is not correct.  Hot
deployed files are copied into the repository like anything else.

 - For the Little G point, the grammar is wrong.  "Little-G, a
minimal, small footprint, Tomcat and Jetty configurations are
available."

 - We should add a point about in-place deployment.  "Geronimo
supports in-place deployment, which means an archive or directory can
be deployed without being copied into the Geronimo directory tree."

In the overall project status, I think we need to list initial Java EE
5 support as a major goal of the next release.

In the Jira section, I think all the entries should be word-wrapped at
77 characters or so.

Thanks,
    Aaron

On 6/8/06, Hernan Cunico <hc...@gmail.com> wrote:
> Dave Colasurdo wrote:
> > Hernan Cunico wrote:
> >
> >> Dave Colasurdo wrote:
> >>
> >>> Hernan Cunico wrote:
> >>>
> >>>> Hi All,
> >>>> I updated the release notes and it is ready for your review and
> >>>> comments, here is the link
> >>>>
> >>>> http://cwiki.apache.org/GMOxDOC11/release-notes-11txt.html
> >>>>
> >>>> Cheers!
> >>>> Hernan
> >>>>
> >>>
> >>> Thanks Hernan!  A few comments:
> >>>
> >>> 1) In section "Installing and Starting Geronimo"
> >>>
> >>> Suspect the geronimo.sh reference should be ./geronimo.sh
> >>
> >>
> >> I did not include the ./ because I specified the full path. Having the
> >> full path do you still need to specify the ./ ?
> >>
> >>>
> > Nope.  It works fine with the full path.
> >
> >>> 2) In section "Significant Changes"
> >>>
> >>> -Shared Library Support
> >>> -Statement Cache for JDBC drivers
> >>> -Dynamic Plugin support
> >>> -In-place deployment of exploded applications
> >>> -Dependent Package Upgrades (Tomcat, Jetty, etc.)
> >>
> >>
> >> DONE.
> >>
> >>>
> > Thanks
> >
> >>> 3)Also, probably want a new section on "Migrating applications from
> >>> previous releases" that references the existence of the Upgrade tool
> >>> that David J has created (and Lin is documenting) and any other major
> >>> differences that existing users will need to know.  It should link to
> >>> any other migration documentation that we have.
> >>
> >>
> >> Is that doc already available, I couldn't find the pointer on the dev
> >> list.
> >>
> >>>
> >
> > http://www.mail-archive.com/user@geronimo.apache.org/msg03519.html
>
> AHA! I was looking at the wrong thread :)
> Thanks Dave
>
> Cheers!
> Hernan
> >
> >
> >>> Thanks
> >>> -Dave-
> >>>
> >> Thanks for the comments.
> >>
> >> Cheers!
> >> Hernan
> >>
> >>
> >
>

Re: RELEASE-NOTES-1.1

Posted by Hernan Cunico <hc...@gmail.com>.
Dave Colasurdo wrote:
> Hernan Cunico wrote:
> 
>> Dave Colasurdo wrote:
>>
>>> Hernan Cunico wrote:
>>>
>>>> Hi All,
>>>> I updated the release notes and it is ready for your review and 
>>>> comments, here is the link
>>>>
>>>> http://cwiki.apache.org/GMOxDOC11/release-notes-11txt.html
>>>>
>>>> Cheers!
>>>> Hernan
>>>>
>>>
>>> Thanks Hernan!  A few comments:
>>>
>>> 1) In section "Installing and Starting Geronimo"
>>>
>>> Suspect the geronimo.sh reference should be ./geronimo.sh
>>
>>
>> I did not include the ./ because I specified the full path. Having the 
>> full path do you still need to specify the ./ ?
>>
>>>
> Nope.  It works fine with the full path.
> 
>>> 2) In section "Significant Changes"
>>>
>>> -Shared Library Support
>>> -Statement Cache for JDBC drivers
>>> -Dynamic Plugin support
>>> -In-place deployment of exploded applications
>>> -Dependent Package Upgrades (Tomcat, Jetty, etc.)
>>
>>
>> DONE.
>>
>>>
> Thanks
> 
>>> 3)Also, probably want a new section on "Migrating applications from 
>>> previous releases" that references the existence of the Upgrade tool 
>>> that David J has created (and Lin is documenting) and any other major 
>>> differences that existing users will need to know.  It should link to 
>>> any other migration documentation that we have.
>>
>>
>> Is that doc already available, I couldn't find the pointer on the dev 
>> list.
>>
>>>
> 
> http://www.mail-archive.com/user@geronimo.apache.org/msg03519.html

AHA! I was looking at the wrong thread :)
Thanks Dave

Cheers!
Hernan
> 
> 
>>> Thanks
>>> -Dave-
>>>
>> Thanks for the comments.
>>
>> Cheers!
>> Hernan
>>
>>
> 

Re: RELEASE-NOTES-1.1

Posted by Dave Colasurdo <da...@earthlink.net>.
Hernan Cunico wrote:
> Dave Colasurdo wrote:
>> Hernan Cunico wrote:
>>
>>> Hi All,
>>> I updated the release notes and it is ready for your review and 
>>> comments, here is the link
>>>
>>> http://cwiki.apache.org/GMOxDOC11/release-notes-11txt.html
>>>
>>> Cheers!
>>> Hernan
>>>
>>
>> Thanks Hernan!  A few comments:
>>
>> 1) In section "Installing and Starting Geronimo"
>>
>> Suspect the geronimo.sh reference should be ./geronimo.sh
> 
> I did not include the ./ because I specified the full path. Having the 
> full path do you still need to specify the ./ ?
>>
Nope.  It works fine with the full path.

>> 2) In section "Significant Changes"
>>
>> -Shared Library Support
>> -Statement Cache for JDBC drivers
>> -Dynamic Plugin support
>> -In-place deployment of exploded applications
>> -Dependent Package Upgrades (Tomcat, Jetty, etc.)
> 
> DONE.
>>
Thanks

>> 3)Also, probably want a new section on "Migrating applications from 
>> previous releases" that references the existence of the Upgrade tool 
>> that David J has created (and Lin is documenting) and any other major 
>> differences that existing users will need to know.  It should link to 
>> any other migration documentation that we have.
> 
> Is that doc already available, I couldn't find the pointer on the dev list.
>>

http://www.mail-archive.com/user@geronimo.apache.org/msg03519.html


>> Thanks
>> -Dave-
>>
> Thanks for the comments.
> 
> Cheers!
> Hernan
> 
> 

Re: RELEASE-NOTES-1.1

Posted by Hernan Cunico <hc...@gmail.com>.
Dave Colasurdo wrote:
> Hernan Cunico wrote:
> 
>> Hi All,
>> I updated the release notes and it is ready for your review and 
>> comments, here is the link
>>
>> http://cwiki.apache.org/GMOxDOC11/release-notes-11txt.html
>>
>> Cheers!
>> Hernan
>>
> 
> Thanks Hernan!  A few comments:
> 
> 1) In section "Installing and Starting Geronimo"
> 
> Suspect the geronimo.sh reference should be ./geronimo.sh

I did not include the ./ because I specified the full path. Having the full path do you still need 
to specify the ./ ?
> 
> 2) In section "Significant Changes"
> 
> -Shared Library Support
> -Statement Cache for JDBC drivers
> -Dynamic Plugin support
> -In-place deployment of exploded applications
> -Dependent Package Upgrades (Tomcat, Jetty, etc.)

DONE.
> 
> 3)Also, probably want a new section on "Migrating applications from 
> previous releases" that references the existence of the Upgrade tool 
> that David J has created (and Lin is documenting) and any other major 
> differences that existing users will need to know.  It should link to 
> any other migration documentation that we have.

Is that doc already available, I couldn't find the pointer on the dev list.
> 
> Thanks
> -Dave-
> 
Thanks for the comments.

Cheers!
Hernan

Re: RELEASE-NOTES-1.1

Posted by Dave Colasurdo <da...@earthlink.net>.
Hernan Cunico wrote:
> Hi All,
> I updated the release notes and it is ready for your review and 
> comments, here is the link
> 
> http://cwiki.apache.org/GMOxDOC11/release-notes-11txt.html
> 
> Cheers!
> Hernan
> 

Thanks Hernan!  A few comments:

1) In section "Installing and Starting Geronimo"

Suspect the geronimo.sh reference should be ./geronimo.sh

2) In section "Significant Changes"

-Shared Library Support
-Statement Cache for JDBC drivers
-Dynamic Plugin support
-In-place deployment of exploded applications
-Dependent Package Upgrades (Tomcat, Jetty, etc.)

3)Also, probably want a new section on "Migrating applications from 
previous releases" that references the existence of the Upgrade tool 
that David J has created (and Lin is documenting) and any other major 
differences that existing users will need to know.  It should link to 
any other migration documentation that we have.

Thanks
-Dave-