Would it be possible for wicket to handle such a after-deploy-structure
without major head-aches:
+---graphics
| logo.gif
|
\---WEB-INF
| web.xml
|
+---classes
| +---com
| | \---foo
| | \---website
| | | FooWebApplication.class
| | | FooWebApplication$1.class
| | |
| | +---pages
| | | | Index.class
| | | |
| | | \---about
| | | Index.class
| | |
| | \---templates
| | PageTemplate.class
| |
| \---pages
| | Index.html
| | PageTemplate.html
| |
| \---about
| Index.html
|
\---lib
commons-logging-1.0.4.jar
log4j-1.2.12.jar
wicket-1.2-20060227-0200-src.zip
wicket-1.2-20060227-0200.jar
and having the markup-files and images in the same directory structure at
design-time?
--
Best regards,
Thomas Singer
Johan Compagner schrieb:
if you don't want to make components for youre image or other resource tags.
Then the only thing i can think of is that you put all youre pages in
the doc root
and then all youre other stuff in images above that so
Page.html
graphics/xxxx
style/xxxx
The big problem with this at runtime is that youre wicket html pages are
also accessible through an url
just ask for /foo/Page.html
So then they just have youre wicket page without the touching of wicket.
Also map youre wicket servlet not on /* but do it on /app/* or something
so that the doc root is not also served through wicket servlet. Thats a
waste.
johan
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
