Thank you for your reply. This tip let me remove the perform method from my base class, but this is actually equivalent to what I was doing. The method perorm() is simply implemented exactly the way I had done it. Why would a method be both depreciated and required?
Thank you for your time, Jason Long CEO and Chief Software Engineer Supernova Software BS Physics, MS Chemical Engineering http://www.supernovasoftware.com -----Original Message----- From: Corey Probst [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 7:34 PM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: TilesController perform() depreciated and required in v1.2???? > I would appreciate any help with the following problem. I just upgraded one > of my applications from v1.1 to v1.2.4. I have resolved all upgrade issues > except the following. The Controller interface has depreciated the > perform() in favor of the execute(), but I am forced to implement both in > order to compile the code. Since I am implementing perform() I get many > depreciation warnings from the compiler. Does anyone have a solution? I > have provided a code sample and error message below. You can extend the ControllerSupport concrete class and override the execute() method instead. That seems to work but I'd like to hear it from somebody who knows for sure. The javadocs *seems* to indicate that is the intent... http://struts.apache.org/api/org/apache/struts/tiles/ControllerSupport.html Corey --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
