Details
-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: 2.0-Beta1
-
Component/s: Tool Integrations
-
Labels:None
-
Environment:eclipse 2.6, IF 2.0 beta2
Description
ICE faces 2 decided to use prefix ice only but with 2 different namespaces depending on sparkle components existence.
ICEfaces tooling need to eject 2 types of facelets xhtml pages. One is welcome page, which is also a reference page. Another is page templates including header page, footer page, template page, and composition page.
welcome page is created during creating project and project has not physically existed yet. The detection of hasCompat, hasSparkle has to be based on libraryInstallDelegationProvider from jst.jsf facet. header/template page is created after project is created and user starts to create page through ui.editor wizard. The detection on hasSparkle/hasCompat needs to be done through checking project's classpath. But problem is ui.editor templates is defined through plugin.xml with no custom project related info available. Has done some investigation on providing templateVariableResolver but it still has no reliable way to get access to project resources.
Temporary solution is to provide documentation to template for how to use namespace uri.
ICEfaces tooling need to eject 2 types of facelets xhtml pages. One is welcome page, which is also a reference page. Another is page templates including header page, footer page, template page, and composition page.
welcome page is created during creating project and project has not physically existed yet. The detection of hasCompat, hasSparkle has to be based on libraryInstallDelegationProvider from jst.jsf facet. header/template page is created after project is created and user starts to create page through ui.editor wizard. The detection on hasSparkle/hasCompat needs to be done through checking project's classpath. But problem is ui.editor templates is defined through plugin.xml with no custom project related info available. Has done some investigation on providing templateVariableResolver but it still has no reliable way to get access to project resources.
Temporary solution is to provide documentation to template for how to use namespace uri.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
We decided to separate 2 namespace URI. This task is invalid