Without going into a lot of detail, suffice to say our application benefits
from action chaning, and we are using it in the documented way.
We've begun to go through and add the validation to some actions, but we
have run into a snag with validation and action chaining.
Whenever one action in th
We actually have no validation XML files (we're setting error fields
manually). We're not performing validation using that approach, but we
want to remain open to doing so in the future. The validation interceptor
is in the struts-default stack, which is what our packages extend from.
From what
I'm referencing defaultStack. Can I simply pass that parameter to the
default stack and the validator interceptor will pick it up?
We don't actually use xml-based validation. We set action errors on our
own. Do you think it'll still work even though that interceptor is
specifically for xml based
The culprit wasn't the validation interceptor, but the workflow
interceptor. Its only job is to stop the chain (and call input on
everything) when validation errors occur. I removed it entirely and
everything is working as we need it to. This worked for us because,
regardless of errors, we need
Hi group,
We're trying to upgrade from 2.1.2 to 2.1.6 and ran into an issue.
We use action chaining because it suits a particular requirement we had for
this application.
However, after upgrading, we're seeing that the value stack isn't holding
on to values set by actions further up in the chain.
Hadn't heard back from anyone about this. I'll go ahead and file a bug
report.
No one is using action chaining with 2.1.6?
Thanks,
-B
Becky.L.O'Sulliva
We've been using GWT and Musachy's Struts 2 GWT plugin, and other than a
few "gotchas" it works well. It hasn't been updated in a looong time
though (hint hint - got a couple of open bugs :) ).
GWT has met all of our expectations and, for Java developers, is far easier
to work with than Dojo.
-
Thanks, bug WW-2970 was submitted along with a test case.
-B
Musachy Barroso
To
I'm guilty of pawning this task off to someone else. I'll have him take a
look at showcase and our example and get back to the group.
Thanks for checking this out so quickly. Maybe it's us. :)
-B
Musachy
Musachy,
In the bug report, under Test 1 instructions it's shows it working against
2.1.2 In the second set of instructions (accidentally also called Test 1)
it details how to make it not work by swapping over to 2.1.6.
Did you by any chance run this test case standalone, using the second set
of
We use Eclipse, but there's no IDE setup necessary and no special IDE
plugins. The beauty of GWT is it's all Java, so you just drop in the GWT
JARs and start using the APIs. Naturally there's a bit of a learning
curve to understand the server-side components, how GWT handles
asynchronous calls i
Because Showcase is so packed with goodies something else may be causing
chaining to actually work. If you try that test case standalone (after
modifying the POM XML for 2.1.6) chaining doesn't work (the value stays the
initial value).
-B
I forgot to mention that we're setting the test value in struts.xml
initially (in the first action in the chain). That's the value that
doesn't get modified in this test case.
-B
Musachy Barroso
We've been posting our URLs that way (sans .action) for a while now and we
love it. Please don't make it go away. :)
-B
d...@holstein.com
A "tooltip" is the HTML title attribute in the anchor tag
this
is the anchor text
The struts tag has a title attribute.
-B
James Neff
<[EM
It's possible - we're doing it:
(Struts.xml)
...
...
We also noticed Struts accepts web.action or just web, so our URLs look
like this
http://ourdomain.com/web/path/to/an/xml/file <-- web action is invoked
-B
I've done *.do or /do/* in S1.
Is it possible in S2 to map a URI fragmen
Hi everyone,
I'm using to include a page fragment in Struts 2.1.2.
(also tried with and the result did not change)
Ensuring the values are passed as Strings using OGNL syntax:
I know nav1 makes it into header.jsp as a request parameter because this
snippet yields "nav1
Thanks for the catch Dave.
Isn't it funny that they provide two examples of parameter passing in [1]?
Don't expect to be able to access those using struts tags within the
included file, ha!
I (hacked | worked around | fixed) it by using JSTL to place those
params into the page context (and there
Yes you can access them via JSTL, like Dave mentioned (using ${param.xx} ),
but not via OGNL.
If you want to access those params via OGNL use JSTL to set them into the
page scope, then use #attr to get them.
I hate JSTL's choose/otherwise tags, and prefer struts if/else tags, so I
use this a lot in
Hi everyone,
Our struts.xml file is getting beastly, so I attempted to break it down
into multiple files.
I read this page:
http://struts.apache.org/2.x/docs/can-we-break-up-a-large-strutsxml-file-into-smaller-pieces.html
Specifically:
"You can use elements in your struts.xml interchangeably wit
I had the same problem, and someone pointed out to me that it does say in
the s:include reference page
(http://struts.apache.org/2.x/docs/include.html) that parameters passedvia
s:include are not available on the stack. Well...it doesn't phrase it that
way, but that's basically it.
Yes, it's sill
Unfortunately you can't use JSTL in Struts 2 tags anymore. I got around
this by using JSTL to set the parameter into page scope:
Once it's in page scope #attr will find it:
found it!
-B
"Musachy Barros
22 matches
Mail list logo
