Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm
Message-ID: <39C92831.396B8CDF@eng.sun.com>
Date: Wed, 20 Sep 2000 14:12:17 -0700
From: "Craig R. McClanahan" <Craig.McClanahan@eng.sun.com>
MIME-Version: 1.0
To: struts-user@jakarta.apache.org
Subject: Re: Why Deprecated method getInputForm()??
References: <034D8B328BD3D311BDC0009027E33C170145DC8D@il06exm22.corp.mot.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Shamdasani Nimmi-ANS004 wrote:

> Hi,
>
> I downloaded the latest version of Struts build of 9/20. When I recompile an
> existing java file which was working fine with older builds I get the
> warning:
>

Ah, I see that I forgot to announce some information on STRUTS-USER.

In preparation for a 1.0 release (targeted for ApacheCon Europe in October), I
have upgraded the Struts controller servlet to accept a new configuration file
format with improved capabilities, and (more importantly) can be extended in the
future without breaking backwards compatibility.  To see the new format, check
out the file WEB-INF/struts-config.xml in the example application.

Besides being a much more useful general format, the new configuration files are
now validated against a corresponding DTD file (file
"src/conf/struts-config_1_0.dtd" in the nightly distribution).  This will help
ensure correct configuration files, and will facilitate preparing the config
files with development tools that are XML aware.

The old configuration file format is still the default and is still supported,
but I hope to phase out support for it by the 1.0 release.  In the mean time,
you need to set initialization parameter "validate" to "true" on the controller
servlet in your web.xml.  The docs will be updated to reflect all this in the
near term.

As part of the general cleanup, I also took the opportunity to simplify the
attribute names used on the <action> element.  In addition, the definition of
form beans has been moved so that multiple actions can share the same bean by
logical name instead of by class.  The corresponding changes have been made to
ActionMapping (which is now a class instead of an interface), and the old method
names have been deprecated.  Check the Javadocs in the documentation application
-- the description of each deprecated method will tell you what has replaced it.

Look for a more comprehensive explanation of the expected changes between now
and 1.0 soon.

Craig McClanahan

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat