myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Resolved] (MYFACESTEST-66) pre-configured containers
Date Wed, 05 Feb 2014 11:42:08 GMT

     [ https://issues.apache.org/jira/browse/MYFACESTEST-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gerhard Petracek resolved MYFACESTEST-66.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.6-SNAPSHOT

> 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
>             Fix For: 1.0.6-SNAPSHOT
>
>
> 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)

Mime
View raw message