Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
we'll try the 1.1.0 ;) i'll try to push some more info on thursday about the RC what is sure is a release should be done at the end of the month *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 Alex The Rocker > Thanks, all I need now is a TomEE 1.0.1 RC (because of the problem with > space around the load-on-startup value in this app's web.xml), I read it's > supposed to come this week. > Impatiently, > > Alex > > On Tue, Sep 11, 2012 at 10:52 PM, Romain Manni-Bucau > wrote: > > > sounds rather good ;) > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau* > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > 2012/9/11 Alex The Rocker > > > > > Thanks, since there's currently no JPA in the application, so I guess > 1) > > > not mandatory at this time. > > > About : 2) the JDK 7 used by this app (which actually installs it from > > its > > > media) has no endorsed/ directory, if that's what you mean. > > > > > > In that case, can I just copy tomcat7.exe / tomcat7w.exe from a Tomcat > 7 > > > distribution at same version as TomEE+ 1.0.0, and repackage TomEE+ > 1.0.0 > > in > > > this application and let its installer register TomEE+ as a Windows > > service > > > just like if it were Tomcat ? > > > > > > (sorry if those questions are trivial, I have one slot for this > > experience > > > - a nightly build in which i'm allowed to make the experiment, I'd > rather > > > be successful, or TomEE+ adoption there will be slower, people are > always > > > kind of scared by changes...) > > > > > > Alex > > > > > > > > > On Tue, Sep 11, 2012 at 10:24 PM, Romain Manni-Bucau > > > wrote: > > > > > > > two previous mentionned hacks are true under windows too > > > > > > > > the main differences are the following ones: > > > > 1) need of javaagent for not enhanced JPA entity with OpenJPA (not > > > > recommanded BTW) > > > > 2) endorsed dir should be empty for java 7 (done automatically in > > startup > > > > scripts switching of folder but doing it manually is fine too if you > > want > > > > to keep "endorsed" dir) > > > > > > > > *Romain Manni-Bucau* > > > > *Twitter: @rmannibucau* > > > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > > > > > > > > > > > 2012/9/11 Alex The Rocker > > > > > > > > > Hello, > > > > > > > > > > Your (kind) answers seem to focus on UNIX starter, but again what' > > the > > > > risk > > > > > of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for > > > > service > > > > > registration ? > > > > > > > > > > To clarify my need: I try to make people believe in TomEE+ can be > an > > > easy > > > > > replacement for Tomcat (and after, lobby for EE feature to be > used). > > > > > For this, I'm trying to replace Tomcat by TomEE in an app without > > even > > > > > modifying this installer's app (but I can create a media for this > app > > > > with > > > > > TomEE expanded in same dir as Tomcat used to be). > > > > > Devil is in details, I don't know if TomEE's registration as a > > Windows > > > > > service can work strictly like Tomcat's, any clue appreciated ! > > > > > > > > > > > > > > > > > > > > On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau > > > > > wrote: > > > > > > > > > > > not really we hack for endorsed dir for java 7 too (in > catalina.sh) > > > > > > > > > > > > *Romain Manni-Bucau* > > > > > > *Twitter: @rmannibucau* > > > > > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2012/9/11 David Blevins > > > > > > > > > > > > > > > > > > > > On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > I am testing the drop-in replacement of Tomcat by TomEE+ for > a > > > > server > > > > > > > > application running on 64-bit Windows > > > > > > > > For the moment, I want minimal changes in this application's > > > > > installer. > > > > > > > > > > > > > > > > This application's installer registers the application server > > as > > > a > > > > > > > service. > > > > > > > > > > > > > > > > I noticed that tomcat7.exe is missing from Windows (ZIP) > > > > distribution > > > > > > of > > > > > > > > TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat > stuff. > > > > > > > > > > > > > > > > I am wondering if I would run into a wall by just copying > > Tomcat > > > > > > 7.0.27's > > > > > > > > tomcat7.exe into bin/ directory and let the application > > installer > > > > > > > register > > > > > > > > the service as if TomEE+ were Tomcat. > > > > > > > > > > > > > > > > Any opinion? > > > > > > > > > > > > > > > > What's different between TomEE.amd64.exe & tomcat7.exe, > appart > > > form > > > > > the > > > > > > > > exe's name? > > > > > > > > > > > > > > > > > > > > > > Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the > > > > > > > ./catalina.sh, the only change we make is adding the -javaagent > > > flag > > > > > > which > > > > > > > is only require
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
Thanks, all I need now is a TomEE 1.0.1 RC (because of the problem with space around the load-on-startup value in this app's web.xml), I read it's supposed to come this week. Impatiently, Alex On Tue, Sep 11, 2012 at 10:52 PM, Romain Manni-Bucau wrote: > sounds rather good ;) > > *Romain Manni-Bucau* > *Twitter: @rmannibucau* > *Blog: http://rmannibucau.wordpress.com* > > > > > 2012/9/11 Alex The Rocker > > > Thanks, since there's currently no JPA in the application, so I guess 1) > > not mandatory at this time. > > About : 2) the JDK 7 used by this app (which actually installs it from > its > > media) has no endorsed/ directory, if that's what you mean. > > > > In that case, can I just copy tomcat7.exe / tomcat7w.exe from a Tomcat 7 > > distribution at same version as TomEE+ 1.0.0, and repackage TomEE+ 1.0.0 > in > > this application and let its installer register TomEE+ as a Windows > service > > just like if it were Tomcat ? > > > > (sorry if those questions are trivial, I have one slot for this > experience > > - a nightly build in which i'm allowed to make the experiment, I'd rather > > be successful, or TomEE+ adoption there will be slower, people are always > > kind of scared by changes...) > > > > Alex > > > > > > On Tue, Sep 11, 2012 at 10:24 PM, Romain Manni-Bucau > > wrote: > > > > > two previous mentionned hacks are true under windows too > > > > > > the main differences are the following ones: > > > 1) need of javaagent for not enhanced JPA entity with OpenJPA (not > > > recommanded BTW) > > > 2) endorsed dir should be empty for java 7 (done automatically in > startup > > > scripts switching of folder but doing it manually is fine too if you > want > > > to keep "endorsed" dir) > > > > > > *Romain Manni-Bucau* > > > *Twitter: @rmannibucau* > > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > > > > > > 2012/9/11 Alex The Rocker > > > > > > > Hello, > > > > > > > > Your (kind) answers seem to focus on UNIX starter, but again what' > the > > > risk > > > > of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for > > > service > > > > registration ? > > > > > > > > To clarify my need: I try to make people believe in TomEE+ can be an > > easy > > > > replacement for Tomcat (and after, lobby for EE feature to be used). > > > > For this, I'm trying to replace Tomcat by TomEE in an app without > even > > > > modifying this installer's app (but I can create a media for this app > > > with > > > > TomEE expanded in same dir as Tomcat used to be). > > > > Devil is in details, I don't know if TomEE's registration as a > Windows > > > > service can work strictly like Tomcat's, any clue appreciated ! > > > > > > > > > > > > > > > > On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau > > > > wrote: > > > > > > > > > not really we hack for endorsed dir for java 7 too (in catalina.sh) > > > > > > > > > > *Romain Manni-Bucau* > > > > > *Twitter: @rmannibucau* > > > > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > > > > > > > > > > > > > > > > 2012/9/11 David Blevins > > > > > > > > > > > > > > > > > On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > I am testing the drop-in replacement of Tomcat by TomEE+ for a > > > server > > > > > > > application running on 64-bit Windows > > > > > > > For the moment, I want minimal changes in this application's > > > > installer. > > > > > > > > > > > > > > This application's installer registers the application server > as > > a > > > > > > service. > > > > > > > > > > > > > > I noticed that tomcat7.exe is missing from Windows (ZIP) > > > distribution > > > > > of > > > > > > > TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. > > > > > > > > > > > > > > I am wondering if I would run into a wall by just copying > Tomcat > > > > > 7.0.27's > > > > > > > tomcat7.exe into bin/ directory and let the application > installer > > > > > > register > > > > > > > the service as if TomEE+ were Tomcat. > > > > > > > > > > > > > > Any opinion? > > > > > > > > > > > > > > What's different between TomEE.amd64.exe & tomcat7.exe, appart > > form > > > > the > > > > > > > exe's name? > > > > > > > > > > > > > > > > > > > Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the > > > > > > ./catalina.sh, the only change we make is adding the -javaagent > > flag > > > > > which > > > > > > is only required if using OpenJPA as your JPA provider and you > want > > > > > runtime > > > > > > JPA enhancement (as opposed to doing it at build time). > > > > > > > > > > > > I suspect that's the main difference, but probably Andy can say > for > > > > > > certain. > > > > > > > > > > > > > > > > > > -David > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
sounds rather good ;) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 Alex The Rocker > Thanks, since there's currently no JPA in the application, so I guess 1) > not mandatory at this time. > About : 2) the JDK 7 used by this app (which actually installs it from its > media) has no endorsed/ directory, if that's what you mean. > > In that case, can I just copy tomcat7.exe / tomcat7w.exe from a Tomcat 7 > distribution at same version as TomEE+ 1.0.0, and repackage TomEE+ 1.0.0 in > this application and let its installer register TomEE+ as a Windows service > just like if it were Tomcat ? > > (sorry if those questions are trivial, I have one slot for this experience > - a nightly build in which i'm allowed to make the experiment, I'd rather > be successful, or TomEE+ adoption there will be slower, people are always > kind of scared by changes...) > > Alex > > > On Tue, Sep 11, 2012 at 10:24 PM, Romain Manni-Bucau > wrote: > > > two previous mentionned hacks are true under windows too > > > > the main differences are the following ones: > > 1) need of javaagent for not enhanced JPA entity with OpenJPA (not > > recommanded BTW) > > 2) endorsed dir should be empty for java 7 (done automatically in startup > > scripts switching of folder but doing it manually is fine too if you want > > to keep "endorsed" dir) > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau* > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > 2012/9/11 Alex The Rocker > > > > > Hello, > > > > > > Your (kind) answers seem to focus on UNIX starter, but again what' the > > risk > > > of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for > > service > > > registration ? > > > > > > To clarify my need: I try to make people believe in TomEE+ can be an > easy > > > replacement for Tomcat (and after, lobby for EE feature to be used). > > > For this, I'm trying to replace Tomcat by TomEE in an app without even > > > modifying this installer's app (but I can create a media for this app > > with > > > TomEE expanded in same dir as Tomcat used to be). > > > Devil is in details, I don't know if TomEE's registration as a Windows > > > service can work strictly like Tomcat's, any clue appreciated ! > > > > > > > > > > > > On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau > > > wrote: > > > > > > > not really we hack for endorsed dir for java 7 too (in catalina.sh) > > > > > > > > *Romain Manni-Bucau* > > > > *Twitter: @rmannibucau* > > > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > > > > > > > > > > > 2012/9/11 David Blevins > > > > > > > > > > > > > > On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > I am testing the drop-in replacement of Tomcat by TomEE+ for a > > server > > > > > > application running on 64-bit Windows > > > > > > For the moment, I want minimal changes in this application's > > > installer. > > > > > > > > > > > > This application's installer registers the application server as > a > > > > > service. > > > > > > > > > > > > I noticed that tomcat7.exe is missing from Windows (ZIP) > > distribution > > > > of > > > > > > TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. > > > > > > > > > > > > I am wondering if I would run into a wall by just copying Tomcat > > > > 7.0.27's > > > > > > tomcat7.exe into bin/ directory and let the application installer > > > > > register > > > > > > the service as if TomEE+ were Tomcat. > > > > > > > > > > > > Any opinion? > > > > > > > > > > > > What's different between TomEE.amd64.exe & tomcat7.exe, appart > form > > > the > > > > > > exe's name? > > > > > > > > > > > > > > > > Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the > > > > > ./catalina.sh, the only change we make is adding the -javaagent > flag > > > > which > > > > > is only required if using OpenJPA as your JPA provider and you want > > > > runtime > > > > > JPA enhancement (as opposed to doing it at build time). > > > > > > > > > > I suspect that's the main difference, but probably Andy can say for > > > > > certain. > > > > > > > > > > > > > > > -David > > > > > > > > > > > > > > > > > > > >
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
Thanks, since there's currently no JPA in the application, so I guess 1) not mandatory at this time. About : 2) the JDK 7 used by this app (which actually installs it from its media) has no endorsed/ directory, if that's what you mean. In that case, can I just copy tomcat7.exe / tomcat7w.exe from a Tomcat 7 distribution at same version as TomEE+ 1.0.0, and repackage TomEE+ 1.0.0 in this application and let its installer register TomEE+ as a Windows service just like if it were Tomcat ? (sorry if those questions are trivial, I have one slot for this experience - a nightly build in which i'm allowed to make the experiment, I'd rather be successful, or TomEE+ adoption there will be slower, people are always kind of scared by changes...) Alex On Tue, Sep 11, 2012 at 10:24 PM, Romain Manni-Bucau wrote: > two previous mentionned hacks are true under windows too > > the main differences are the following ones: > 1) need of javaagent for not enhanced JPA entity with OpenJPA (not > recommanded BTW) > 2) endorsed dir should be empty for java 7 (done automatically in startup > scripts switching of folder but doing it manually is fine too if you want > to keep "endorsed" dir) > > *Romain Manni-Bucau* > *Twitter: @rmannibucau* > *Blog: http://rmannibucau.wordpress.com* > > > > > 2012/9/11 Alex The Rocker > > > Hello, > > > > Your (kind) answers seem to focus on UNIX starter, but again what' the > risk > > of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for > service > > registration ? > > > > To clarify my need: I try to make people believe in TomEE+ can be an easy > > replacement for Tomcat (and after, lobby for EE feature to be used). > > For this, I'm trying to replace Tomcat by TomEE in an app without even > > modifying this installer's app (but I can create a media for this app > with > > TomEE expanded in same dir as Tomcat used to be). > > Devil is in details, I don't know if TomEE's registration as a Windows > > service can work strictly like Tomcat's, any clue appreciated ! > > > > > > > > On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau > > wrote: > > > > > not really we hack for endorsed dir for java 7 too (in catalina.sh) > > > > > > *Romain Manni-Bucau* > > > *Twitter: @rmannibucau* > > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > > > > > > 2012/9/11 David Blevins > > > > > > > > > > > On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: > > > > > > > > > Hello, > > > > > > > > > > I am testing the drop-in replacement of Tomcat by TomEE+ for a > server > > > > > application running on 64-bit Windows > > > > > For the moment, I want minimal changes in this application's > > installer. > > > > > > > > > > This application's installer registers the application server as a > > > > service. > > > > > > > > > > I noticed that tomcat7.exe is missing from Windows (ZIP) > distribution > > > of > > > > > TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. > > > > > > > > > > I am wondering if I would run into a wall by just copying Tomcat > > > 7.0.27's > > > > > tomcat7.exe into bin/ directory and let the application installer > > > > register > > > > > the service as if TomEE+ were Tomcat. > > > > > > > > > > Any opinion? > > > > > > > > > > What's different between TomEE.amd64.exe & tomcat7.exe, appart form > > the > > > > > exe's name? > > > > > > > > > > > > > Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the > > > > ./catalina.sh, the only change we make is adding the -javaagent flag > > > which > > > > is only required if using OpenJPA as your JPA provider and you want > > > runtime > > > > JPA enhancement (as opposed to doing it at build time). > > > > > > > > I suspect that's the main difference, but probably Andy can say for > > > > certain. > > > > > > > > > > > > -David > > > > > > > > > > > > > >
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
two previous mentionned hacks are true under windows too the main differences are the following ones: 1) need of javaagent for not enhanced JPA entity with OpenJPA (not recommanded BTW) 2) endorsed dir should be empty for java 7 (done automatically in startup scripts switching of folder but doing it manually is fine too if you want to keep "endorsed" dir) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 Alex The Rocker > Hello, > > Your (kind) answers seem to focus on UNIX starter, but again what' the risk > of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for service > registration ? > > To clarify my need: I try to make people believe in TomEE+ can be an easy > replacement for Tomcat (and after, lobby for EE feature to be used). > For this, I'm trying to replace Tomcat by TomEE in an app without even > modifying this installer's app (but I can create a media for this app with > TomEE expanded in same dir as Tomcat used to be). > Devil is in details, I don't know if TomEE's registration as a Windows > service can work strictly like Tomcat's, any clue appreciated ! > > > > On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau > wrote: > > > not really we hack for endorsed dir for java 7 too (in catalina.sh) > > > > *Romain Manni-Bucau* > > *Twitter: @rmannibucau* > > *Blog: http://rmannibucau.wordpress.com* > > > > > > > > > > 2012/9/11 David Blevins > > > > > > > > On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: > > > > > > > Hello, > > > > > > > > I am testing the drop-in replacement of Tomcat by TomEE+ for a server > > > > application running on 64-bit Windows > > > > For the moment, I want minimal changes in this application's > installer. > > > > > > > > This application's installer registers the application server as a > > > service. > > > > > > > > I noticed that tomcat7.exe is missing from Windows (ZIP) distribution > > of > > > > TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. > > > > > > > > I am wondering if I would run into a wall by just copying Tomcat > > 7.0.27's > > > > tomcat7.exe into bin/ directory and let the application installer > > > register > > > > the service as if TomEE+ were Tomcat. > > > > > > > > Any opinion? > > > > > > > > What's different between TomEE.amd64.exe & tomcat7.exe, appart form > the > > > > exe's name? > > > > > > > > > > Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the > > > ./catalina.sh, the only change we make is adding the -javaagent flag > > which > > > is only required if using OpenJPA as your JPA provider and you want > > runtime > > > JPA enhancement (as opposed to doing it at build time). > > > > > > I suspect that's the main difference, but probably Andy can say for > > > certain. > > > > > > > > > -David > > > > > > > > >
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
Hello, Your (kind) answers seem to focus on UNIX starter, but again what' the risk of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for service registration ? To clarify my need: I try to make people believe in TomEE+ can be an easy replacement for Tomcat (and after, lobby for EE feature to be used). For this, I'm trying to replace Tomcat by TomEE in an app without even modifying this installer's app (but I can create a media for this app with TomEE expanded in same dir as Tomcat used to be). Devil is in details, I don't know if TomEE's registration as a Windows service can work strictly like Tomcat's, any clue appreciated ! On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau wrote: > not really we hack for endorsed dir for java 7 too (in catalina.sh) > > *Romain Manni-Bucau* > *Twitter: @rmannibucau* > *Blog: http://rmannibucau.wordpress.com* > > > > > 2012/9/11 David Blevins > > > > > On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: > > > > > Hello, > > > > > > I am testing the drop-in replacement of Tomcat by TomEE+ for a server > > > application running on 64-bit Windows > > > For the moment, I want minimal changes in this application's installer. > > > > > > This application's installer registers the application server as a > > service. > > > > > > I noticed that tomcat7.exe is missing from Windows (ZIP) distribution > of > > > TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. > > > > > > I am wondering if I would run into a wall by just copying Tomcat > 7.0.27's > > > tomcat7.exe into bin/ directory and let the application installer > > register > > > the service as if TomEE+ were Tomcat. > > > > > > Any opinion? > > > > > > What's different between TomEE.amd64.exe & tomcat7.exe, appart form the > > > exe's name? > > > > > > > Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the > > ./catalina.sh, the only change we make is adding the -javaagent flag > which > > is only required if using OpenJPA as your JPA provider and you want > runtime > > JPA enhancement (as opposed to doing it at build time). > > > > I suspect that's the main difference, but probably Andy can say for > > certain. > > > > > > -David > > > > >
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
not really we hack for endorsed dir for java 7 too (in catalina.sh) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 David Blevins > > On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: > > > Hello, > > > > I am testing the drop-in replacement of Tomcat by TomEE+ for a server > > application running on 64-bit Windows > > For the moment, I want minimal changes in this application's installer. > > > > This application's installer registers the application server as a > service. > > > > I noticed that tomcat7.exe is missing from Windows (ZIP) distribution of > > TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. > > > > I am wondering if I would run into a wall by just copying Tomcat 7.0.27's > > tomcat7.exe into bin/ directory and let the application installer > register > > the service as if TomEE+ were Tomcat. > > > > Any opinion? > > > > What's different between TomEE.amd64.exe & tomcat7.exe, appart form the > > exe's name? > > > > Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the > ./catalina.sh, the only change we make is adding the -javaagent flag which > is only required if using OpenJPA as your JPA provider and you want runtime > JPA enhancement (as opposed to doing it at build time). > > I suspect that's the main difference, but probably Andy can say for > certain. > > > -David > >
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: > Hello, > > I am testing the drop-in replacement of Tomcat by TomEE+ for a server > application running on 64-bit Windows > For the moment, I want minimal changes in this application's installer. > > This application's installer registers the application server as a service. > > I noticed that tomcat7.exe is missing from Windows (ZIP) distribution of > TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. > > I am wondering if I would run into a wall by just copying Tomcat 7.0.27's > tomcat7.exe into bin/ directory and let the application installer register > the service as if TomEE+ were Tomcat. > > Any opinion? > > What's different between TomEE.amd64.exe & tomcat7.exe, appart form the > exe's name? > Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the ./catalina.sh, the only change we make is adding the -javaagent flag which is only required if using OpenJPA as your JPA provider and you want runtime JPA enhancement (as opposed to doing it at build time). I suspect that's the main difference, but probably Andy can say for certain. -David
Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
Hello, I am testing the drop-in replacement of Tomcat by TomEE+ for a server application running on 64-bit Windows For the moment, I want minimal changes in this application's installer. This application's installer registers the application server as a service. I noticed that tomcat7.exe is missing from Windows (ZIP) distribution of TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. I am wondering if I would run into a wall by just copying Tomcat 7.0.27's tomcat7.exe into bin/ directory and let the application installer register the service as if TomEE+ were Tomcat. Any opinion? What's different between TomEE.amd64.exe & tomcat7.exe, appart form the exe's name? Alex
