[
https://issues.jboss.org/browse/JBIDE-16096?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-16096:
----------------------------------------
The problem is that the corresponding tag libraries are not available for projects with
WildFly runtime since WildFly classpath container includes a limited set of jars.
To handle situations when the project does not have all needed tag libs in its classpath
we bundle a few common libraries (<h:*>, <f:*>, etc) and register them via
XMLCatalog.
But we have a bug JBIDE-16859 with jst plugins packed in JARs so that is why the tests
case from description works well in dev environment (plugins are not packed there) and
fails in JBDS.
So this issue is not about supporting new namespaces actually but about supporting XML
Catalog with tag libs packed in JARs.
This is not critical for Beta1, so I'm moving the issue to Beta2.
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: Viacheslav Kabanovich
Priority: Critical
Fix For: 4.2.0.Beta1
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