- 
    Bug 
- 
    Resolution: Done
- 
    Major 
- 
    4.2.0.Beta1
- 
    None
1. Create a JSF 2.2 KickStart project with WildFly 8 target server.
2. Open inputname.xhtml with JBoss XHTML editor.
3. FAILURE: inputname uses http://java.sun.com/jsf/* namespaces instead of http://xmlns.jcp.org/jsf/*
4. Replace all http://java.sun.com/jsf/* by http://xmlns.jcp.org/jsf/*:
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://xmlns.jcp.org/jsf/facelets" xmlns:h="http://xmlns.jcp.org/jsf/html" xmlns:f="http://xmlns.jcp.org/jsf/core" xmlns:ez="http://xmlns.jcp.org/jsf/composite/demo">
5. FAILURE: Content assist for <h: <f: <ui: <ez: is not working
- blocks
- 
                    JBIDE-16096 JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces -         
- Closed
 
-         
- 
                    JBIDE-16643 JSF composite component validation does not support http://xmlns.jcp.org name space -         
- Closed
 
-         
- is duplicated by
- 
                    JBIDE-16929 Code Assist for <h:link value ""> is missing items "/resources","/templates","/pages" -         
- Closed
 
-         
- 
                    JBIDE-16932 Code completion for <rich: tag is empty -         
- Closed
 
-         
- is related to
- 
                    JBIDE-17518 "Unknown composite component" shown for tags from http://java.sun.com/jsf/composite namespace -         
- Closed
 
-