[
https://jira.jboss.org/browse/JBSEAM-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Costa updated JBSEAM-4699:
---------------------------------
Attachment: new-lifecycle-method-seamtest.diff
Attaching a patch to make your life easier.
> Add one more "lifecycle" method to AbstractSeamTest.Request
> -----------------------------------------------------------
>
> Key: JBSEAM-4699
> URL: https://jira.jboss.org/browse/JBSEAM-4699
> Project: Seam
> Issue Type: Feature Request
> Affects Versions: 2.2.1.CR2
> Reporter: Flavio Costa
> Fix For: 2.2.1.CR3
>
> Attachments: new-lifecycle-method-seamtest.diff
>
>
> org.jboss.seam.mock.AbstractSeamTest.Request has tons of methods, many of
> them are protected and can be overrode but I'm missing a method that enables
> me to tap into the very beggining of "private boolean emulateJsfLifecycle()
> throws Exception" to be more specific after the "restoreViewPhase();" method
> call.
> I need this in order to be able to use Components.getInstance() in the early
> stages of the test.
> It should look like this:
> private boolean emulateJsfLifecycle() throws Exception
> {
> restoreViewPhase();
> insideFacesLifecycle();
> ....
> }
> and insideFacesLifecycle() should look like this:
> protected void insideFacesLifecycle() { }
> Is that possible?
> Since I'm not altering the behaviour of the test, just adding one more
> entry-point I guess it wouldn't be a problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
