I wonder, what kind of usability issue that could be? I see two cases: 1) At best, URL should show the path to the object, like app/task/itemid/actiontype or something. I think this is better than artificial breadcrumbs, which do basically the same. And, if a user tries to go one "directory" up, application still would have to make sense out of it, like app/task/itemid would show possible actions for the item, and app/task would show... I don' t know what. I guess, my task tree is faulted ;)
2) If the above scheme does not work, why bother at all about some "usability issues" with URLs? Don't you have links? Can your app autogenerate proper links to needed items? Michael. On 6/3/05, amol k <[EMAIL PROTECTED]> wrote: > > Why not just map /do/* to the action servlet insted of *.do > > http://myserver/Login.do to http://myserver/do/Login, etc is not an issue but > Making the users type http://myserver/do/user/blahblah instead of > http://myserver/user/blahblah is a usability issue. > (will have to ultimately do that if there's no other option but I want > to avoid /do before user/blahblah as far as possible) > > > > On 6/3/05, Rick Reumann <[EMAIL PROTECTED]> wrote: > > Why not just map > > > > /do/* to the action servlet insted of *.do > > > > Then all of these would go through Struts.. > > > > http://myserver/do/Login > > http://myserver/do/Logout > > http://myserver/do/user/blahblah > > > > This obviously wouldn't go through struts.. > > > > http://myserver/pages/blahblah.jsp > > > > amol k wrote the following on 6/3/2005 2:39 PM: > > > Here is what I am trying to achieve: > > > > > > http://myserver/Login.do --> (maps to) LoginAction > > > http://myserver/Logout.do --> (maps to) LogoutAction > > > http://myserver/user/blahblah --> UserPageAction (notice that there is > > > no .do in this case. blahblah can be replaced by anything at runtime) > > > > > > http://myserver/pages/blahblah.jsp --> not handled by ActionServlet > > > (obviously) > > > > > > I am trying various combinations in web.xml and struts-config.xml > > > (including configuring /user as a module) but havent yet found a > > > decent solution. > > > Any thoughts? > > > > > > Thanks in advance. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -- > > Rick > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]