[
https://issues.jboss.org/browse/JBIDE-16096?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-16096:
----------------------------------------
Unfortunately it's not so easy to fix as it seemed before.
What we need to do:
1. Change JSF 2.2 project templates to use
http://xmlns.jcp.org/jsf/*
2. Register JSF 2.2 tag libs in xml catalog to provide CA for them even when these libs
are not included into project's classpath (WildFly server adapter doesn't include
them).
3. Register JBT JSF lib extensions for
http://xmlns.jcp.org/jsf/* in plugin.xml to provide
content assist for facelet components (<ui:*>)
4. Make JBT JSF model recognize composite components with
http://xmlns.jcp.org/jsf/*
namespace.
5. Write JUnit tests for 1,2,3,4 :)
JSF Code completion does not support
http://xmlns.jcp.org/jsf/*
namespaces
--------------------------------------------------------------------------
Key: JBIDE-16096
URL:
https://issues.jboss.org/browse/JBIDE-16096
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsf, jsp/jsf/xml/html source editing
Affects Versions: 4.2.0.Alpha1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Priority: Critical
Labels: respin-a
Fix For: 4.2.x
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/*:
{code}
<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">
{code}
5. FAILURE: Content assist for <h: <f: <ui: <ez: is not working
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira