Interceptors don't go on the value stack. They're similar to filters -- the
intercept() method is executed before the action is run, and they can (say)
initialize your action, but they're not used as value objects.
You might be thinking of the Model Driven interceptor. The Object returned
by (you
Turns out OC4J had a bug. They fixed it; we now have 10.1.3.3, and it works
fine.
JBL wrote:
>
> We have a link to a Struts 2 action that includes a URL parameter
> (.../something_method.action?name=NAME), and the URL parameter is getting
> lost -- it doesn't show up i
Final answer: we implemented a custom ActionMapper that handles a URL string
that doesn't involve a ? to separate the query parameters. Stuck a reference
to it in struts.properties:
struts.mapper.class=mypackage.MyActionMapper
Building a new ActionMapper isn't terribly difficult. It helps to def
ameters have yet
appeared. Looking at the byte[] in the ServletInputStream, it's easy to find
the original URL with all parameters intact, but the offset (several
hundred) seems to indicate that something has already processed it.
JBL wrote:
>
> We have a link to a Struts 2 action that inclu
ply again if anything turns up.
Jon
mihel wrote:
>
> JBL wrote:
>> We have a link to a Struts 2 action that includes a URL parameter
>> (.../something_method.action?name=NAME), and the URL parameter is getting
>> lost -- it doesn't show up in the action, the reques
if anything turns up.
Jon
Ian Roughley wrote:
>
> Since it works for the form, but not the wildcard action mapping, it
> might be an issue with the action mapper. Try using a non-wildcard
> mapping to see if it makes a difference.
>
> /Ian
>
> JBL wrote:
>> W
We have a link to a Struts 2 action that includes a URL parameter
(.../something_method.action?name=NAME), and the URL parameter is getting
lost -- it doesn't show up in the action, the request map (when we implement
RequestAware), the parameter map (when we implement ParameterAware), or a
custom
7 matches
Mail list logo
