Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: EE-3.0.0.BETA
-
Fix Version/s: None
-
Component/s: Facelet Components
-
Labels:None
-
Environment:n/a
Description
The composite components currently use a 'home grown' strategy for checking for required attributes and displaying an error message if a composite component is used on a page with one or more of its required attributes. This was first implemented for the JSF 1.2 environment as a TagHandler. This TagHandler is now causing errors when used with MyFaces 2.1.6, so we need to look at doing this another way.
First proposal is to use proper <composite:interface> along with <composite:attribute required="true"..> tags in the composite components, but this will have to be tested for every component, as well as for both the Mojarra and MyFaces environments.
First proposal is to use proper <composite:interface> along with <composite:attribute required="true"..> tags in the composite components, but this will have to be tested for every component, as well as for both the Mojarra and MyFaces environments.
Issue Links
- depends on
-
IPCK-368 Reimplement Composite Components with JSF 2 Composite interfaces
- Closed
Activity
Philip Breau
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [] | |
Fix Version/s | EE-3.0.0.GA [ 10261 ] |
Philip Breau
made changes -
Philip Breau
made changes -
Salesforce Case | [] | |
Fix Version/s | EE-3.0.0.GA [ 10261 ] |
Philip Breau
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Won't Fix [ 2 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |