On 17-12-2008 at 22:17, Nathan Maves wrote:
is there a such thing?
is freddy book there is an example of using a SimpleMessage to display
to the user...
public Resolution delete() {
Contact deleted = contactDao.read(contactId);
contactDao.delete(contactId);
Thanks for the reply.
This may work if all attributes in ActionBeanContext are serialisable, which I
don't think so. I'm quite understand why the ActionBeanContext is not a
serialisable class, because it contains request, response, servlet context, etc.
However, there should be a workaround to
On 18-12-2008 at 12:14, epsilon wrote:
This may work if all attributes in ActionBeanContext are serialisable, which I
don't think so. I'm quite understand why the ActionBeanContext is not a
serialisable class, because it contains request, response, servlet context,
etc.
True. The
Indeed, I use LocalizableMessage later in the book. On page 224 of the PDF
you'll find a diagram illustrating the interfaces and classes for messages and
errors.
- In your situation, LocalizableMessage is probably sufficient.
-
- Oscar
-
Does anybody have any insight on this?
From: Asleson, Ryan [mailto:asle...@biworldwide.com]
Sent: Wednesday, December 17, 2008 8:45 AM
To: Stripes Users List
Subject: [Stripes-users] RedirectResolution in Unit Tests
Hello,
I'm using Stripes 1.5. I'm
On Thu, Dec 18, 2008 at 9:28 AM, Asleson, Ryan asle...@biworldwide.com wrote:
Does anybody have any insight on this?
How are you launching your action beans in your unit tests?
Specifically, is it through the Stripes Mock facilities?
--
Turtle, turtle, on the ground,
Pink and shiny, turn
In my unit tests I'm creating my ActionBeans simply by using the new
operator:
MyActionBean actionBean = new MyActionBean();
Should they be created another way?
-Original Message-
From: Mike McNally [mailto:emmecin...@gmail.com]
Sent: Thursday, December 18, 2008 9:51 AM
To: Stripes
Ben, so far so good. I've only changed a couple of actions through the
app but it is working without errors at the moment.
On Wed, Dec 17, 2008 at 5:22 PM, Ben Gunter gunter...@gmail.com wrote:
The URL for the trunk is
https://stripes.svn.sourceforge.net/svnroot/stripes/trunk . If you're
Ok spent too much time on this already so I am looking for help :)
Action has two lists.
List availablePeople;
Interger[] selectedPeople;
The availablePeople is the complete list of people objects, say 50 of them.
The selectedPeople array is the subset of those people's ids who
should be
Wanted to correct the subject
On Thu, Dec 18, 2008 at 2:23 PM, Nathan Maves nathan.ma...@gmail.com wrote:
Ok spent too much time on this already so I am looking for help :)
Action has two lists.
List availablePeople;
Interger[] selectedPeople;
The availablePeople is the complete list of
I was looking into this last night. I read the unit testing information on
the Stripes web site, and it does say you should be able to just create your
ActionBeans and test them without using any mock objects. Between 1.4 and
1.5 some new features were added that introduced dependencies on the
Is there a reason why you need to keep the indexes?
I may miss something, but using checkbox and indexes does not seem to be a good
implementation since, upon submission, unchecked checkboxes are not submitted...
Christian
-Original Message-
From: Nathan Maves
Oscar Westra van Holthe - Kind kin...@... writes:
True. The non-serializable fields should ideally transient, to exclude them
from serialization. Maybe this should be a Jira issue.
Then again, you can also ensure your action beans don't rely on the context
being present. It contains mostly
My conversion to use stripes clean urls is coming along reasonably
smoothly now thanks to Ben, but I've stumbled across another problem.
If I submit a form and it fails a validation handler
(@ValidationMethod), when Stripes sends it back to the browser the
extra bits in the URL are removed.
For
I just got done digging a little deeper. The constructor
OnwardResolution(Class) was added on March 13, 2006, and has always depended
on an ActionResolver being available. The good news for me is that I didn't
do it :) The bad news for you is that this isn't likely to change anytime
soon so you
This actually doesn't have anything to do with validation, just with forms.
The parameters weren't there in the form's action attribute so when you
submit the form the parameters aren't there on the URL. A validatio
On Thu, Dec 18, 2008 at 7:56 PM, Chris Cheshire cheshira...@gmail.comwrote:
My
I'm trying to get the Wizard model to work, flowing through a number of
jsp pages.
I get the following error, which is nice and clear, but I don't know
what the hidden field is supposed to look like.
Submission of a wizard form in Stripes absolutely requires that the
hidden field Stripes writes
Pat,
The hidden field is automatically generated by Stripes. It sounds like
you're missing the startEvents parameter in @Wizard. That tells which
events are valid entry points into the wizard.
Aaron
Pat Farrell wrote:
I'm trying to get the Wizard model to work, flowing through a number of
Aaron Porter wrote:
The hidden field is automatically generated by Stripes. It sounds like
you're missing the startEvents parameter in @Wizard. That tells which
events are valid entry points into the wizard.
How is it generated in the .jsp?
I do have code in the .java such as:
I forgot to mention that your forms in a wizard need to use only stripes
form fields. The stripes form tag keeps track of which fields exist and
generates the hidden field. It does that to prevent people from
injecting fields that you didn't intend to receive.
Aaron
Pat Farrell wrote:
Aaron
Isn't the s:wizard-fields/ tag still necessary in 1.5?
-Craig.
On Dec 18, 2008, at 9:11 PM, Aaron Porter wrote:
I forgot to mention that your forms in a wizard need to use only
stripes form fields. The stripes form tag keeps track of which
fields exist and generates the hidden field. It
Aaron Porter wrote:
I forgot to mention that your forms in a wizard need to use only stripes
form fields. The stripes form tag keeps track of which fields exist and
generates the hidden field. It does that to prevent people from
injecting fields that you didn't intend to receive.
Can you
I don't think I've ever used that tag. I had to look it up. Pretty sure
it's not necessary but by no means am I the @Wizard expert. I've only
used it a few times.
Aaron
Cra Cru wrote:
Isn't the s:wizard-fields/ tag still necessary in 1.5?
-Craig.
On Dec 18, 2008, at 9:11 PM, Aaron Porter
On 18-12-2008 at 22:57, Ben Gunter wrote:
Hidden inputs aren't handled like parameters for clean URLs. Instead, the
s:form tag now accepts s:params.
Just out of curiosity: what's the rationale behind this?
Oscar
--
,-_
/() ) Oscar Westra van holthe - Kind
24 matches
Mail list logo
