Bugzilla – Full Text Bug Listing
| Summary: | [JSF2.0] MyFaces 2.0 not supported | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Java Server Faces | Reporter: | Cameron Bateman <cameron.bateman> | ||||||
| Component: | Core | Assignee: | Cameron Bateman <cameron.bateman> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | david_williams, raghunathan.srinivasan, thatnitind, xiaonan_jiang, yurykats | ||||||
| Version: | 3.2 | Flags: | david_williams:
pmc_approved+
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 RC3 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | PMC_approved JSF2.0 | ||||||||
| Attachments: |
|
||||||||
|
Description
Cameron Bateman
Tooling for standard tags should not depend on JSF implementations packaging taglib.xml. This is not required by JSF spec and is up to the implementation authors. Tooling for standard tags should be self-contained as all information about those tags is spec'ed and thus is available. Not supporting MyFaces is a big deal. I would mark this as "critical", not "normal". (In reply to comment #1) > Not supporting MyFaces is a big deal. I would mark this as "critical", not > "normal". That's not what that means. https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#bug_severity ok, major if you insist. Created attachment 169681 [details]
Ensures that standard taglibs are loaded if they are not found on the classpath.
Created attachment 169682 [details]
Test coverage
* 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. This is a stop-ship bug. JSF 2.0 features are not supported for the MyFaces 2.0 implementation which is a major blocker for adopters and users. * Is there a work-around? If so, why do you believe the work-around is insufficient? No workaround. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Junit test attached. * Give a brief technical overview. Who has reviewed this fix? See description and comment 4. The fix bundles the taglib.xml from the RI implementation and loads it if not found in the classpath. * What is the risk associated with this fix? medium Patches applied to HEAD (3.2M3) |