Actually allow me to clarify:
BY DEFAULT you do not need markers for non-exploded deployments.
You do need them for exploded. You can enable auto-deploy for
directories, and ignore using any marker, but you have the same casino
odds that you had in previous AS releases.
On 4/12/11 10:04 AM, Jason T. Greene wrote:
You dont need markers for non-exploded deployments (see auto-deploy
in
deployments/README.txt)
On 4/12/11 9:51 AM, Howard Gao wrote:
> Hi,
>
> In AS7 it uses a bunch of 'Marker files' to control and indicate a
> deployment. Comparing to previous AS 4 I found this is not so
> convenient. For example if I want to deploy an EJB jar I need to drop it
> to the /deployments dir and create a .dodeploy marker file. And if my
> EJB failed to deploy the marker file changed to .fail mark file. In a
> debug process this deployment can be repeated many times, each time a
> .dodeploy has to be manually added. And that's for a single EJB. If I
> have 5 EJB jars deployed I need file marker files manually created.
>
> In AS 4 I just drop it and done. I wonder what's the good reason for
> those marker files? From a user's point of view, for what other purposes
> could it be to drop something to the deployments directory than for
> deploying it right away?
>
> Thanks
> Howard
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss, a division of Red Hat