[jira] [Resolved] (MYFACES-3970) 11.4.2.1 topic Each element can have one or more elements.

["Leonardo Uribe (JIRA)" <de...@myfaces.apache.org>]

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

Leonardo Uribe resolved MYFACES-3970.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.8
         Assignee: Leonardo Uribe

You can do this too:

<contracts>testContract team</contracts>

But the observation about the many to many relationship is correct. I have fixed it. Thanks for pointing this out.

> 11.4.2.1 topic Each <contract-mapping> element can have  one or more <contract> elements.
> -----------------------------------------------------------------------------------------
>
>                 Key: MYFACES-3970
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3970
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-344
>    Affects Versions: 2.2.7
>            Reporter: Anup
>            Assignee: Leonardo Uribe
>            Priority: Minor
>             Fix For: 2.2.8
>
>
> JSF specification says that <contract-mapping> can have one or more url-pattern with one or more contracts. So Many to many option is possible. 
> 11.4.2.1
>  The <resource-library-contracts> element is contained with in the <application> element and contains
> one or more <contract-mapping> elements. Each <contract-mapping> element must one or more <urlpattern>
> elements and one or more <contract> elements.
> In my testing on Myfaces 2.2.7 it always keeps the second entry in the list overwriting the first one. 
> e.g. for this url-pattern the contract assigned is "team" . It does not consider "testContract".
> 			<contract-mapping>
> 				<url-pattern>/user/*</url-pattern>				
> 		  		<contracts>testContract</contracts> 
> 		  		<contracts>team</contracts>
> 			</contract-mapping>
> Tested on reference implementation Mojarra , it assigns to testContract correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)