[
https://issues.jboss.org/browse/JBIDE-14938?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-14938:
----------------------------------------
{code}
testGetBundleProperties2(org.jboss.tools.jsf.model.pv.test.JSFPromptingProviderTest) Time
elapsed: 0.036 sec <<< FAILURE!
junit.framework.AssertionFailedError: Bundles properties proposal list has wrong size
expected:<2> but was:<0>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.TestCase.assertEquals(TestCase.java:401)
at
org.jboss.tools.jsf.model.pv.test.JSFPromptingProviderTest.testGetBundleProperties2(JSFPromptingProviderTest.java:88)
{code}
Content assist for JSF components does not consider
composite-library-name
--------------------------------------------------------------------------
Key: JBIDE-14938
URL:
https://issues.jboss.org/browse/JBIDE-14938
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JSF
Affects Versions: 4.0.0.Final
Reporter: Rich DiCroce
Assignee: Viacheslav Kabanovich
Fix For: 4.2.x
The <facelet-taglib> schema allows you to define a <composite-library-name>,
which allows you to combine pure facelet components and composite components into a single
namespace, defined by the <namespace> tag.
Currently, it appears JBoss Tools ignores <composite-library-name>, so the facelet
components defined in the taglib (using <tag>) appear when you trigger content
assist, but the composite components do not.
--
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