Return-Path: <issues-return-28988-archive-asf-public=cust-asf.ponee.io@struts.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 0EE77200BF8
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri, 13 Jan 2017 16:09:35 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 0D835160B3F; Fri, 13 Jan 2017 15:09:35 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 7C120160B32
	for <archive-asf-public@cust-asf.ponee.io>; Fri, 13 Jan 2017 16:09:34 +0100 (CET)
Received: (qmail 13906 invoked by uid 500); 13 Jan 2017 15:09:28 -0000
Mailing-List: contact issues-help@struts.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@struts.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@struts.apache.org>
List-Post: <mailto:issues@struts.apache.org>
List-Id: <issues.struts.apache.org>
Reply-To: dev@struts.apache.org
Delivered-To: mailing list issues@struts.apache.org
Received: (qmail 13846 invoked by uid 99); 13 Jan 2017 15:09:28 -0000
Received: from Unknown (HELO jira-lw-us.apache.org) (207.244.88.139)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jan 2017 15:09:28 +0000
Received: from jira-lw-us.apache.org (localhost [127.0.0.1])
	by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6388325282
	for <issues@struts.apache.org>; Fri, 13 Jan 2017 15:09:26 +0000 (UTC)
Date: Fri, 13 Jan 2017 15:09:26 +0000 (UTC)
From: "Lukasz Lenart (JIRA)" <jira@apache.org>
To: issues@struts.apache.org
Message-ID: <JIRA.13029487.1482247938000.2844.1484320166405@Atlassian.JIRA>
In-Reply-To: <JIRA.13029487.1482247938000@Atlassian.JIRA>
References: <JIRA.13029487.1482247938000@Atlassian.JIRA> <JIRA.13029487.1482247938680@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (WW-4727) Struts 2.5.8 no longer supports the
 <include> directive in the struts.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Fri, 13 Jan 2017 15:09:35 -0000


     [ https://issues.apache.org/jira/browse/WW-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukasz Lenart resolved WW-4727.
-------------------------------
    Resolution: Cannot Reproduce
      Assignee: Lukasz Lenart

Asked on a user group and got confirmation that everything is ok. Feel free to re-open and post more details.

> Struts 2.5.8 no longer supports the <include> directive in the struts.xml
> -------------------------------------------------------------------------
>
>                 Key: WW-4727
>                 URL: https://issues.apache.org/jira/browse/WW-4727
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.5.8
>            Reporter: adam brin
>            Assignee: Lukasz Lenart
>            Priority: Minor
>             Fix For: 2.5.next
>
>
> in 2.5.5 and most previous versions of Struts 2 you could use the {{<include file="struts-local-settings.xml" />}} directive to separate out constants and other parameters into changsets that could be managed.  This appears to have stopped working based on the fact that we're now getting NumberFormatExceptions when trying to parse {{struts.multipart.maxSize}} when it's not defined in the struts.xml but instead in the included file.  Setting {{struts.multipart.maxSize}} directly corrects this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)