Mike Watson wrote:
The trick (I believe) is that the url should be parsed from right to
left, not left to right. I don't think it's a hijack; for the
application I'm working on context is very important so knowing that a
given resource is being accessed in the context of another resource
has a big part to play in dictating which functions should be
available and how they behave. (The book/chapter model is just an
example I used to try and simplify the problem).
Jeromy, I'm still really struggling to get this going, I don't suppose
you've found time to knock up that demo app?
Thanks in advance,
Sorry guys, I haven't had a chance to get back to this yet.
Dusty wrote:
This doesn't seem right. How can you distinguish between something like
/book/1/customMethod and /book/1/chapter?
Dusty, you're right. I just had a quick look and I do have a custom
action mapper that checks whether the pattern above references an action
or method for that exact reason (it checks the list of available actions
and gives precedence to those). Works great for me.
I released another actionmapper that solved the problem using a
different approach. It will be deprecated, but it's still up for info:
http://code.google.com/p/struts2urlplugin/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
