And of course the magic of sending my problem to the mailing list let me
figure out the solution on my own:
I should have been using ServletActionRedirectResult rather than
ServletRedirectResult.
jk
On Wed, Feb 4, 2009 at 10:03 AM, Jim Kiley wrote:
> I'm feeling dim this morning and I hope you
I'm feeling dim this morning and I hope you folks can help me out.
To simplify, I have two classes:
com.company.view.cust.my.order.FieldRepAction
com.company.view.cust.my.rep.ChooseCustomerAction
FieldRepAction has the following annotation:
@Result(value = "chooseCustomer!input.action",
splay the tiles definition here. But it is important to me to
>> have a "forward" to an action defintion rather than a "redirect". Once I
>> redirect, I'm going to lose request-scoped data. "redirect" to actions
>> works perfectly but "forward&q
. "redirect" to actions
> works perfectly but "forward" doesn't. In my struts configuration
> sameAction should be dynamically substituted with the action name or the
> action call where the form is included, either "/welcome.action",
> "/product.ac
truts.apache.org/2.x/docs/action-chaining.html
>
> Dave
>
> -
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>
>
--
Vie
Dirk Forchel wrote:
I could not resolve my problem yet. How can I use the "dispatch" result type
to forward to actions (or maybe tiles definitions) rather than to JSPs?
You can't, AFAIK. You use "redirectAction" to go to actions, and "tiles"
to go to Tiles. IIRC "tiles" aren't redirects, so yo
ry.action" or even "/searchResult.action".
Has somebody any idea how to accomplish this? I reckon this is a almost
common workflow.
--
View this message in context:
http://www.nabble.com/-S2--Result-Type-Dispatch-problem-with-relative-Action-calls-tp21368053p21368053.html
Sent from
I'd go with bug. Please file a JIRA ticket at http://issues.apache.org/struts
Thanks,
Don
On Tue, Oct 28, 2008 at 11:16 PM, Leonard Broman <[EMAIL PROTECTED]> wrote:
> I am using 2.0.11.2. When I am inheriting action, the codebehind
> plugin is not overriding the definition for the supertype.
>
I am using 2.0.11.2. When I am inheriting action, the codebehind
plugin is not overriding the definition for the supertype.
Example:
@Result(value="foo.jsp")
public class FooAction ...
@Result(value="bar.jsp")
public class BarAction extends FooAction
Then exeuting bar.action renders foo.jsp any
but made no difference, so I put it back to match the
> showcase example.
>
> Please cc me directly on the reply, as I only get the daily digest of the
> list.
>
> Thanks for any help.
> Greg
>
>
>
>
>
> ---------
> To unsubscribe, e-mail: [EMAIL PROT
Using Struts 2.0.11.1.
I get this exception:
2008-08-21 10:50:17,859 ERROR org.apache.struts2.dispatcher.StreamResult:188 -
Can not find a java.io.InputStream with the name [inputStream] in the
invocation stack. Check the tag specified for this
action.
2008-08-21 10:50:18,640 ERROR org.apache.
Worked fine using dispatcher.forward(request, response);
On Thu, Aug 14, 2008 at 8:23 AM, <[EMAIL PROTECTED]> wrote:
> I am trying to retrofit the Ajax JSP Tag Library server side *servlet *code
> to fit the S2 lifecycle. I have a particular situation where my custom
> result works if I:
>
>
I am trying to retrofit the Ajax JSP Tag Library server side *servlet *code
to fit the S2 lifecycle. I have a particular situation where my custom
result works if I:
PrintWriter pw = response.getWriter();
pw.write(request.getParameter(blah, blah, blah);
pw.close();
but
the execute() method of actionName.
> How can you go to another method? Something like:
> @Result(name="send",type=ActionChainResult.class,value="actionName",params=
> {"method,anotherMethod"}).
>
>
--
View this message in context:
http://www.nabble.com
rtunately, this will send you to the execute() method of actionName. How
can you go to another method? Something like:
@Result(name="send",type=ActionChainResult.class,value="actionName",params=
{"method,anotherMethod"}).
--
View this message in context:
http://www.
lto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 10:32 AM
To: Struts Users Mailing List
Subject: RE: [S2] Result Type Dispatcher problem
--- "Inamdar, Anil" <[EMAIL PROTECTED]> wrote:
> Yes I tried with "redirect-action" and it works. But
> I don't want a
--- "Inamdar, Anil" <[EMAIL PROTECTED]> wrote:
> Yes I tried with "redirect-action" and it works. But
> I don't want a redirect as I lose my messages and
> other data from the previous action
Oh, I didn't notice that you said that in your
original post.
The default result type is "redirect". I d
rs Mailing List
Subject: Re: [S2] Result Type Dispatcher problem
--- "Inamdar, Anil" <[EMAIL PROTECTED]> wrote:
> TaskInsert.action
>
--- "Inamdar, Anil" <[EMAIL PROTECTED]> wrote:
> TaskInsert.action
>
Hello,
I have a problem with the result type dispatcher when I try to dispatch
the success or error to another action. I get 404 error. This works fine
with result type chain.
Here is my configuration.
sampleapp.examples.task.insert
TaskList.action
Does anyone have a use case for the params field in the Result
annotation? Currently it's defined in the annotation as:
String[] params() default {};
which I'm not sure makes sense as a name and value was passed in the XML
configuration.
/Ian
---
--- Don Brown <[EMAIL PROTECTED]> wrote:
> True...hmm...well, at the least, we should warn
> people or configure the annotation to not be able to
> be set at the method level.
I had updated the @Result anno wiki docs based on the
OP's woes, but yeah, making it a class-level
annotation would help
True...hmm...well, at the least, we should warn people or configure
the annotation to not be able to be set at the method level.
Don
On 2/9/07, Dave Newton <[EMAIL PROTECTED]> wrote:
--- Don Brown <[EMAIL PROTECTED]> wrote:
> Hm...if it doesn't work on the method level, file a
> ticket as it sh
--- Don Brown <[EMAIL PROTECTED]> wrote:
> Hm...if it doesn't work on the method level, file a
> ticket as it should work that way. If nothing else
> we should document it better.
I first annotated my methods, which failed, and I was
confused, but... results are defined in the XML file
for the t
Hm...if it doesn't work on the method level, file a ticket as it
should work that way. If nothing else we should document it better.
Don
On 2/9/07, Dave Newton <[EMAIL PROTECTED]> wrote:
--- Dave Newton <[EMAIL PROTECTED]> wrote:
> --- Laurie Harper <[EMAIL PROTECTED]> wrote:
> > Doh! That was
--- Dave Newton <[EMAIL PROTECTED]> wrote:
> --- Laurie Harper <[EMAIL PROTECTED]> wrote:
> > Doh! That was the problem. I could have sworn the
> > examples I looked at had it at the method level.
> I added more on the topic [...]
And no, I didn't sneak in and change the examples ;)
d.
--- Laurie Harper <[EMAIL PROTECTED]> wrote:
> Doh! That was the problem. I could have sworn the
> examples I looked at had it at the method level.
I had done the exact same thing the first time I used
annotations (hence the @Result page :) I added more on
the topic as a result of your issues and
Nate Drake wrote:
The @Result annotation should be at the class level, not the method level.
Doh! That was the problem. I could have sworn the examples I looked at
had it at the method level. Mea culpa!
Thanks,
L.
-
To un
Dave Newton wrote:
--- Laurie Harper <[EMAIL PROTECTED]> wrote:
What do I need to do to make @Result annotations on
my action methods work?
What doesn't work/what are the symptoms? I had it
working under 2.0.4 (w/ the 2.0.4 jars, anyway) until
it seemed I wouldn't be able to use it because of
The @Result annotation should be at the class level, not the method level.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Do you have the web.xml init-param "actionPackages" listing the package
that the action is in?
/Ian
Dave Newton wrote:
--- Laurie Harper <[EMAIL PROTECTED]> wrote:
What do I need to do to make @Result annotations on
my action methods work?
What doesn't work/what are the symptoms?
--- Laurie Harper <[EMAIL PROTECTED]> wrote:
> What do I need to do to make @Result annotations on
> my action methods work?
What doesn't work/what are the symptoms? I had it
working under 2.0.4 (w/ the 2.0.4 jars, anyway) until
it seemed I wouldn't be able to use it because of an
apparent confli
What do I need to do to make @Result annotations on my action methods
work? I'm using the code-behind and zero-config plugins, and tried to
add the annotation like this:
@Result(value = "users", type = ServletActionRedirectResult.class)
public String save() {
userService.saveUse
33 matches
Mail list logo
