if you want your pages accessible via a url you need to mount them. im sure wicket in action has a chapter on that.
-igor On Thu, Sep 1, 2011 at 3:55 PM, jlazeraski <[email protected]> wrote: > Hi all, > > I am new to Wicket. I have Wicket in Action, read that and a bit on the web, > but my first go of Wicket 1.4 is not doing so well. I have the wicket jar > files, logging files, etc in the lib, and I see the log of my GlassFish v3 > server showing Wicket in Development mode. I set up the web.xml to use the > path of /html/* to point to the Wicket filter. In my code I have a > HellowWorld at com.company.wicket.HelloWorld. I also had the > HellowWorld.html file there. When I deploy that and point my browser to > localhost/war_name/html it shows the HellowWorld just fine. > > I am not a fan of having html in my src paths, so I figured out how to move > the html files to another pat using: > > IResourceSettings resourceSettings = getResourceSettings(); > resourceSettings.addResourceFolder(""); > > in my WebApplication class init method. That worked upon redeployment with > the HellowWorld.html moved to a new path under my root web path, which > mimicked the package name. > > The problem is, no other page works. If I put a 2nd WebPage extending class > called TestPage with a TestPage.html in my same location as the other html, > using the localhost/war_name/html/TestPage doesn't work. I've also tried > localhost/war_name/html/com.company.wicket.TestPage and that didn't work. > > I am not seeing any log errors either, so I am unsure at this time how to > make the other pages show up. I can't seem to find anything in the Wicket in > Action book either that would solve this. > > Appreciate a little help figuring out this issue. Thanks. > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Having-problems-with-wicket-pages-not-showing-up-tp3784941p3784941.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com. >
