On 07/06/2011 20:08, Christopher Schultz wrote:
> Mark,
> 
> On 6/7/2011 2:36 PM, Mark Thomas wrote:
>> On 07/06/2011 19:30, Christopher Schultz wrote:
>>> Keiichi,
>>>
>>> On 6/7/2011 7:37 AM, Keiichi Fujino wrote:
>>>> Index: conf/web.xml
>>>> ===================================================================
>>>> --- conf/web.xml   (revision 1127122)
>>>> +++ conf/web.xml   (working copy)
>>>> @@ -4176,4 +4176,6 @@
>>>>          <welcome-file>index.jsp</welcome-file>
>>>>      </welcome-file-list>
>>>>
>>>> +  <!-- ====================  distributable ===================== -->
>>>> +    <distributable/>
>>>>  </web-app>
>>>
>>> -1
>>>
>>> This will cause web applications to fail when adding session attributes
>>> that are not Serializable.
>>
>> Not it won't. This is *not* changing the default value of distributable.
> 
> That <distributable> flag is in conf/web.xml, which I assumed set
> defaults for all web applications. Is <distributable> handled
> differently than, say, <servlet-mapping> or anything else we put into
> conf/web.xml?

Yes. The defaults are now treated as a fragment. When merging the main
web.xml with fragments, all the fragments and the main web.xml have to
have to be distributable for the result to be distributable.

The default distributable setting for main web.xml is false.
The default distributable setting for web-fragment.xml in JARs is false.

By default, distributable is therefore false.
Only if the main web.xml and all of the fragments are marked as
distributable will the application be distributable.

The defaults are marked as distributable (in code) so they do not
prevent an app from being distributable.

> I apologize for not having read the code at this point.

I forgive you. This time. :)

Mark

> 
> -chris
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to