Menu
▾
▴
springframework-developer — Spring Framework developers list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Steven D. <ste...@gm...> - 2005-04-04 08:40:06
|
Hi guys, What are you views on the topics below? Thanks Steven ---------- Forwarded message ---------- From: Steven Devijver <ste...@gm...> Date: Mar 29, 2005 9:52 AM Subject: webflow & security To: spr...@li... Hi, It would be nice if webflow would support J2EE roles on a state level. This way one could set a read-only role on all states except a save or delete state which would have a management role. Next to that, ideally, it should be possible for the view technology to determine which buttons or anchors should or should not be rendered by checking the role of the current user with the role of the state linked to a given button or anchor. Steven -- "If you want to be a different fish, you gotta jump out of the school." -- Captain Beefheart -- "If you want to be a different fish, you gotta jump out of the school." -- Captain Beefheart |
|
From: Thierry T. <te...@ya...> - 2005-04-04 08:15:41
|
Great Brian!! > Cool. I've been javadoc-ing it, and cleaning up some > of the duplication. Will keep poking at it locally > until we figure out what to do with it. > > Spring main, Spring Modules, Lucene contrib, just > self hosted, however > it goes =) Figured I had it, and a bunch of folks I > know asked for it, > so might as well share. > > -Brian Take a look at my blog: http://templth.blogspot.com/ __________________________________________________________________ Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ |
|
From: Thierry T. <te...@ya...> - 2005-04-04 07:45:52
|
Dmitriy, I will clean it and send it to you... Thierry > Also, could this code become a part of the sandbox > for now? > > Dmitriy. Take a look at my blog: http://templth.blogspot.com/ __________________________________________________________________ Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ |
|
From: Thierry T. <te...@ya...> - 2005-04-04 07:44:45
|
Hi Dmitriy, For the management of connection, perhaps could it be good to delegate it to commons-pool (or other)? I will make some tests. The demarcation of transaction is not really a problem with JCA (some code in the allocateConnection, connectionClosed and connectionErrorOccurred methods)... On the other hand, we must manage the two version of JCA (1.0 and 1.5) because the SPI is very different... For the security, I must have a closer look at the problem. Thierry > How much effort would implementing J2C system > contracts require? > Juergen, what do you think? > > Dmitriy. Take a look at my blog: http://templth.blogspot.com/ __________________________________________________________________ Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ |
|
From: Keith D. <ke...@in...> - 2005-04-04 05:49:56
|
Steven, All:
The 'validatorMethod' feature discussed below is now implemented and
demonstrated in the 'sellItem' sample in CVS. Specifically:
In the flow definition:
<action-state id="bindAndValidatePriceAndItemCount">
<action bean="sellItemAction" method="bindAndValidate">
<property name="validatorMethod" value="validatePriceAndItemCount"/>
</action>
<transition on="success" to="enterCategory"/>
<transition on="error" to="enterPriceAndItemCount"/>
</action-state>
In SaleValidator, the Validator configured on the 'SellItemAction':
public void validatePriceAndItemCount(Sale sale, Errors errors) {
if (sale.getItemCount() <= 0) {
errors.rejectValue("itemCount", null, "Item count must be
greater than 0");
}
if (sale.getPrice() <= 0.0) {
errors.rejectValue("price", null, "Price must be greater
than 0.0");
}
}
In SellItemAction, which will only perform validation if the
'validatorMethod' property is indeed set:
protected boolean validationEnabled(RequestContext context) {
return containsProperty(VALIDATOR_METHOD_PROPERTY, context);
}
-----Original Message-----
From: Keith Donald [mailto:ke...@in...]
Sent: Sunday, April 03, 2005 1:20 AM
To: 'spr...@li...'
Subject: RE: [Springframework-developer] webflow: FormAction question
Steven,
1.) setupForm is called if and when you want it to be called - with Spring
webflow, you define the workflow explicitly and what actions (or target
methods) should be called on what events. That's the inherent power in web
flows---the action methods don't contain any workflow, they just execute
some logic-- the flow itself fully defines the workflow, dynamically.
Checkout the new 'sellitem' sample in samples/webflow in CVS to see how it
calls 'setupForm' at the beginning of the wizard flow.
2.) You could always do custom validation logic for each page in the action
that processes each submit, in a custom method that you define, like "public
bindAndValidateShippingDetails(RequestContext context)". However, I am
thinking it makes sense to have the FormAction aware of a action property
called 'validatorMethod' that will be invoked by ValidatorUtils, to allow
piecemeal validation of the domain object on a per page basis (instead of
always calling the 'validate' method, which validates the whole object).
Either that or perhaps we need a WizardFormAction that provides specific
support for this. Thoughts?
Keith
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Steven Devijver
Sent: Saturday, April 02, 2005 4:41 PM
To: spr...@li...
Subject: Re: [Springframework-developer] webflow: FormAction question
Keith,
Thanks for the feedback an my apologies for not posting on the user
list. There's two things that aren't clear to me:
1) is setupForm on FormAction called only once and if so where and why
only there?
2) how can I validate every page/form separately saying this or that
is missing? Every form submit uses the same validator, how can it
validate only the properties related to the form?
Thanks
Steven
On Apr 2, 2005 8:11 PM, Keith Donald <ke...@in...> wrote:
> Hey Steven,
>
> Be sure to use the 'users' list or forum for questions like this next
time,
> so more users will see it.
>
> You can use one FormAction to do this, yep. Erwin will be checking in a
> wizard sample shortly (potentially this evening), so I'll just sum up what
> the sample will illustrate:
>
> - The FormAction already has a 'bindAndValidate' method, that does what
you
> want on each intermediate page submit. So you can have that method called
> on each submit by using a bindAndValidate<X> action state, where <X>
> describes what it is you are binding and validating.
>
> For example:
>
> <action-state id="bindAndValidatePageFoo">
> <action id="myFormAction">
> <property name="executeMethodName" value="bindAndValidate"/>
> </action>
> <transition on="error" to="viewPageFoo"/>
> <transition on="success" to="viewPageBar"/>
> </action-state>
>
> <action-state id="bindAndValidatePageBar">
> <action id="myFormAction">
> <property name="executeMethodName" value="bindAndValidate"/>
> </action>
> <transition on="error" to="viewPageBar"/>
> <transition on="success" to="submit"/>
> </action-state>
>
> <action-state id="submit">
> <action id="myFormAction">
> <property name="executeMethodName" value="submit"/>
> </action>
> <transition on="error" to="error"/>
> <transition on="success" to="end"/>
> </action-state>
>
> Keep in mind I've omitted the view states and end states here, (I also
typed
> this on-the-fly) but this should get you started.
>
> Looking at the definition above, and given this need will be quite common,
> it may be wise for us to make the 'executeMethodName' property a first
class
> citizen in the DTD. Erwin, what do you think? Others? For example:
>
> <action id="myFormAction" executeMethod="submit"/>
>
> That would shorten the above xml a good bit, to:
>
> <action-state id="bindAndValidatePageFoo">
> <action id="myFormAction" executeMethod="bindAndValidate"/>
> <transition on="error" to="viewPageFoo"/>
> <transition on="success" to="viewPageBar"/>
> </action-state>
>
> <action-state id="bindAndValidatePageBar">
> <action id="myFormAction" executeMethod="bindAndValidate"/>
> <transition on="error" to="viewPageBar"/>
> <transition on="success" to="submit"/>
> </action-state>
>
> <action-state id="submit">
> <action id="myFormAction" executeMethod="submit"/>
> <transition on="error" to="error"/>
> <transition on="success" to="end"/>
> </action-state>
>
> It may also be wise to drop "Name" from "executeMethodName", leaving the
> shorter "executeMethod" - as name is sort of implied already anyway...
> (though name is more accurate from a implementation detail POV, but who
> cares about that here.)
>
> What do you think?
>
> Keith
>
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On Behalf
Of
> Steven Devijver
> Sent: Saturday, April 02, 2005 12:55 PM
> To: spr...@li...
> Subject: [Springframework-developer] webflow: FormAction question
>
> Hi,
>
> I want to create a wizard that spans across multiple pages. I want to
> bind to one and the same form instance across the different pages and
> validate on every page submit. When the wizard completes I want this
> one instance to contain all the information entered through the
> various forms.
>
> Can I use FormAction for this purpose?
>
> Thanks
>
> Steven
>
> --
> "If you want to be a different fish, you gotta jump out of the school."
> -- Captain Beefheart
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
--
"If you want to be a different fish, you gotta jump out of the school."
-- Captain Beefheart
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Dmitriy K. <dko...@ru...> - 2005-04-04 00:42:47
|
Also, could this code become a part of the sandbox for now? Dmitriy. Thierry TEMPLIER wrote: >Hi Dmitriy! > >Yes, I make some tests with JOTM, XAPool, Hypersonic >and the connector JCA of Joram (the JMS server of >objectweb)... and it works fine. However you need to >make the system contract of the connector (pooling, >transaction enlist/delist and security). I must make >cleaner code and try to delegate the pooling of >connection to dbcp (or other..). >Do you think that it could be interesting to implement >this feature in Spring? >Thierry > > > >>So that means that one would be able to use J2C >>(JCA) connector in a non-managed mode (with just a >>Servlet container + standalone JTA capable >>transaction coordinator) and have a full XA support >>with 2PC - no J2EE container required? That would be >> >> > > > >>cool! >> >>Dmitriy. >> >>Thierry TEMPLIER wrote: >> >> >> >>>In parallel of the JCA CCI support, I have made >>> >>> >>some >> >> >>>classes to plug JCA connectors, which support >>> >>> >>global >> >> >>>transactions, (enlist/delist) in the current JTA >>>transaction) in a non-managed mode. It works fine >>> >>> >>but >> >> >>>these classes need to improved... >>>Thierry >>> >>> >>> >>> >>> >>>>I can say from experience that JOTM and Spring >>>> >>>> >>work >> >> >>>>really well together. We've only plugged in JDBC >>>> >>>> >>XA >> >> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>>>resources, but so far, so good! >>>> >>>>Seth >>>> >>>> >>>> >>>> >>>Take a look at my blog: >>>http://templth.blogspot.com/ >>> >>> >>> >>> >>> >>> >>> >>> >>__________________________________________________________________ >> >> >>>Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace >>> >>> >>de stockage pour vos mails ! >> >> >>>Créez votre Yahoo! Mail sur >>> >>> >>http://fr.mail.yahoo.com/ >> >> >>> >>> >>------------------------------------------------------- >> >> >>>This SF.net email is sponsored by Demarc: >>>A global provider of Threat Management Solutions. >>>Download our HomeAdmin security software for free >>> >>> >>today! >> >> >>>http://www.demarc.com/info/Sentarus/hamr30 >>>_______________________________________________ >>>Springframework-user mailing list >>>Spr...@li... >>> >>> >>https://lists.sourceforge.net/lists/listinfo/springframework-user >> >> >>> >>> >>> >>> >> >> > > >Take a look at my blog: >http://templth.blogspot.com/ > > > > > > >__________________________________________________________________ >Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! >Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Springframework-user mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-user > > |
|
From: Dmitriy K. <dko...@ru...> - 2005-04-04 00:39:57
|
Thierry TEMPLIER wrote: >Hi Dmitriy! > >Yes, I make some tests with JOTM, XAPool, Hypersonic >and the connector JCA of Joram (the JMS server of >objectweb)... and it works fine. However you need to >make the system contract of the connector (pooling, >transaction enlist/delist and security). I must make >cleaner code and try to delegate the pooling of >connection to dbcp (or other..). > > >Do you think that it could be interesting to implement >this feature in Spring? > > > How much effort would implementing J2C system contracts require? Juergen, what do you think? Dmitriy. |
|
From: Keith D. <ke...@in...> - 2005-04-04 00:31:14
|
Is a package dependency from "util" to "core" acceptable? I could really use NestedRuntimeException there... Keith Keith Donald http://www.springframework.com <http://www.springframework.com/> - Spring Training, Consulting and Support - "From the Source" |
|
From: <al...@jt...> - 2005-04-03 22:32:16
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050404001553Lbuild.237 |
|
From: Keith D. <ke...@in...> - 2005-04-03 16:58:32
|
Update: support for a 'method' shortcut attribute on <action> element is in
CVS Head. This nicely reduces the amount of XML needed to specify a target
method on a multi-action instance.
Note: we've decided to keep the MultiAction class after all, as we feel it's
better to have consistency there with the Action interface, rather than have
any-old-object be invokable via reflection from an ActionState.
Keith
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Keith Donald
Sent: Saturday, April 02, 2005 1:52 PM
To: spr...@li...
Subject: RE: [Springframework-developer] webflow: FormAction question
Update: Erwin and I are also seriously considering removing Multi-Action
entirely, in favor of the ActionState doing the method dispatch if
appropriate. This is arguably cleaner and more flexible, and forces no
special inheritance requirement on your "multi-action" implementation.
Regarding backwards compatibility here: existing Multi-Action
implementations should continue to work, with the following caveats:
1. You'll just need to remove the 'extends MultiAction' clause if we decide
to remove that class. Your "Event <method>(RequestContext context)" action
execute method implementations won't have to change.
2. If your MultiAction leverages the AbstractAction pre-execute and
post-execute template methods (which we find are rarely used), you'll need
to use Spring AOP to achieve that pre/post execution logic. At some point
we may add support for declarative pre/post execute method as additional
properties for the ActionStateAction (e.g. <action ...> <property
name="preExecuteMethod" value="..."/></action>)
So we're proposing three things:
1. Rename of 'executeMethodName' property to 'method'.
2. Promotion of 'method' to first-class 'action' element attribute.
3. Remove of MultiAction in favor of method-based dispatch in the
ActionState class.
Keith
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Keith Donald
Sent: Saturday, April 02, 2005 1:14 PM
To: 'Keith Donald'; spr...@li...
Subject: RE: [Springframework-developer] webflow: FormAction question
Now that I think about it just "method" might be even better, as 'execute'
is also implied (actions all execute, duh):
<action id="myFormAction" method="bindAndValidate"/>
Thoughts?
Keith
-----Original Message-----
From: Keith Donald [mailto:ke...@in...]
Sent: Saturday, April 02, 2005 1:11 PM
To: 'spr...@li...'
Subject: RE: [Springframework-developer] webflow: FormAction question
Hey Steven,
Be sure to use the 'users' list or forum for questions like this next time,
so more users will see it.
You can use one FormAction to do this, yep. Erwin will be checking in a
wizard sample shortly (potentially this evening), so I'll just sum up what
the sample will illustrate:
- The FormAction already has a 'bindAndValidate' method, that does what you
want on each intermediate page submit. So you can have that method called
on each submit by using a bindAndValidate<X> action state, where <X>
describes what it is you are binding and validating.
For example:
<action-state id="bindAndValidatePageFoo">
<action id="myFormAction">
<property name="executeMethodName" value="bindAndValidate"/>
</action>
<transition on="error" to="viewPageFoo"/>
<transition on="success" to="viewPageBar"/>
</action-state>
<action-state id="bindAndValidatePageBar">
<action id="myFormAction">
<property name="executeMethodName" value="bindAndValidate"/>
</action>
<transition on="error" to="viewPageBar"/>
<transition on="success" to="submit"/>
</action-state>
<action-state id="submit">
<action id="myFormAction">
<property name="executeMethodName" value="submit"/>
</action>
<transition on="error" to="error"/>
<transition on="success" to="end"/>
</action-state>
Keep in mind I've omitted the view states and end states here, (I also typed
this on-the-fly) but this should get you started.
Looking at the definition above, and given this need will be quite common,
it may be wise for us to make the 'executeMethodName' property a first class
citizen in the DTD. Erwin, what do you think? Others? For example:
<action id="myFormAction" executeMethod="submit"/>
That would shorten the above xml a good bit, to:
<action-state id="bindAndValidatePageFoo">
<action id="myFormAction" executeMethod="bindAndValidate"/>
<transition on="error" to="viewPageFoo"/>
<transition on="success" to="viewPageBar"/>
</action-state>
<action-state id="bindAndValidatePageBar">
<action id="myFormAction" executeMethod="bindAndValidate"/>
<transition on="error" to="viewPageBar"/>
<transition on="success" to="submit"/>
</action-state>
<action-state id="submit">
<action id="myFormAction" executeMethod="submit"/>
<transition on="error" to="error"/>
<transition on="success" to="end"/>
</action-state>
It may also be wise to drop "Name" from "executeMethodName", leaving the
shorter "executeMethod" - as name is sort of implied already anyway...
(though name is more accurate from a implementation detail POV, but who
cares about that here.)
What do you think?
Keith
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Steven Devijver
Sent: Saturday, April 02, 2005 12:55 PM
To: spr...@li...
Subject: [Springframework-developer] webflow: FormAction question
Hi,
I want to create a wizard that spans across multiple pages. I want to
bind to one and the same form instance across the different pages and
validate on every page submit. When the wizard completes I want this
one instance to contain all the information entered through the
various forms.
Can I use FormAction for this purpose?
Thanks
Steven
--
"If you want to be a different fish, you gotta jump out of the school."
-- Captain Beefheart
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Brian M. <br...@ap...> - 2005-04-03 16:29:22
|
Cool. I've been javadoc-ing it, and cleaning up some of the duplication. Will keep poking at it locally until we figure out what to do with it. Spring main, Spring Modules, Lucene contrib, just self hosted, however it goes =) Figured I had it, and a bunch of folks I know asked for it, so might as well share. -Brian On Apr 3, 2005, at 7:00 AM, Rob Harrop wrote: > Brian, > > I took a look at the code and it looks really useful. I had actually > started something similar but I am no where near where you are with > your code. > > I'm happy to work with you on this code - we just need to decide where > to put it. I had originally intended to put my code in the fledgling > Spring Modules project, but we should evaluate the possibility of > putting it in Spring main. > > What are everyone's thought. Lucene is a relatively small JAR at only > 316K so it won't have a huge impact on distribution size. > > Rob > > Brian McCallister wrote: > >> snapshot of the classes as they are now: >> >> http://morphy.skife.org/spring-lucene/ >> >> -Brian >> >> On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: >> >>> I have a set of classes for Apache Lucene integration with Spring >>> (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which >>> are designed to >>> >>> a) make it easier to work with Lucene from Spring (the template in >>> particular optimizes common cases nicely, and does the resource >>> open/closing like the other templates) >>> >>> b) make lucene index modifications abide by Spring's transaction >>> system by doing write-behind on adds (which are ignored on rollback) >>> and rolling back deletes via a transaction synchronization. >>> >>> >>> >>> I'd like to contribute them to Spring (if ya'll are interested), but >>> to clean up the code and design some first, I have a few questions: >>> >>> 1) Should transaction binding be "on" by default? Lucene is >>> semi-transactional by nature (supports r and r/w locks, changes are >>> flushed on reader/writer closing, etc), but I am not sure people >>> expect Lucene to be bound by other transactions. Potential >>> confusion. >>> >>> 2) What is a good tx manager to use for the unit tests? I am using a >>> modified version of the TestTransactionManager in Spring right now >>> (just changed to make it accessible and use synchonrizations). It is >>> much easier to use the TransactionTemplate than to manually manage >>> the tx's for tests =) >>> >>> 3) Not all of the ~interesting things you can do in lucene are >>> convenient to expose (splitting indexes etc) from the configuration. >>> Right now, rather than make a hack, the factory beans only support >>> single indexes. The only multi-index thing exposed right now is >>> really a configuration option on the SearcherBean which allows for >>> multiple indexes and a MultiSearcher ~transparently. >>> >>> Thanks! >>> >>> -Brian >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Erwin V. <erw...@er...> - 2005-04-03 15:02:26
|
About FormAction: yes, but it uses "formObjectName" and "formObjectClass". Erwin Vervaet erw...@er... ----- Original Message ----- From: "Steven Devijver" <ste...@gm...> To: <spr...@li...> Sent: Sunday, April 03, 2005 12:43 PM Subject: Re: [Springframework-developer] webflow: FormAction question > Keith, > > Wow, this personal support thing you guys are doing is really cool :-) > > One more question, just for my understanding: > > The 'bindAndValidate' method on FormAction checks if an instance is > available under 'commandName' and if not creates an instance specified > by 'commandClass'. Is this correct. > > Thanks > > Steven > > > On Apr 3, 2005 8:20 AM, Keith Donald <ke...@in...> wrote: >> Steven, >> >> 1.) setupForm is called if and when you want it to be called - with >> Spring >> webflow, you define the workflow explicitly and what actions (or target >> methods) should be called on what events. That's the inherent power in >> web >> flows---the action methods don't contain any workflow, they just execute >> some logic-- the flow itself fully defines the workflow, dynamically. >> >> Checkout the new 'sellitem' sample in samples/webflow in CVS to see how >> it >> calls 'setupForm' at the beginning of the wizard flow. >> >> 2.) You could always do custom validation logic for each page in the >> action >> that processes each submit, in a custom method that you define, like >> "public >> bindAndValidateShippingDetails(RequestContext context)". However, I am >> thinking it makes sense to have the FormAction aware of a action property >> called 'validatorMethod' that will be invoked by ValidatorUtils, to allow >> piecemeal validation of the domain object on a per page basis (instead of >> always calling the 'validate' method, which validates the whole object). >> Either that or perhaps we need a WizardFormAction that provides specific >> support for this. Thoughts? >> >> Keith >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...] On Behalf >> Of >> Steven Devijver >> Sent: Saturday, April 02, 2005 4:41 PM >> To: spr...@li... >> Subject: Re: [Springframework-developer] webflow: FormAction question >> >> Keith, >> >> Thanks for the feedback an my apologies for not posting on the user >> list. There's two things that aren't clear to me: >> >> 1) is setupForm on FormAction called only once and if so where and why >> only there? >> >> 2) how can I validate every page/form separately saying this or that >> is missing? Every form submit uses the same validator, how can it >> validate only the properties related to the form? >> >> Thanks >> >> Steven >> >> On Apr 2, 2005 8:11 PM, Keith Donald <ke...@in...> wrote: >> > Hey Steven, >> > >> > Be sure to use the 'users' list or forum for questions like this next >> time, >> > so more users will see it. >> > >> > You can use one FormAction to do this, yep. Erwin will be checking in >> > a >> > wizard sample shortly (potentially this evening), so I'll just sum up >> > what >> > the sample will illustrate: >> > >> > - The FormAction already has a 'bindAndValidate' method, that does what >> you >> > want on each intermediate page submit. So you can have that method >> > called >> > on each submit by using a bindAndValidate<X> action state, where <X> >> > describes what it is you are binding and validating. >> > >> > For example: >> > >> > <action-state id="bindAndValidatePageFoo"> >> > <action id="myFormAction"> >> > <property name="executeMethodName" value="bindAndValidate"/> >> > </action> >> > <transition on="error" to="viewPageFoo"/> >> > <transition on="success" to="viewPageBar"/> >> > </action-state> >> > >> > <action-state id="bindAndValidatePageBar"> >> > <action id="myFormAction"> >> > <property name="executeMethodName" value="bindAndValidate"/> >> > </action> >> > <transition on="error" to="viewPageBar"/> >> > <transition on="success" to="submit"/> >> > </action-state> >> > >> > <action-state id="submit"> >> > <action id="myFormAction"> >> > <property name="executeMethodName" value="submit"/> >> > </action> >> > <transition on="error" to="error"/> >> > <transition on="success" to="end"/> >> > </action-state> >> > >> > Keep in mind I've omitted the view states and end states here, (I also >> typed >> > this on-the-fly) but this should get you started. >> > >> > Looking at the definition above, and given this need will be quite >> > common, >> > it may be wise for us to make the 'executeMethodName' property a first >> class >> > citizen in the DTD. Erwin, what do you think? Others? For example: >> > >> > <action id="myFormAction" executeMethod="submit"/> >> > >> > That would shorten the above xml a good bit, to: >> > >> > <action-state id="bindAndValidatePageFoo"> >> > <action id="myFormAction" executeMethod="bindAndValidate"/> >> > <transition on="error" to="viewPageFoo"/> >> > <transition on="success" to="viewPageBar"/> >> > </action-state> >> > >> > <action-state id="bindAndValidatePageBar"> >> > <action id="myFormAction" executeMethod="bindAndValidate"/> >> > <transition on="error" to="viewPageBar"/> >> > <transition on="success" to="submit"/> >> > </action-state> >> > >> > <action-state id="submit"> >> > <action id="myFormAction" executeMethod="submit"/> >> > <transition on="error" to="error"/> >> > <transition on="success" to="end"/> >> > </action-state> >> > >> > It may also be wise to drop "Name" from "executeMethodName", leaving >> > the >> > shorter "executeMethod" - as name is sort of implied already anyway... >> > (though name is more accurate from a implementation detail POV, but who >> > cares about that here.) >> > >> > What do you think? >> > >> > Keith >> > >> > -----Original Message----- >> > From: spr...@li... >> > [mailto:spr...@li...] On >> > Behalf >> Of >> > Steven Devijver >> > Sent: Saturday, April 02, 2005 12:55 PM >> > To: spr...@li... >> > Subject: [Springframework-developer] webflow: FormAction question >> > >> > Hi, >> > >> > I want to create a wizard that spans across multiple pages. I want to >> > bind to one and the same form instance across the different pages and >> > validate on every page submit. When the wizard completes I want this >> > one instance to contain all the information entered through the >> > various forms. >> > >> > Can I use FormAction for this purpose? >> > >> > Thanks >> > >> > Steven >> > >> > -- >> > "If you want to be a different fish, you gotta jump out of the school." >> > -- Captain Beefheart >> > >> > ------------------------------------------------------- >> > SF email is sponsored by - The IT Product Guide >> > Read honest & candid reviews on hundreds of IT Products from real >> > users. >> > Discover which products truly live up to the hype. Start reading now. >> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> > _______________________________________________ >> > Springframework-developer mailing list >> > Spr...@li... >> > https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > >> > ------------------------------------------------------- >> > SF email is sponsored by - The IT Product Guide >> > Read honest & candid reviews on hundreds of IT Products from real >> > users. >> > Discover which products truly live up to the hype. Start reading now. >> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> > _______________________________________________ >> > Springframework-developer mailing list >> > Spr...@li... >> > https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > >> > >> >> -- >> "If you want to be a different fish, you gotta jump out of the school." >> -- Captain Beefheart >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > > > -- > "If you want to be a different fish, you gotta jump out of the school." > -- Captain Beefheart > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Brian M. <br...@ch...> - 2005-04-03 14:30:40
|
Cool. I've been javadoc-ing it, and cleaning up some of the duplication. Will keep poking at it locally until we figure out what to do with it. Spring main, Spring Modules, Lucene contrib, just self hosted, however it goes =) Figured I had it, and a bunch of folks I know asked for it, so might as well share. -Brian On Apr 3, 2005, at 7:00 AM, Rob Harrop wrote: > Brian, > > I took a look at the code and it looks really useful. I had actually > started something similar but I am no where near where you are with > your code. > > I'm happy to work with you on this code - we just need to decide where > to put it. I had originally intended to put my code in the fledgling > Spring Modules project, but we should evaluate the possibility of > putting it in Spring main. > > What are everyone's thought. Lucene is a relatively small JAR at only > 316K so it won't have a huge impact on distribution size. > > Rob > > Brian McCallister wrote: > >> snapshot of the classes as they are now: >> >> http://morphy.skife.org/spring-lucene/ >> >> -Brian >> >> On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: >> >>> I have a set of classes for Apache Lucene integration with Spring >>> (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which >>> are designed to >>> >>> a) make it easier to work with Lucene from Spring (the template in >>> particular optimizes common cases nicely, and does the resource >>> open/closing like the other templates) >>> >>> b) make lucene index modifications abide by Spring's transaction >>> system by doing write-behind on adds (which are ignored on rollback) >>> and rolling back deletes via a transaction synchronization. >>> >>> >>> >>> I'd like to contribute them to Spring (if ya'll are interested), but >>> to clean up the code and design some first, I have a few questions: >>> >>> 1) Should transaction binding be "on" by default? Lucene is >>> semi-transactional by nature (supports r and r/w locks, changes are >>> flushed on reader/writer closing, etc), but I am not sure people >>> expect Lucene to be bound by other transactions. Potential >>> confusion. >>> >>> 2) What is a good tx manager to use for the unit tests? I am using a >>> modified version of the TestTransactionManager in Spring right now >>> (just changed to make it accessible and use synchonrizations). It is >>> much easier to use the TransactionTemplate than to manually manage >>> the tx's for tests =) >>> >>> 3) Not all of the ~interesting things you can do in lucene are >>> convenient to expose (splitting indexes etc) from the configuration. >>> Right now, rather than make a hack, the factory beans only support >>> single indexes. The only multi-index thing exposed right now is >>> really a configuration option on the SearcherBean which allows for >>> multiple indexes and a MultiSearcher ~transparently. >>> >>> Thanks! >>> >>> -Brian >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Rob H. <ro...@ca...> - 2005-04-03 11:02:17
|
Brian, I took a look at the code and it looks really useful. I had actually started something similar but I am no where near where you are with your code. I'm happy to work with you on this code - we just need to decide where to put it. I had originally intended to put my code in the fledgling Spring Modules project, but we should evaluate the possibility of putting it in Spring main. What are everyone's thought. Lucene is a relatively small JAR at only 316K so it won't have a huge impact on distribution size. Rob Brian McCallister wrote: > snapshot of the classes as they are now: > > http://morphy.skife.org/spring-lucene/ > > -Brian > > On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: > >> I have a set of classes for Apache Lucene integration with Spring >> (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which >> are designed to >> >> a) make it easier to work with Lucene from Spring (the template in >> particular optimizes common cases nicely, and does the resource >> open/closing like the other templates) >> >> b) make lucene index modifications abide by Spring's transaction >> system by doing write-behind on adds (which are ignored on rollback) >> and rolling back deletes via a transaction synchronization. >> >> >> >> I'd like to contribute them to Spring (if ya'll are interested), but >> to clean up the code and design some first, I have a few questions: >> >> 1) Should transaction binding be "on" by default? Lucene is >> semi-transactional by nature (supports r and r/w locks, changes are >> flushed on reader/writer closing, etc), but I am not sure people >> expect Lucene to be bound by other transactions. Potential confusion. >> >> 2) What is a good tx manager to use for the unit tests? I am using a >> modified version of the TestTransactionManager in Spring right now >> (just changed to make it accessible and use synchonrizations). It is >> much easier to use the TransactionTemplate than to manually manage >> the tx's for tests =) >> >> 3) Not all of the ~interesting things you can do in lucene are >> convenient to expose (splitting indexes etc) from the configuration. >> Right now, rather than make a hack, the factory beans only support >> single indexes. The only multi-index thing exposed right now is >> really a configuration option on the SearcherBean which allows for >> multiple indexes and a MultiSearcher ~transparently. >> >> Thanks! >> >> -Brian >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Steven D. <ste...@gm...> - 2005-04-03 10:43:34
|
Keith, Wow, this personal support thing you guys are doing is really cool :-) One more question, just for my understanding: The 'bindAndValidate' method on FormAction checks if an instance is available under 'commandName' and if not creates an instance specified by 'commandClass'. Is this correct. Thanks Steven On Apr 3, 2005 8:20 AM, Keith Donald <ke...@in...> wrote: > Steven, > > 1.) setupForm is called if and when you want it to be called - with Spring > webflow, you define the workflow explicitly and what actions (or target > methods) should be called on what events. That's the inherent power in web > flows---the action methods don't contain any workflow, they just execute > some logic-- the flow itself fully defines the workflow, dynamically. > > Checkout the new 'sellitem' sample in samples/webflow in CVS to see how it > calls 'setupForm' at the beginning of the wizard flow. > > 2.) You could always do custom validation logic for each page in the action > that processes each submit, in a custom method that you define, like "public > bindAndValidateShippingDetails(RequestContext context)". However, I am > thinking it makes sense to have the FormAction aware of a action property > called 'validatorMethod' that will be invoked by ValidatorUtils, to allow > piecemeal validation of the domain object on a per page basis (instead of > always calling the 'validate' method, which validates the whole object). > Either that or perhaps we need a WizardFormAction that provides specific > support for this. Thoughts? > > Keith > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf Of > Steven Devijver > Sent: Saturday, April 02, 2005 4:41 PM > To: spr...@li... > Subject: Re: [Springframework-developer] webflow: FormAction question > > Keith, > > Thanks for the feedback an my apologies for not posting on the user > list. There's two things that aren't clear to me: > > 1) is setupForm on FormAction called only once and if so where and why > only there? > > 2) how can I validate every page/form separately saying this or that > is missing? Every form submit uses the same validator, how can it > validate only the properties related to the form? > > Thanks > > Steven > > On Apr 2, 2005 8:11 PM, Keith Donald <ke...@in...> wrote: > > Hey Steven, > > > > Be sure to use the 'users' list or forum for questions like this next > time, > > so more users will see it. > > > > You can use one FormAction to do this, yep. Erwin will be checking in a > > wizard sample shortly (potentially this evening), so I'll just sum up what > > the sample will illustrate: > > > > - The FormAction already has a 'bindAndValidate' method, that does what > you > > want on each intermediate page submit. So you can have that method called > > on each submit by using a bindAndValidate<X> action state, where <X> > > describes what it is you are binding and validating. > > > > For example: > > > > <action-state id="bindAndValidatePageFoo"> > > <action id="myFormAction"> > > <property name="executeMethodName" value="bindAndValidate"/> > > </action> > > <transition on="error" to="viewPageFoo"/> > > <transition on="success" to="viewPageBar"/> > > </action-state> > > > > <action-state id="bindAndValidatePageBar"> > > <action id="myFormAction"> > > <property name="executeMethodName" value="bindAndValidate"/> > > </action> > > <transition on="error" to="viewPageBar"/> > > <transition on="success" to="submit"/> > > </action-state> > > > > <action-state id="submit"> > > <action id="myFormAction"> > > <property name="executeMethodName" value="submit"/> > > </action> > > <transition on="error" to="error"/> > > <transition on="success" to="end"/> > > </action-state> > > > > Keep in mind I've omitted the view states and end states here, (I also > typed > > this on-the-fly) but this should get you started. > > > > Looking at the definition above, and given this need will be quite common, > > it may be wise for us to make the 'executeMethodName' property a first > class > > citizen in the DTD. Erwin, what do you think? Others? For example: > > > > <action id="myFormAction" executeMethod="submit"/> > > > > That would shorten the above xml a good bit, to: > > > > <action-state id="bindAndValidatePageFoo"> > > <action id="myFormAction" executeMethod="bindAndValidate"/> > > <transition on="error" to="viewPageFoo"/> > > <transition on="success" to="viewPageBar"/> > > </action-state> > > > > <action-state id="bindAndValidatePageBar"> > > <action id="myFormAction" executeMethod="bindAndValidate"/> > > <transition on="error" to="viewPageBar"/> > > <transition on="success" to="submit"/> > > </action-state> > > > > <action-state id="submit"> > > <action id="myFormAction" executeMethod="submit"/> > > <transition on="error" to="error"/> > > <transition on="success" to="end"/> > > </action-state> > > > > It may also be wise to drop "Name" from "executeMethodName", leaving the > > shorter "executeMethod" - as name is sort of implied already anyway... > > (though name is more accurate from a implementation detail POV, but who > > cares about that here.) > > > > What do you think? > > > > Keith > > > > -----Original Message----- > > From: spr...@li... > > [mailto:spr...@li...] On Behalf > Of > > Steven Devijver > > Sent: Saturday, April 02, 2005 12:55 PM > > To: spr...@li... > > Subject: [Springframework-developer] webflow: FormAction question > > > > Hi, > > > > I want to create a wizard that spans across multiple pages. I want to > > bind to one and the same form instance across the different pages and > > validate on every page submit. When the wizard completes I want this > > one instance to contain all the information entered through the > > various forms. > > > > Can I use FormAction for this purpose? > > > > Thanks > > > > Steven > > > > -- > > "If you want to be a different fish, you gotta jump out of the school." > > -- Captain Beefheart > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > Springframework-developer mailing list > > Spr...@li... > > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > > -- > "If you want to be a different fish, you gotta jump out of the school." > -- Captain Beefheart > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > -- "If you want to be a different fish, you gotta jump out of the school." -- Captain Beefheart |
|
From: Keith D. <ke...@in...> - 2005-04-03 08:03:37
|
Cool, I've added it. We're keeping the change log updated as we add new features here: http://opensource.atlassian.com/confluence/spring/display/WEBFLOW/Change+Log We'll likely cut PR2 soon given we've already got a good deal of new stuff. Keith -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Erwin Vervaet Sent: Sunday, April 03, 2005 1:59 AM To: spr...@li... Subject: Re: [Springframework-developer] webflow: FormAction question I pretty much like the extra validatorMethod property for FormAction. Erwin Vervaet erw...@er... ----- Original Message ----- From: "Keith Donald" <ke...@in...> To: <spr...@li...> Sent: Sunday, April 03, 2005 8:20 AM Subject: RE: [Springframework-developer] webflow: FormAction question > Steven, > > 1.) setupForm is called if and when you want it to be called - with Spring > webflow, you define the workflow explicitly and what actions (or target > methods) should be called on what events. That's the inherent power in > web > flows---the action methods don't contain any workflow, they just execute > some logic-- the flow itself fully defines the workflow, dynamically. > > Checkout the new 'sellitem' sample in samples/webflow in CVS to see how it > calls 'setupForm' at the beginning of the wizard flow. > > 2.) You could always do custom validation logic for each page in the > action > that processes each submit, in a custom method that you define, like > "public > bindAndValidateShippingDetails(RequestContext context)". However, I am > thinking it makes sense to have the FormAction aware of a action property > called 'validatorMethod' that will be invoked by ValidatorUtils, to allow > piecemeal validation of the domain object on a per page basis (instead of > always calling the 'validate' method, which validates the whole object). > Either that or perhaps we need a WizardFormAction that provides specific > support for this. Thoughts? > > Keith > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf > Of > Steven Devijver > Sent: Saturday, April 02, 2005 4:41 PM > To: spr...@li... > Subject: Re: [Springframework-developer] webflow: FormAction question > > Keith, > > Thanks for the feedback an my apologies for not posting on the user > list. There's two things that aren't clear to me: > > 1) is setupForm on FormAction called only once and if so where and why > only there? > > 2) how can I validate every page/form separately saying this or that > is missing? Every form submit uses the same validator, how can it > validate only the properties related to the form? > > Thanks > > Steven > > On Apr 2, 2005 8:11 PM, Keith Donald <ke...@in...> wrote: >> Hey Steven, >> >> Be sure to use the 'users' list or forum for questions like this next > time, >> so more users will see it. >> >> You can use one FormAction to do this, yep. Erwin will be checking in a >> wizard sample shortly (potentially this evening), so I'll just sum up >> what >> the sample will illustrate: >> >> - The FormAction already has a 'bindAndValidate' method, that does what > you >> want on each intermediate page submit. So you can have that method >> called >> on each submit by using a bindAndValidate<X> action state, where <X> >> describes what it is you are binding and validating. >> >> For example: >> >> <action-state id="bindAndValidatePageFoo"> >> <action id="myFormAction"> >> <property name="executeMethodName" value="bindAndValidate"/> >> </action> >> <transition on="error" to="viewPageFoo"/> >> <transition on="success" to="viewPageBar"/> >> </action-state> >> >> <action-state id="bindAndValidatePageBar"> >> <action id="myFormAction"> >> <property name="executeMethodName" value="bindAndValidate"/> >> </action> >> <transition on="error" to="viewPageBar"/> >> <transition on="success" to="submit"/> >> </action-state> >> >> <action-state id="submit"> >> <action id="myFormAction"> >> <property name="executeMethodName" value="submit"/> >> </action> >> <transition on="error" to="error"/> >> <transition on="success" to="end"/> >> </action-state> >> >> Keep in mind I've omitted the view states and end states here, (I also > typed >> this on-the-fly) but this should get you started. >> >> Looking at the definition above, and given this need will be quite >> common, >> it may be wise for us to make the 'executeMethodName' property a first > class >> citizen in the DTD. Erwin, what do you think? Others? For example: >> >> <action id="myFormAction" executeMethod="submit"/> >> >> That would shorten the above xml a good bit, to: >> >> <action-state id="bindAndValidatePageFoo"> >> <action id="myFormAction" executeMethod="bindAndValidate"/> >> <transition on="error" to="viewPageFoo"/> >> <transition on="success" to="viewPageBar"/> >> </action-state> >> >> <action-state id="bindAndValidatePageBar"> >> <action id="myFormAction" executeMethod="bindAndValidate"/> >> <transition on="error" to="viewPageBar"/> >> <transition on="success" to="submit"/> >> </action-state> >> >> <action-state id="submit"> >> <action id="myFormAction" executeMethod="submit"/> >> <transition on="error" to="error"/> >> <transition on="success" to="end"/> >> </action-state> >> >> It may also be wise to drop "Name" from "executeMethodName", leaving the >> shorter "executeMethod" - as name is sort of implied already anyway... >> (though name is more accurate from a implementation detail POV, but who >> cares about that here.) >> >> What do you think? >> >> Keith >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...] On Behalf > Of >> Steven Devijver >> Sent: Saturday, April 02, 2005 12:55 PM >> To: spr...@li... >> Subject: [Springframework-developer] webflow: FormAction question >> >> Hi, >> >> I want to create a wizard that spans across multiple pages. I want to >> bind to one and the same form instance across the different pages and >> validate on every page submit. When the wizard completes I want this >> one instance to contain all the information entered through the >> various forms. >> >> Can I use FormAction for this purpose? >> >> Thanks >> >> Steven >> >> -- >> "If you want to be a different fish, you gotta jump out of the school." >> -- Captain Beefheart >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > > > -- > "If you want to be a different fish, you gotta jump out of the school." > -- Captain Beefheart > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Erwin V. <erw...@er...> - 2005-04-03 07:13:02
|
I pretty much like the extra validatorMethod property for FormAction. Erwin Vervaet erw...@er... ----- Original Message ----- From: "Keith Donald" <ke...@in...> To: <spr...@li...> Sent: Sunday, April 03, 2005 8:20 AM Subject: RE: [Springframework-developer] webflow: FormAction question > Steven, > > 1.) setupForm is called if and when you want it to be called - with Spring > webflow, you define the workflow explicitly and what actions (or target > methods) should be called on what events. That's the inherent power in > web > flows---the action methods don't contain any workflow, they just execute > some logic-- the flow itself fully defines the workflow, dynamically. > > Checkout the new 'sellitem' sample in samples/webflow in CVS to see how it > calls 'setupForm' at the beginning of the wizard flow. > > 2.) You could always do custom validation logic for each page in the > action > that processes each submit, in a custom method that you define, like > "public > bindAndValidateShippingDetails(RequestContext context)". However, I am > thinking it makes sense to have the FormAction aware of a action property > called 'validatorMethod' that will be invoked by ValidatorUtils, to allow > piecemeal validation of the domain object on a per page basis (instead of > always calling the 'validate' method, which validates the whole object). > Either that or perhaps we need a WizardFormAction that provides specific > support for this. Thoughts? > > Keith > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf > Of > Steven Devijver > Sent: Saturday, April 02, 2005 4:41 PM > To: spr...@li... > Subject: Re: [Springframework-developer] webflow: FormAction question > > Keith, > > Thanks for the feedback an my apologies for not posting on the user > list. There's two things that aren't clear to me: > > 1) is setupForm on FormAction called only once and if so where and why > only there? > > 2) how can I validate every page/form separately saying this or that > is missing? Every form submit uses the same validator, how can it > validate only the properties related to the form? > > Thanks > > Steven > > On Apr 2, 2005 8:11 PM, Keith Donald <ke...@in...> wrote: >> Hey Steven, >> >> Be sure to use the 'users' list or forum for questions like this next > time, >> so more users will see it. >> >> You can use one FormAction to do this, yep. Erwin will be checking in a >> wizard sample shortly (potentially this evening), so I'll just sum up >> what >> the sample will illustrate: >> >> - The FormAction already has a 'bindAndValidate' method, that does what > you >> want on each intermediate page submit. So you can have that method >> called >> on each submit by using a bindAndValidate<X> action state, where <X> >> describes what it is you are binding and validating. >> >> For example: >> >> <action-state id="bindAndValidatePageFoo"> >> <action id="myFormAction"> >> <property name="executeMethodName" value="bindAndValidate"/> >> </action> >> <transition on="error" to="viewPageFoo"/> >> <transition on="success" to="viewPageBar"/> >> </action-state> >> >> <action-state id="bindAndValidatePageBar"> >> <action id="myFormAction"> >> <property name="executeMethodName" value="bindAndValidate"/> >> </action> >> <transition on="error" to="viewPageBar"/> >> <transition on="success" to="submit"/> >> </action-state> >> >> <action-state id="submit"> >> <action id="myFormAction"> >> <property name="executeMethodName" value="submit"/> >> </action> >> <transition on="error" to="error"/> >> <transition on="success" to="end"/> >> </action-state> >> >> Keep in mind I've omitted the view states and end states here, (I also > typed >> this on-the-fly) but this should get you started. >> >> Looking at the definition above, and given this need will be quite >> common, >> it may be wise for us to make the 'executeMethodName' property a first > class >> citizen in the DTD. Erwin, what do you think? Others? For example: >> >> <action id="myFormAction" executeMethod="submit"/> >> >> That would shorten the above xml a good bit, to: >> >> <action-state id="bindAndValidatePageFoo"> >> <action id="myFormAction" executeMethod="bindAndValidate"/> >> <transition on="error" to="viewPageFoo"/> >> <transition on="success" to="viewPageBar"/> >> </action-state> >> >> <action-state id="bindAndValidatePageBar"> >> <action id="myFormAction" executeMethod="bindAndValidate"/> >> <transition on="error" to="viewPageBar"/> >> <transition on="success" to="submit"/> >> </action-state> >> >> <action-state id="submit"> >> <action id="myFormAction" executeMethod="submit"/> >> <transition on="error" to="error"/> >> <transition on="success" to="end"/> >> </action-state> >> >> It may also be wise to drop "Name" from "executeMethodName", leaving the >> shorter "executeMethod" - as name is sort of implied already anyway... >> (though name is more accurate from a implementation detail POV, but who >> cares about that here.) >> >> What do you think? >> >> Keith >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...] On Behalf > Of >> Steven Devijver >> Sent: Saturday, April 02, 2005 12:55 PM >> To: spr...@li... >> Subject: [Springframework-developer] webflow: FormAction question >> >> Hi, >> >> I want to create a wizard that spans across multiple pages. I want to >> bind to one and the same form instance across the different pages and >> validate on every page submit. When the wizard completes I want this >> one instance to contain all the information entered through the >> various forms. >> >> Can I use FormAction for this purpose? >> >> Thanks >> >> Steven >> >> -- >> "If you want to be a different fish, you gotta jump out of the school." >> -- Captain Beefheart >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > > > -- > "If you want to be a different fish, you gotta jump out of the school." > -- Captain Beefheart > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Keith D. <ke...@in...> - 2005-04-03 06:21:09
|
Steven, 1.) setupForm is called if and when you want it to be called - with Spring webflow, you define the workflow explicitly and what actions (or target methods) should be called on what events. That's the inherent power in web flows---the action methods don't contain any workflow, they just execute some logic-- the flow itself fully defines the workflow, dynamically. Checkout the new 'sellitem' sample in samples/webflow in CVS to see how it calls 'setupForm' at the beginning of the wizard flow. 2.) You could always do custom validation logic for each page in the action that processes each submit, in a custom method that you define, like "public bindAndValidateShippingDetails(RequestContext context)". However, I am thinking it makes sense to have the FormAction aware of a action property called 'validatorMethod' that will be invoked by ValidatorUtils, to allow piecemeal validation of the domain object on a per page basis (instead of always calling the 'validate' method, which validates the whole object). Either that or perhaps we need a WizardFormAction that provides specific support for this. Thoughts? Keith -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Steven Devijver Sent: Saturday, April 02, 2005 4:41 PM To: spr...@li... Subject: Re: [Springframework-developer] webflow: FormAction question Keith, Thanks for the feedback an my apologies for not posting on the user list. There's two things that aren't clear to me: 1) is setupForm on FormAction called only once and if so where and why only there? 2) how can I validate every page/form separately saying this or that is missing? Every form submit uses the same validator, how can it validate only the properties related to the form? Thanks Steven On Apr 2, 2005 8:11 PM, Keith Donald <ke...@in...> wrote: > Hey Steven, > > Be sure to use the 'users' list or forum for questions like this next time, > so more users will see it. > > You can use one FormAction to do this, yep. Erwin will be checking in a > wizard sample shortly (potentially this evening), so I'll just sum up what > the sample will illustrate: > > - The FormAction already has a 'bindAndValidate' method, that does what you > want on each intermediate page submit. So you can have that method called > on each submit by using a bindAndValidate<X> action state, where <X> > describes what it is you are binding and validating. > > For example: > > <action-state id="bindAndValidatePageFoo"> > <action id="myFormAction"> > <property name="executeMethodName" value="bindAndValidate"/> > </action> > <transition on="error" to="viewPageFoo"/> > <transition on="success" to="viewPageBar"/> > </action-state> > > <action-state id="bindAndValidatePageBar"> > <action id="myFormAction"> > <property name="executeMethodName" value="bindAndValidate"/> > </action> > <transition on="error" to="viewPageBar"/> > <transition on="success" to="submit"/> > </action-state> > > <action-state id="submit"> > <action id="myFormAction"> > <property name="executeMethodName" value="submit"/> > </action> > <transition on="error" to="error"/> > <transition on="success" to="end"/> > </action-state> > > Keep in mind I've omitted the view states and end states here, (I also typed > this on-the-fly) but this should get you started. > > Looking at the definition above, and given this need will be quite common, > it may be wise for us to make the 'executeMethodName' property a first class > citizen in the DTD. Erwin, what do you think? Others? For example: > > <action id="myFormAction" executeMethod="submit"/> > > That would shorten the above xml a good bit, to: > > <action-state id="bindAndValidatePageFoo"> > <action id="myFormAction" executeMethod="bindAndValidate"/> > <transition on="error" to="viewPageFoo"/> > <transition on="success" to="viewPageBar"/> > </action-state> > > <action-state id="bindAndValidatePageBar"> > <action id="myFormAction" executeMethod="bindAndValidate"/> > <transition on="error" to="viewPageBar"/> > <transition on="success" to="submit"/> > </action-state> > > <action-state id="submit"> > <action id="myFormAction" executeMethod="submit"/> > <transition on="error" to="error"/> > <transition on="success" to="end"/> > </action-state> > > It may also be wise to drop "Name" from "executeMethodName", leaving the > shorter "executeMethod" - as name is sort of implied already anyway... > (though name is more accurate from a implementation detail POV, but who > cares about that here.) > > What do you think? > > Keith > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf Of > Steven Devijver > Sent: Saturday, April 02, 2005 12:55 PM > To: spr...@li... > Subject: [Springframework-developer] webflow: FormAction question > > Hi, > > I want to create a wizard that spans across multiple pages. I want to > bind to one and the same form instance across the different pages and > validate on every page submit. When the wizard completes I want this > one instance to contain all the information entered through the > various forms. > > Can I use FormAction for this purpose? > > Thanks > > Steven > > -- > "If you want to be a different fish, you gotta jump out of the school." > -- Captain Beefheart > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > -- "If you want to be a different fish, you gotta jump out of the school." -- Captain Beefheart ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <al...@jt...> - 2005-04-02 22:34:45
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050403001645Lbuild.236 |
|
From: Steven D. <ste...@gm...> - 2005-04-02 21:41:35
|
Keith, Thanks for the feedback an my apologies for not posting on the user list. There's two things that aren't clear to me: 1) is setupForm on FormAction called only once and if so where and why only there? 2) how can I validate every page/form separately saying this or that is missing? Every form submit uses the same validator, how can it validate only the properties related to the form? Thanks Steven On Apr 2, 2005 8:11 PM, Keith Donald <ke...@in...> wrote: > Hey Steven, > > Be sure to use the 'users' list or forum for questions like this next time, > so more users will see it. > > You can use one FormAction to do this, yep. Erwin will be checking in a > wizard sample shortly (potentially this evening), so I'll just sum up what > the sample will illustrate: > > - The FormAction already has a 'bindAndValidate' method, that does what you > want on each intermediate page submit. So you can have that method called > on each submit by using a bindAndValidate<X> action state, where <X> > describes what it is you are binding and validating. > > For example: > > <action-state id="bindAndValidatePageFoo"> > <action id="myFormAction"> > <property name="executeMethodName" value="bindAndValidate"/> > </action> > <transition on="error" to="viewPageFoo"/> > <transition on="success" to="viewPageBar"/> > </action-state> > > <action-state id="bindAndValidatePageBar"> > <action id="myFormAction"> > <property name="executeMethodName" value="bindAndValidate"/> > </action> > <transition on="error" to="viewPageBar"/> > <transition on="success" to="submit"/> > </action-state> > > <action-state id="submit"> > <action id="myFormAction"> > <property name="executeMethodName" value="submit"/> > </action> > <transition on="error" to="error"/> > <transition on="success" to="end"/> > </action-state> > > Keep in mind I've omitted the view states and end states here, (I also typed > this on-the-fly) but this should get you started. > > Looking at the definition above, and given this need will be quite common, > it may be wise for us to make the 'executeMethodName' property a first class > citizen in the DTD. Erwin, what do you think? Others? For example: > > <action id="myFormAction" executeMethod="submit"/> > > That would shorten the above xml a good bit, to: > > <action-state id="bindAndValidatePageFoo"> > <action id="myFormAction" executeMethod="bindAndValidate"/> > <transition on="error" to="viewPageFoo"/> > <transition on="success" to="viewPageBar"/> > </action-state> > > <action-state id="bindAndValidatePageBar"> > <action id="myFormAction" executeMethod="bindAndValidate"/> > <transition on="error" to="viewPageBar"/> > <transition on="success" to="submit"/> > </action-state> > > <action-state id="submit"> > <action id="myFormAction" executeMethod="submit"/> > <transition on="error" to="error"/> > <transition on="success" to="end"/> > </action-state> > > It may also be wise to drop "Name" from "executeMethodName", leaving the > shorter "executeMethod" - as name is sort of implied already anyway... > (though name is more accurate from a implementation detail POV, but who > cares about that here.) > > What do you think? > > Keith > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On Behalf Of > Steven Devijver > Sent: Saturday, April 02, 2005 12:55 PM > To: spr...@li... > Subject: [Springframework-developer] webflow: FormAction question > > Hi, > > I want to create a wizard that spans across multiple pages. I want to > bind to one and the same form instance across the different pages and > validate on every page submit. When the wizard completes I want this > one instance to contain all the information entered through the > various forms. > > Can I use FormAction for this purpose? > > Thanks > > Steven > > -- > "If you want to be a different fish, you gotta jump out of the school." > -- Captain Beefheart > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > -- "If you want to be a different fish, you gotta jump out of the school." -- Captain Beefheart |
|
From: Brian M. <br...@ap...> - 2005-04-02 21:35:38
|
snapshot of the classes as they are now: http://morphy.skife.org/spring-lucene/ -Brian On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: > I have a set of classes for Apache Lucene integration with Spring > (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which > are designed to > > a) make it easier to work with Lucene from Spring (the template in > particular optimizes common cases nicely, and does the resource > open/closing like the other templates) > > b) make lucene index modifications abide by Spring's transaction > system by doing write-behind on adds (which are ignored on rollback) > and rolling back deletes via a transaction synchronization. > > > > I'd like to contribute them to Spring (if ya'll are interested), but > to clean up the code and design some first, I have a few questions: > > 1) Should transaction binding be "on" by default? Lucene is > semi-transactional by nature (supports r and r/w locks, changes are > flushed on reader/writer closing, etc), but I am not sure people > expect Lucene to be bound by other transactions. Potential confusion. > > 2) What is a good tx manager to use for the unit tests? I am using a > modified version of the TestTransactionManager in Spring right now > (just changed to make it accessible and use synchonrizations). It is > much easier to use the TransactionTemplate than to manually manage the > tx's for tests =) > > 3) Not all of the ~interesting things you can do in lucene are > convenient to expose (splitting indexes etc) from the configuration. > Right now, rather than make a hack, the factory beans only support > single indexes. The only multi-index thing exposed right now is really > a configuration option on the SearcherBean which allows for multiple > indexes and a MultiSearcher ~transparently. > > Thanks! > > -Brian > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Brian M. <br...@ap...> - 2005-04-02 21:19:59
|
I have a set of classes for Apache Lucene integration with Spring (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which are designed to a) make it easier to work with Lucene from Spring (the template in particular optimizes common cases nicely, and does the resource open/closing like the other templates) b) make lucene index modifications abide by Spring's transaction system by doing write-behind on adds (which are ignored on rollback) and rolling back deletes via a transaction synchronization. I'd like to contribute them to Spring (if ya'll are interested), but to clean up the code and design some first, I have a few questions: 1) Should transaction binding be "on" by default? Lucene is semi-transactional by nature (supports r and r/w locks, changes are flushed on reader/writer closing, etc), but I am not sure people expect Lucene to be bound by other transactions. Potential confusion. 2) What is a good tx manager to use for the unit tests? I am using a modified version of the TestTransactionManager in Spring right now (just changed to make it accessible and use synchonrizations). It is much easier to use the TransactionTemplate than to manually manage the tx's for tests =) 3) Not all of the ~interesting things you can do in lucene are convenient to expose (splitting indexes etc) from the configuration. Right now, rather than make a hack, the factory beans only support single indexes. The only multi-index thing exposed right now is really a configuration option on the SearcherBean which allows for multiple indexes and a MultiSearcher ~transparently. Thanks! -Brian |
|
From: Keith D. <ke...@in...> - 2005-04-02 18:52:29
|
Update: Erwin and I are also seriously considering removing Multi-Action
entirely, in favor of the ActionState doing the method dispatch if
appropriate. This is arguably cleaner and more flexible, and forces no
special inheritance requirement on your "multi-action" implementation.
Regarding backwards compatibility here: existing Multi-Action
implementations should continue to work, with the following caveats:
1. You'll just need to remove the 'extends MultiAction' clause if we decide
to remove that class. Your "Event <method>(RequestContext context)" action
execute method implementations won't have to change.
2. If your MultiAction leverages the AbstractAction pre-execute and
post-execute template methods (which we find are rarely used), you'll need
to use Spring AOP to achieve that pre/post execution logic. At some point
we may add support for declarative pre/post execute method as additional
properties for the ActionStateAction (e.g. <action ...> <property
name="preExecuteMethod" value="..."/></action>)
So we're proposing three things:
1. Rename of 'executeMethodName' property to 'method'.
2. Promotion of 'method' to first-class 'action' element attribute.
3. Remove of MultiAction in favor of method-based dispatch in the
ActionState class.
Keith
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Keith Donald
Sent: Saturday, April 02, 2005 1:14 PM
To: 'Keith Donald'; spr...@li...
Subject: RE: [Springframework-developer] webflow: FormAction question
Now that I think about it just "method" might be even better, as 'execute'
is also implied (actions all execute, duh):
<action id="myFormAction" method="bindAndValidate"/>
Thoughts?
Keith
-----Original Message-----
From: Keith Donald [mailto:ke...@in...]
Sent: Saturday, April 02, 2005 1:11 PM
To: 'spr...@li...'
Subject: RE: [Springframework-developer] webflow: FormAction question
Hey Steven,
Be sure to use the 'users' list or forum for questions like this next time,
so more users will see it.
You can use one FormAction to do this, yep. Erwin will be checking in a
wizard sample shortly (potentially this evening), so I'll just sum up what
the sample will illustrate:
- The FormAction already has a 'bindAndValidate' method, that does what you
want on each intermediate page submit. So you can have that method called
on each submit by using a bindAndValidate<X> action state, where <X>
describes what it is you are binding and validating.
For example:
<action-state id="bindAndValidatePageFoo">
<action id="myFormAction">
<property name="executeMethodName" value="bindAndValidate"/>
</action>
<transition on="error" to="viewPageFoo"/>
<transition on="success" to="viewPageBar"/>
</action-state>
<action-state id="bindAndValidatePageBar">
<action id="myFormAction">
<property name="executeMethodName" value="bindAndValidate"/>
</action>
<transition on="error" to="viewPageBar"/>
<transition on="success" to="submit"/>
</action-state>
<action-state id="submit">
<action id="myFormAction">
<property name="executeMethodName" value="submit"/>
</action>
<transition on="error" to="error"/>
<transition on="success" to="end"/>
</action-state>
Keep in mind I've omitted the view states and end states here, (I also typed
this on-the-fly) but this should get you started.
Looking at the definition above, and given this need will be quite common,
it may be wise for us to make the 'executeMethodName' property a first class
citizen in the DTD. Erwin, what do you think? Others? For example:
<action id="myFormAction" executeMethod="submit"/>
That would shorten the above xml a good bit, to:
<action-state id="bindAndValidatePageFoo">
<action id="myFormAction" executeMethod="bindAndValidate"/>
<transition on="error" to="viewPageFoo"/>
<transition on="success" to="viewPageBar"/>
</action-state>
<action-state id="bindAndValidatePageBar">
<action id="myFormAction" executeMethod="bindAndValidate"/>
<transition on="error" to="viewPageBar"/>
<transition on="success" to="submit"/>
</action-state>
<action-state id="submit">
<action id="myFormAction" executeMethod="submit"/>
<transition on="error" to="error"/>
<transition on="success" to="end"/>
</action-state>
It may also be wise to drop "Name" from "executeMethodName", leaving the
shorter "executeMethod" - as name is sort of implied already anyway...
(though name is more accurate from a implementation detail POV, but who
cares about that here.)
What do you think?
Keith
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Steven Devijver
Sent: Saturday, April 02, 2005 12:55 PM
To: spr...@li...
Subject: [Springframework-developer] webflow: FormAction question
Hi,
I want to create a wizard that spans across multiple pages. I want to
bind to one and the same form instance across the different pages and
validate on every page submit. When the wizard completes I want this
one instance to contain all the information entered through the
various forms.
Can I use FormAction for this purpose?
Thanks
Steven
--
"If you want to be a different fish, you gotta jump out of the school."
-- Captain Beefheart
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Keith D. <ke...@in...> - 2005-04-02 18:14:33
|
Now that I think about it just "method" might be even better, as 'execute'
is also implied (actions all execute, duh):
<action id="myFormAction" method="bindAndValidate"/>
Thoughts?
Keith
-----Original Message-----
From: Keith Donald [mailto:ke...@in...]
Sent: Saturday, April 02, 2005 1:11 PM
To: 'spr...@li...'
Subject: RE: [Springframework-developer] webflow: FormAction question
Hey Steven,
Be sure to use the 'users' list or forum for questions like this next time,
so more users will see it.
You can use one FormAction to do this, yep. Erwin will be checking in a
wizard sample shortly (potentially this evening), so I'll just sum up what
the sample will illustrate:
- The FormAction already has a 'bindAndValidate' method, that does what you
want on each intermediate page submit. So you can have that method called
on each submit by using a bindAndValidate<X> action state, where <X>
describes what it is you are binding and validating.
For example:
<action-state id="bindAndValidatePageFoo">
<action id="myFormAction">
<property name="executeMethodName" value="bindAndValidate"/>
</action>
<transition on="error" to="viewPageFoo"/>
<transition on="success" to="viewPageBar"/>
</action-state>
<action-state id="bindAndValidatePageBar">
<action id="myFormAction">
<property name="executeMethodName" value="bindAndValidate"/>
</action>
<transition on="error" to="viewPageBar"/>
<transition on="success" to="submit"/>
</action-state>
<action-state id="submit">
<action id="myFormAction">
<property name="executeMethodName" value="submit"/>
</action>
<transition on="error" to="error"/>
<transition on="success" to="end"/>
</action-state>
Keep in mind I've omitted the view states and end states here, (I also typed
this on-the-fly) but this should get you started.
Looking at the definition above, and given this need will be quite common,
it may be wise for us to make the 'executeMethodName' property a first class
citizen in the DTD. Erwin, what do you think? Others? For example:
<action id="myFormAction" executeMethod="submit"/>
That would shorten the above xml a good bit, to:
<action-state id="bindAndValidatePageFoo">
<action id="myFormAction" executeMethod="bindAndValidate"/>
<transition on="error" to="viewPageFoo"/>
<transition on="success" to="viewPageBar"/>
</action-state>
<action-state id="bindAndValidatePageBar">
<action id="myFormAction" executeMethod="bindAndValidate"/>
<transition on="error" to="viewPageBar"/>
<transition on="success" to="submit"/>
</action-state>
<action-state id="submit">
<action id="myFormAction" executeMethod="submit"/>
<transition on="error" to="error"/>
<transition on="success" to="end"/>
</action-state>
It may also be wise to drop "Name" from "executeMethodName", leaving the
shorter "executeMethod" - as name is sort of implied already anyway...
(though name is more accurate from a implementation detail POV, but who
cares about that here.)
What do you think?
Keith
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Steven Devijver
Sent: Saturday, April 02, 2005 12:55 PM
To: spr...@li...
Subject: [Springframework-developer] webflow: FormAction question
Hi,
I want to create a wizard that spans across multiple pages. I want to
bind to one and the same form instance across the different pages and
validate on every page submit. When the wizard completes I want this
one instance to contain all the information entered through the
various forms.
Can I use FormAction for this purpose?
Thanks
Steven
--
"If you want to be a different fish, you gotta jump out of the school."
-- Captain Beefheart
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Keith D. <ke...@in...> - 2005-04-02 18:11:36
|
Hey Steven,
Be sure to use the 'users' list or forum for questions like this next time,
so more users will see it.
You can use one FormAction to do this, yep. Erwin will be checking in a
wizard sample shortly (potentially this evening), so I'll just sum up what
the sample will illustrate:
- The FormAction already has a 'bindAndValidate' method, that does what you
want on each intermediate page submit. So you can have that method called
on each submit by using a bindAndValidate<X> action state, where <X>
describes what it is you are binding and validating.
For example:
<action-state id="bindAndValidatePageFoo">
<action id="myFormAction">
<property name="executeMethodName" value="bindAndValidate"/>
</action>
<transition on="error" to="viewPageFoo"/>
<transition on="success" to="viewPageBar"/>
</action-state>
<action-state id="bindAndValidatePageBar">
<action id="myFormAction">
<property name="executeMethodName" value="bindAndValidate"/>
</action>
<transition on="error" to="viewPageBar"/>
<transition on="success" to="submit"/>
</action-state>
<action-state id="submit">
<action id="myFormAction">
<property name="executeMethodName" value="submit"/>
</action>
<transition on="error" to="error"/>
<transition on="success" to="end"/>
</action-state>
Keep in mind I've omitted the view states and end states here, (I also typed
this on-the-fly) but this should get you started.
Looking at the definition above, and given this need will be quite common,
it may be wise for us to make the 'executeMethodName' property a first class
citizen in the DTD. Erwin, what do you think? Others? For example:
<action id="myFormAction" executeMethod="submit"/>
That would shorten the above xml a good bit, to:
<action-state id="bindAndValidatePageFoo">
<action id="myFormAction" executeMethod="bindAndValidate"/>
<transition on="error" to="viewPageFoo"/>
<transition on="success" to="viewPageBar"/>
</action-state>
<action-state id="bindAndValidatePageBar">
<action id="myFormAction" executeMethod="bindAndValidate"/>
<transition on="error" to="viewPageBar"/>
<transition on="success" to="submit"/>
</action-state>
<action-state id="submit">
<action id="myFormAction" executeMethod="submit"/>
<transition on="error" to="error"/>
<transition on="success" to="end"/>
</action-state>
It may also be wise to drop "Name" from "executeMethodName", leaving the
shorter "executeMethod" - as name is sort of implied already anyway...
(though name is more accurate from a implementation detail POV, but who
cares about that here.)
What do you think?
Keith
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Steven Devijver
Sent: Saturday, April 02, 2005 12:55 PM
To: spr...@li...
Subject: [Springframework-developer] webflow: FormAction question
Hi,
I want to create a wizard that spans across multiple pages. I want to
bind to one and the same form instance across the different pages and
validate on every page submit. When the wizard completes I want this
one instance to contain all the information entered through the
various forms.
Can I use FormAction for this purpose?
Thanks
Steven
--
"If you want to be a different fish, you gotta jump out of the school."
-- Captain Beefheart
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
1239 messages has been excluded from this view by a project administrator.
