Yes, Ajax calls are HTTP requests, so they pass along session
identifier cookies in the same manner as any other request.
So, just to clarify exactly what is failing, this event executes a
controller function that sets a session variable, and then adds a
"result" value to the event (presumably the value of true indicates
success), is that correct? And if it is, neither of these actions is
performed, right? (In other words, the function is not executing at
all, and this isn't just a problem with the return value not being
present.)
If your controller function isn't executing, then I can think of a
couple of likely reasons:
1. An exception is occurring, and is being caught by the MG error
handling event.
To see whether this is happening, you could add a message broadcast to
the error event for a message-listener function that dumps the
exception information to a file, using something like this:
<cfdump var="#arguments.event.getValue("exception")#" format="text"
output="/path/to/dump/file" />
(I understand that you verified that the event worked as expected
outside the context of a remote request, but it is still possible that
the remote request is throwing an error for some reason, so it's
probably worth confirming that this is not the case.)
2. The change to the AbstractRemotingService is causing an interaction
in your application that is causing the request to fail.
More specifically, the difference here is the fact that unlike the
methodology used in MG 3.0, the full MG event lifecycle is now
executed for a remoting request. This means that there is a
possibility that an onRequestStart function, for example, could be
doing something that causes the remoting request to fail, which would
not have been the case in the 3.0 version.
Hopefully some of this is helpful in trying to troubleshoot the problem.
--
Ezra Parker
On Wed, Dec 15, 2010 at 1:11 PM, olivierb <[email protected]> wrote:
> I tried accessing the event directly through a page instead of through
> the remoting request and my event works.
>
> Does the RemotingService keep the same session? All the event does is
> add some information to a session variable.
>
> Olivier
>
> --
> Model-Glue Sites:
> Home Page: http://www.model-glue.com
> Documentation: http://docs.model-glue.com
> Bug Tracker: http://bugs.model-glue.com
> Blog: http://www.model-glue.com/blog
>
> You received this message because you are subscribed to the Google
> Groups "model-glue" group.
> 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/model-glue?hl=en
>
--
Model-Glue Sites:
Home Page: http://www.model-glue.com
Documentation: http://docs.model-glue.com
Bug Tracker: http://bugs.model-glue.com
Blog: http://www.model-glue.com/blog
You received this message because you are subscribed to the Google
Groups "model-glue" group.
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/model-glue?hl=en
