[
https://issues.apache.org/jira/browse/MYFACESTEST-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890232#comment-13890232
]
Leonardo Uribe commented on MYFACESTEST-66:
-------------------------------------------
After some feedback I have made some changes to the proposed class including:
- Use MockWebContainer to fix the session creation problem. Now a listener is
used and there are methods to start session and invalidate it.
- Add some getter methods for objects like facesContext, externalContext,
servletContext and so on.
- Split initialization in 2 steps (setup container and setup request) and
provide a setUpAll / tearDownAll to do these two steps at once.
I also added some junit tests.
> pre-configured containers
> -------------------------
>
> Key: MYFACESTEST-66
> URL: https://issues.apache.org/jira/browse/MYFACESTEST-66
> Project: MyFaces Test
> Issue Type: New Feature
> Components: Mock Objects
> Affects Versions: 1.0.5
> Reporter: Gerhard Petracek
> Assignee: Leonardo Uribe
>
> currently other frameworks like deltaspike have to use mocked containers for
> every version of jsf (one example can be found at
> https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;a=blob;f=deltaspike/modules/test-control/impl/src/main/java/org/apache/deltaspike/testcontrol/impl/jsf/MockedJsf2TestContainer.java;h=e6e2b2bec6cf443c141035643cb5816e1118e6d6;hb=HEAD
> ). in a lot of cases it's just required to have a simple control over the
> mocked container (methods like #addConfigEntry, #boot, #shutdown,
> #activateView, #startScope, #stopScope). those methods are independent of the
> jsf-api. -> if every new version of myfaces-test provides a correctly mocked
> container with such independent methods, frameworks like deltaspike could
> delegate to it (instead of hosting a correctly mocked container for every
> version of the jsf-api).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
