I agree. I made the suggestion last month:
http://sourceforge.net/mailarchive/message.php?msg_id=13756383
I really like the architecture of Wicket although I have not used it much yet. The long url's is the one thing about Wicket that seemed would be a problem. It appears that the development team is considering some improvements with simplified url's.
Jeff
Mark Derricutt <[EMAIL PROTECTED]> wrote:
http://sourceforge.net/mailarchive/message.php?msg_id=13756383
I really like the architecture of Wicket although I have not used it much yet. The long url's is the one thing about Wicket that seemed would be a problem. It appears that the development team is considering some improvements with simplified url's.
Jeff
Mark Derricutt <[EMAIL PROTECTED]> wrote:
Hey all, so I'm starting to play with Wicket and loving it, but I currently have a small pethate with the URL scheme used in the application.
I realize the look of the URL "shouldn't" really matter, but I keep finding myself disliking it.
Currently my app shows a URL like:
http://localhost:8081/quickstart/app?bookmarkablePage=com.theoryinpractice.testapp.pages.CommentsPage
Is there a way to get the app to resolve the above using something like:
http://localhost:8081/quickstart/app/page/Podcomments
or even
http://localhost:8081/quickstart/app?page=Podcomments
I guess it could be possible to say 'register' the package
com.theoryinpractice.testapp.pages as a place where pages could be found and "resolve" the class to use instead of using the FQN all the time, this would only work in the case of unambiguous classes thou.
Or maybe theres something already in wicket for more REST like URL schemes? I notice in the basic frame work there's only a BookmarkablePage extension of Page, is there something in wicket-stuff maybe?
Jeff Miller
[EMAIL PROTECTED]
Yahoo! Shopping
Find Great Deals on Gifts at Yahoo! Shopping
