We have run into a problem related to a pattern that our company has established with regards to handling json events. We have a pattern something like this ...
<request-map uri="doStuff"> <event type="jsonservice" invoke="doCoolStuff" /> <response name="success" type="request" value="doRelatedCoolStuff" /> </request-map> The trouble is with the nature of the json event -- it wraps up the results from the service/event that is called and streams that back in the response. The browser gets the JSON result from doCoolStuff and then has the opportunity to perform another operation before "doRelatedCoolStuff" has completed. Naturally there is an easy fix to ensure that the second request's logic is properly contained in "doCoolStuff"; what I am wondering is if there is something we can do from a infrastructure perspective that would prevent people from establishing this pattern in the future. I wonder if there are any situations where you would want the response to an initial JSON request to be anything other than of type "none"? -- View this message in context: http://www.nabble.com/Standard-practice-for-a-controller%27s-json-event-tp24631007p24631007.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
