Bad idea to mix deployment styles?

Does that mean that I cannot do the following interchangeably?

1. deploy WAR to TomEE via Netbeans
2. deploy WAR by dropping WAR in tomee /webapps folder

If the answer is yes, I am pretty sure that i have been able to do the
following with an earlier version of 1.5.1 SNAPSHOT, but I could be wrong.
I often undeploy, but not all the time.

Quite frankly, I've been quite impressed with TomEE's ability to load a WAR
whether I drop WAR in tomee /webapps 'or' if I deploy from NetBeans.

When NetBeans deploy to TomEE does not work, I 'help' TomEE, by undeploying
the application by manual delete from file folder (Windows Explorer), or
undeploy app via NetBeans.



On Mon, Dec 3, 2012 at 11:25 AM, Romain Manni-Bucau
<[email protected]>wrote:

> Hi,
>
> if you update the unpacked war it should work
>
> or maybe netbeans is hiding sthg
>
> in general it is a bad idea to mix deployment styles
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2012/12/3 Howard W. Smith, Jr. <[email protected]>:
> > Just wanted to share the following issue I see
> > with apache-tomee-1.5.1-20121201.041455-93-plus; I don't think I saw this
> > with earlier versions of snapshot.
> >
> > 1. TomEE 'is' shutdown (or not running)
> > 2. Drop a WAR in tomee /webapps folder
> > 3. Start TomEE via NetBeans
> > 4. Attempt to use/access the web app
> >
> > 5. None of the latest software changes in the WAR file (that was 'last'
> > dropped in tomee /webapps folder) can be seen in the web app
> >
> > 6. Undeploy web app via NetBeans
> > 7. Shutdown TomEE
> > 8. Drop WAR in tomee /webapps folder 'again'
> > 9. Start TomEE via NetBeans
> > 10. Use/access the web app
> > 11. Finally, I see my latest software changes
> >
> > I've duplicated this at least twice within the last 1 or 2 hours.
> >
> > I am reporting this, since I know TomEE 1.5 vote is vastly approaching
> and
> > this 'might' be a bug, unless this is a user error. :)
>

Reply via email to