-
1. Re: sub folder not supported in url
liudan2005 Feb 23, 2006 3:51 PM (in response to liudan2005)has anyone tried yet? looks like a bug.
-
2. Re: sub folder not supported in url
theute Feb 24, 2006 3:26 AM (in response to liudan2005)Are you sure your subfolders are being copied into the war ?
-
3. Re: sub folder not supported in url
liudan2005 Feb 24, 2006 4:54 AM (in response to liudan2005)Yes, I'm pretty sure it's copied to war folder. when I type http://localhost:8080/myweb/myfolder/a.xhtml, i can actually download the xhtml source file from the site.
-
4. Re: sub folder not supported in url
ido_tamir Feb 26, 2006 8:28 AM (in response to liudan2005)having stuff in subfolders works.
I also started to move pages into subfolders and
did not adjust some of the paths e.g.
<ui:composition template="../template.xhtml">
Same error response.
hth
ido -
5. Re: sub folder not supported in url
liudan2005 Mar 1, 2006 12:58 PM (in response to liudan2005)Has anyone else tried yet? this is the error i've got:
HTTP Status 404 - /seam-booking/member/main.seam
type Status report
message /seam-booking/member/main.seam
description The requested resource (/seam-booking/member/main.seam) is not available.
I simply moved main.seam to member folder and have path chaged. still no luck. -
6. Re: sub folder not supported in url
gnulp Mar 1, 2006 2:55 PM (in response to liudan2005)I had the same troubles, but I am not sure if it is really a seam problem or more a faclets problem !
If you have a look at the faclets documentation there is a sentence telling you that templates are loaded relativly - meaning it will be loaded relativly from the directory where you are ==> so your template will be found but all pathes within the template seems to be broken because faclets doesn't take the templates directory as its origin but your directory !!! Unfortunatelly it seems currently not possible to use "absolute pathes" in the template which would solve the problem - at least my tries faild ...
A simple workaround is to use a global xhtml file including the template and your code within the directories - not nice but at least it works ! Once these problems are solved you can simply switch back to your structure without much changes ...
If anybody found a better solution or even implemented it successfully - please give us a hint ;-)