Thanks Brian, I can't break this version :-)
Excellent!
I still have the /an/arbitary/url/index issue which is very annoying
but acknowledge its present in non-smartURLs apps too. Unfortunately
setting the alwaysSelectFullNamespace flag doesn't entirely avoid it.
It generates a correct
Brian Pontarelli wrote:
Okay. That should be finished. It was somewhat tricky because the
XWork runtime configuration returns a valid ActionConfig for any URL
that ends in a / if you have a index action at the root. This is the
default handling that I'm not very fond of. For now, I turned
Brian Pontarelli wrote:
Okay, I reproduced this pretty easily. The environment differences
didn't matter. The /missing rendering /index is due to the default
handling of missing actions that is performed by Struts/XWork I
think. I'll have to figure out exactly which interceptor does this,
Okay, I reproduced this pretty easily. The environment differences
didn't matter. The /missing rendering /index is due to the default
handling of missing actions that is performed by Struts/XWork I
think. I'll have to figure out exactly which interceptor does this,
but I'm not a big fan of
Inspecting the HTTP requests:
update returns a 404 with an iframe referencing /missing
the get of /missing returns a 302 containing the index page
subsequent requests are successfully performed within the /missing
namespace
ie.
http://localhost:8080//missing/edit?id=0
Note the double / as
Inspecting the HTTP requests:
update returns a 404 with an iframe referencing /missing
the get of /missing returns a 302 containing the index page
subsequent requests are successfully performed within the /missing
namespace
ie.
http://localhost:8080//missing/edit?id=0
Note the double / as
Brian Pontarelli wrote:
Brian Pontarelli wrote:
Okay. That should be finished. It was somewhat tricky because the
XWork runtime configuration returns a valid ActionConfig for any URL
that ends in a / if you have a index action at the root. This is the
default handling that I'm not very fond
Sorry, forgot to commit those changes. They are in now.
-bp
Jeromy Evans wrote:
Brian Pontarelli wrote:
Brian Pontarelli wrote:
Okay. That should be finished. It was somewhat tricky because the
XWork runtime configuration returns a valid ActionConfig for any URL
that ends in a / if you
Hi Brian,
There seems to be a small glitch with url mapping in the crud-example
(rev151). It's okay for the standard use-cases but break-downs if I do
something untoward.
Interestingly, the behaviour differs between Firefox and IE6.
Here's the test-case. The URL is what's displayed on the