You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Craig McClanahan (JIRA)" <ji...@apache.org> on 2006/07/17 05:17:21 UTC
[jira] Resolved: (SHALE-220) init() lifecycle method called twice
[ http://issues.apache.org/struts/browse/SHALE-220?page=all ]
Craig McClanahan resolved SHALE-220.
------------------------------------
Resolution: Fixed
Fixed in nightly build 20060717. There were two related bugs ... the init() and destroy() methods were indeed being called twice, and the postBack property was not being initialized prior to the call to the init() method. Both of these problems have been fixed, and a system integration test added to verify correct behavior in the future.
Thanks for the bug report!
> init() lifecycle method called twice
> ------------------------------------
>
> Key: SHALE-220
> URL: http://issues.apache.org/struts/browse/SHALE-220
> Project: Shale
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.2
> Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.3
>
>
> From a user mailing list posting by Viswanath <v_ramineni AT hotmail.com>, following up on earlier mailing list conversations:
> ==========
> Hi Craig,
> Now that I have subscribed to Shale user group, I am posting this issue again.
> Just to make sure that I am not using older version of Shale libraries, I have downloaded shale-framework-20060713.zip and tried, same problem. This is what I did, to reproduce the issue in usecases project. ( I am not able to post code from my project because of lot of dependencies on EJBs/Database)
> I downloaded the latest usecases zip (07/14/2006). Unzipped the war file into a directory, created a project in eclipse, added the java source files, built and deployed it into JBOSS and it ran fine. Added the following code at the end of org/apache/shale/usecases/locale/Select.java overriding the "do-nothing" init() from ActionViewController.
> public void init()
> {
> System.out.println("Select.java - Init - PostBack Value: " + Boolean.toString(isPostBack()));
> }
> redeployed and ran. The console output when I click on "Select Language" link
> 15:20:27,515 INFO [STDOUT] Select.java - Init - PostBack Value: false
> 15:20:27,515 INFO [STDOUT] Select.java - Init - PostBack Value: false
> and on sumbit (when I click on "Go" )
> 15:20:33,546 INFO [STDOUT] Select.java - Init - PostBack Value: false
> 15:20:33,562 INFO [STDOUT] Select.java - Init - PostBack Value: true
> My environment is :
> OS : Windows XP Home
> JBOSS 4.0.4 Patch1 with Tomcat 5.5
> JRE : 1.5.0_06
> Eclipse 3.1.1
> Thanks
> Vish
> ==========
> I was able to reproduce this with latest trunk bits, using the default testing configuration (MyFaces, Tomcat 5.5). It's clearly a bug in how init and destroy method callbacks are being triggered for view controllers, most likely related to the fact that the mechanism for this was recently changed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira