[jboss-as7-dev] Intended deployemnt behavior?

[Scott Marlow]

On 07/08/2011 10:21 AM, Jim Crossley wrote:
> I may be too old school as well, but I miss the old file-system
> deployment.  The new marker system is error-prone and confusing.  The
> README in the deployments dir, while helpful, shouldn't be necessary.
> Apparently, there were some edge conditions that made hot deployment
> hard -- I remember having to disable the scanner before copying lots of
> files and then reenable after -- so rather than spend the effort to
> address those issues, instead we expose the complexity to the user?
>
> Copying an archive to a directory to deploy it and removing it to
> undeploy it is simple and beautiful.  That mechanism distinguishes JBoss
> among the other point-and-drool app server alternatives.  Personally, I
> think it's worth making that work.
>
> Maintaining your deployment state on the filesystem is awesome, allowing
> clever sysadmins to do some amazing things with rsync, git, and other
> filesystem-based tools.  Expecting users to sacrifice those tools in
> order to use a shiny web interface or fancy CLI is a mistake, imho.  I
> think the marker stuff will piss them off, tbh.

This sounds like a simple add-on that could be independent of AS7 (e.g. 
create an external process that scans some file system location for 
legacy deployment type actions and turns them into the new actions.)

>
> I say let the deployment tools (eclipse, maven, etc) use the CLI/API and
> bring back the old deployments dir.
>
> And keep those kids off my lawn!  ;)
>
> $.02
> Jim
>
>
> Jaikiran Pai<jpai at redhat.com>  writes:
>
>> Although, we should encourage users to use CLI or web interface, IMO,
>> many users would still prefer file system based deployments since it
>> doesn't require the server to be started and is also pretty simple to
>> "deploy".
>>
>> -Jaikiran
>> On Friday 08 July 2011 07:14 PM, Heiko Braun wrote:
>>>
>>>
>>> As a side note:
>>>
>>> Users are not advised to use the file system deployment mechanism.
>>> This is intended to be used by deployment tools that properly deal with all the
>>> marker files (eclipse, maven). Users should either rely on the CLI or the web interface to deploy applications:
>>>
>>> https://docs.jboss.org/author/display/AS7/Admin+Guide
>>>
>>>
>>> Ike
>>>
>>>
>>>
>>> On Jul 8, 2011, at 3:38 PM, Bill Burke wrote:
>>>
>>>> Maybe I'm just not supposed to do it this way but:
>>>>
>>>> 1) I deployed a bad war, bot a deployment error
>>>> 2) I fixed the problem, re-copied the war to the deployments directory
>>>> 3) The war deployment was skipped on restart (I'm guessing because there
>>>> is a mywar.war.failed file in the deploy directory.
>>>>
>>>> Is this intended behavior?  Seems like it could cause a lot of problems.
>>>>    In the minimum, AS7 should check to see if the date of the .failed or
>>>> .deployed file is older than the actual deployment file.
>>>>
>>>> I'll log a JIRA if u agree.
>>>>
>>>> --
>>>> Bill Burke
>>>> JBoss, a division of Red Hat
>>>> http://bill.burkecentral.com
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev