[
https://issues.jboss.org/browse/JBIDE-8100?page=com.atlassian.jira.plugin...
]
Alexander Smirnov commented on JBIDE-8100:
------------------------------------------
RF 4 CDK generates faces-config that's compatible with jsf schema:
</description>
<component-type>org.richfaces.List</component-type>
<component-class>org.richfaces.component.UIList</component-class>
<facet>
<facet-name>term</facet-name>
<facet-extension/>
</facet>
<property>
<description>The value binding expression used to wire up this
component to a component property of a JavaBean class</description>
<display-name></display-name>
<icon/>
<property-name>binding</property-name>
<property-class>javax.faces.component.UIComponent</property-class>
<property-extension>
<cdk:generate>false</cdk:generate>
<cdk:hidden>false</cdk:hidden>
<cdk:literal>false</cdk:literal>
<cdk:pass-through>false</cdk:pass-through>
<cdk:read-only>false</cdk:read-only>
<cdk:required>false</cdk:required>
</property-extension>
</property>
In the schema, all <*-extension> elements have type "Any element". Tool
that don't recognize particular extensions has too ignore them.
So, my question is: does generated faces-config.xml has incompatibility with standard JSF
schema ( i checked them with eclipse xml validator ), or JBDS fails on unknown content of
<*-extension> ? For later, it's JBDS bug.
Content Assist does not propose a name for f:facet
--------------------------------------------------
Key: JBIDE-8100
URL:
https://issues.jboss.org/browse/JBIDE-8100
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.2.0.Beta2
Environment: JBDS 3.2.0-Beta2
Reporter: Yahor Radtsevich
Assignee: Alexey Kazakov
Fix For: 3.2.x, 3.3.x
Attachments: screenshot-1.png, screenshot.gif
See screenshot-1.png.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira