Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312358

Summary:

[JSF2.0] Composite component defined in project is not being recognized

Product:

[WebTools] Java Server Faces

Reporter:

Raghunathan Srinivasan <raghunathan.srinivasan>

Component:

Core

Assignee:

Cameron Bateman <cameron.bateman>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

yurykats

Version:

3.2

Flags:

raghunathan.srinivasan: pmc_approved? (david_williams)
raghunathan.srinivasan: pmc_approved? (naci.dai)
deboer: pmc_approved+
raghunathan.srinivasan: pmc_approved? (neil.hauge)
raghunathan.srinivasan: pmc_approved? (kaloyan)
raghunathan.srinivasan: review+

Target Milestone:

3.2 RC2

Hardware:

OS:

Windows XP

Whiteboard:

PMC_approved

Attachments:

Description	Flags
Adds tracking of resources folder when it is added and deleted	none
Test coverage for changes	none

Description Raghunathan Srinivasan

2010-05-10 19:49:28 EDT

Composite component defined in the resources folder is not being recognized when used in a xhtml page.

Steps:
1) In a new workspace, create a DWP with JSF 2.0 facet
2) Create index.xhtml under the WebContent fodler
3) Create resources\ezcomp folder under the WebContent folder
4) Create testComponnet.xhtml under resources\ezcomp folder
5) Open index.xhtml in the WPE
6) In the source view, in the html tag, type 'xmlns:ez=' and gesture for content assist.
Expected: http://java.sun.com/jsf/composite/ezcomp
Result: The namespace is not listed.

Workaround: 
1) Open the Tag Registry View
2) Select the current project
3) In the tree view, expand the "Facelt Tag Registry' node. Note that the namespace for the ezcomp library is not displayed.
4) Hit the refresh icon next to the project. Select Yes in the resulting dialog
5) The namespace for excomp is displayed

Comment 1 Cameron Bateman

2010-05-14 16:25:25 EDT

Created attachment 168606 [details]
Adds tracking of resources folder when it is added and deleted

Comment 2 Cameron Bateman

2010-05-14 16:25:53 EDT

Created attachment 168607 [details]
Test coverage for changes

Comment 3 Raghunathan Srinivasan

2010-05-16 20:54:58 EDT

* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug"
(requested by an adopter) please document it as such. 
Locating composite components is a key feature of the JSF 2.0 support in
Helios. The use case in the description one likely path for the user to define a cusitm component. This bug will break that feature and hence is a stop-ship defect.
* Is there a work-around? If so, why do you believe the work-around is
insufficient? 
No reasonable workaround
* How has the fix been tested? Is there a test case attached to the bugzilla
record? Has a JUnit Test been added? 
New Junit test to cover this use case is included
* Give a brief technical overview. Who has reviewed this fix? 
See description.
* What is the risk associated with this fix?
low-medium

Comment 4 Cameron Bateman

2010-05-18 15:53:54 EDT

Patches applied to HEAD (3.2RC2).