[
http://jira.jboss.com/jira/browse/JBSEAM-1484?page=comments#action_12389717 ]
Max Andersen commented on JBSEAM-1484:
--------------------------------------
btw. the reason why it doesn't work in jboss tools is because you suddenly are using
absolute paths and we don't know where the root are for plain java projects (that is
an limitation we will work on fixing in upcoming versions, but just so you know ;)
Besides hard coded absolute path is evil in my book too, so what is actually the best way
to avoid this ? Is it by having something like #{templatelayout.dir}/template.xhtml
instead and allow you the greatest flexibility ? (this is somethng we also would need to
add support for in the tools to resolve that variable - but all doable)
Seam-gen should generate pages using templates relative to web
application, not the pages themselves
----------------------------------------------------------------------------------------------------
Key: JBSEAM-1484
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1484
Project: JBoss Seam
Issue Type: Patch
Components: Tools
Affects Versions: 1.3.0.ALPHA
Reporter: Dejan Krsmanovic
Assigned To: Dan Allen
Priority: Blocker
Fix For: 2.0.1.GA
Attachments: seam-gen.txt
Seam-gen currently creates facelets xhtml pages having ui-composition element with
template attribute specified relative to page itself. This is OK if all pages are stored
in the root folder of web application. However, when you start refactoring and moving
pages to separate folders you need to update template attribute in all ui-composition
elements in moved pages.
So, I think seam-gen should generate pages with ui-composition element which references
template relative to web-app, and not the page. In other words instead of:
<ui:composition ... template="layout/template.xhtml">
it should be:
<ui:composition ... template="/layout/template.xhtml">
With this change, you can move xhtml pages to any folder and template would still be
referenced correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira