[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8275) Composite components should be recognized in jar-files and class folders inside META-INF/resources/
[
https://issues.jboss.org/browse/JBIDE-8275?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-8275:
----------------------------------------------
Initially, request was about content assist only
(http://community.jboss.org/message/583919#583919). Accordingly, I have implemented only
loading composite components into KB model that provides data for content assist and
open-ons. You can test that if namespace for a composite tag library is declared on a
page, you will have completion proposals for composite components; and when a tag is
inserted, the declaring resource can be opened from it.
However, I see that the issue name and description imply full support, including rendering
in Visual Page editor. Well, lets implement that.
Composite components should be recognized in jar-files and class
folders inside META-INF/resources/
---------------------------------------------------------------------------------------------------
Key: JBIDE-8275
URL: https://issues.jboss.org/browse/JBIDE-8275
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JSF
Affects Versions: 3.2.0.CR1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.2.1.M1, 3.3.0.M1
Attachments: JBIDE-8275-impl.patch, JBIDE-8275-test.patch
Within project, composite components are located in folder %Web-root%/resources. - That
is supported by JBoss Tools.
But besides, composite components may be located in used by the project external jars and
class folders in folder META-INF/resources. - That was implemented for jar files but not
for class folders.
See http://community.jboss.org/message/583919#583919
JavaServerTM Faces Specification
2.6.1.2 Packaging Resources into the Classpath
For the default implementation, resources packaged in the classpath must reside under the
JAR entry name:
META-INF/resources/<resourceIdentifier>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira