[jboss-as7-dev] Missing 404 for non-existent web app context?

[Brian Stansberry]

On 4/18/11 12:02 PM, David M. Lloyd wrote:
> On 04/18/2011 11:57 AM, Brian Stansberry wrote:
>> On 4/18/11 9:59 AM, Jason T. Greene wrote:
>>> On 4/18/11 9:56 AM, David M. Lloyd wrote:
>>>> On 04/18/2011 09:51 AM, Brian Stansberry wrote:
>>>>> If we're going to do it as a true deployment (i.e. one that shows up in
>>>>> the config file's<deployments>      section and not a hack like we did in
>>>>> Alpha1 for the jdbc rars) then we need to do JBAS-9020 and treat it as
>>>>> "unmanaged" content
>>>>>
>>>>> <deployment name="ROOT.war" runtime-name="ROOT.war">
>>>>>           <fs-archive path="ROOT.war"
>>>>> relative-to="jboss.server.system.content.dir"/>
>>>>> </deployment>
>>>>>
>>>>> Treating it as managed content ain't gonna fly.
>>>>>
>>>>> <!-- No way!
>>>>> <deployment name="ROOT.war" runtime-name="ROOT.war">
>>>>>          <content id="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
>>>>> </deployment>
>>>>> -->
>>>>
>>>> Yeah this is what I was getting at.  To Remy's point though we will
>>>> probably want a nice name like "jboss-welcome.war" or something.
>>>>
>>
>> Sounds good. BTW, to help clarify, that
>> "jboss.server.system.content.dir" above is a system path that points to
>> a special location in the dist for this kind of thing, probably a peer
>> to "standalone/configuration", "standalone/data", "standalone/log",
>> "standalone/deployments". For domain mode an analogue would be under
>> "domain".
>>
>> We had such a location in Alpha1. See strikeout-text discussion of it in
>> http://community.jboss.org/wiki/JBossAS7UserGuide
>
> TBH in this particular case, it could most likely exist outside of
> "standalone" or "domain" in some other location.  After all if we ship
> this file, we can reference it by file name even in domain mode.
>

True; that's simpler.

The key thing is it's not going to be "standalone/deployments" which is 
a whole other animal.

-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat