[
https://issues.apache.org/jira/browse/MYFACES-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844753#action_12844753
]
Gerry Kessler commented on MYFACES-2603:
----------------------------------------
Hi Jakob,
I am glad to hear that this will be helpful for you guys.
I have never used Subversion before and have spent the past half-hour trying to
configure a Subclipse team provider plugin to provide that diff for this issue.
So far I have not been successful. I will try for awhile longer, but if you
don't see that diff attachment by the end of today it probably means,
unfortunately, that you won't be getting it from me. :-(
Regards, GK
> Incorrect web-facesconfig_2_0.xsd
> ----------------------------------
>
> Key: MYFACES-2603
> URL: https://issues.apache.org/jira/browse/MYFACES-2603
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta-2
> Reporter: Gerry Kessler
> Attachments: web-facesconfig_2_0.xsd
>
>
> The web-facesconfig_2_0.xsd schema that is shipping with the latest binaries
> (myfaces-core-2.0.0-beta-2) is not compliant with the final JSF 2.0 spec.
> I have noted the following issues:
> - Missing namespace for faces-configType behavior element
> - Missing "eager" attribute for faces-config-managed-beanType
> - Missing "include-view-params" attribute for
> faces-config-redirectType
> - Missing faces-config-redirect-viewParamType type
> - Missing "if" element in faces-config-navigation-caseType
> - Missing faces-config-ifType type
> - Incorrect element name for behavior-extensionType in
> faces-config-behaviorType: was "extension"; should be "behavior-extension"
> I believe there are also several minor issues with schema listed in the final
> JSR-314 spec:
> Missing id attribute on:
> - faces-config-orderingType
> - faces-config-absoluteOrderingType
> - faces-config-behaviorType
> - faces-config-client-behavior-rendererType
> I am new to JIRA and this is my first submitted bug. I hope to attach my
> "repaired" schema to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
