FYI, we still have to save the persist data in the session or
application scope -- that is the redirectPersistScope property. If you
want to store the persist id in a cookie instead of passing that in the
URL (which is required for persist to work with routes), you need to set
the "redirectPersistParameterLocation" property and set the value to
"cookie" (it defaults to url if you don't have this property set in your
config):
http://trac.mach-ii.com/machii/wiki/URLManagementFeatures#PropertiesThatAffectTheRedirectCommand
I'll look into the other thing you mentioned. Can you confirm what
version of Mach-II you are using? Look at the README file for the
complete version number (it should read something like 1.8.0.1947 [which
is a BER] or 1.8.0.8 [which is a stable version]).
.pjf
Po said the following on 29/06/10 16:02:
The strange thing is that this was all working with regular urls (not
routes).
But regardless, if I do<property name="redirectPersistScope"
value="cookie" />,
I get the following error:
The redirect persist feature cannot access the session scope because
it has not been enabled in your application.
The sesion scope is used by default, however it is configurable if you
have disabled the session scope in your application. Add (or change if
already defined) the 'redirectPersistScope' property to your XML
configuration file with a value of 'application' or 'server.'
We have been using the session scope with this app with no problem, so
I am not sure to what this is referring.
As far as the regular args attribute is concerned, if I do<redirect
event="validateAddress" args="address_id,step,nextRoute,editRoute" />,
it works fine. As soon as I change it from event to route, and
specify the corresponding created route as follows:
<redirect route="validate" args="address_id,step,nextRoute,editRoute" /
, it stops working. The event parameters do not even show up in the
URL.
I am using the rewriteConfigFile built in to the framework to setup
the rewrite rules.
Please let me know if I am doing something wrong or if this is a
possible bug.
On Jun 29, 1:32 pm, Kurt Wiersma<[email protected]> wrote:
For the persistArgs to work you need to specify the persistArgs
storage property to be "cookie" instead of the default of session. I
think from our team Mach II test app that args should be working with
routes. Can you post an example of how you have it configured and how
you are calling the redirect?
--Kurt
On Tue, Jun 29, 2010 at 10:29 AM, Po<[email protected]> wrote:
It seems that when I am using a route and try to also use the args
attribute/paremeter (either in the command or method), it just does
not work. I believe the same issue is happening with persistArgs, but
have not tested enough to be 100% sure.
Any ideas?
Thank you.
--
You received this message because you are subscribed to Mach-II for CFML list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group
athttp://groups.google.com/group/mach-ii-for-coldfusion?hl=en
***New URLs as of April 29th, 2010***
SVN:http://svn.mach-ii.com/machii/
Wiki / Documentation / Tickets:http://trac.mach-ii.com/machii/
--
You received this message because you are subscribed to Mach-II for CFML list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
***New URLs as of April 29th, 2010***
SVN: http://svn.mach-ii.com/machii/
Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
