ProcessAction - Scaffold package

Greetings, We are using ProcessAction and Access Layer. Our Access Layer Component throws SQLException. If exception is thrown , it should be caught by BaseAction but that is not happening in my case. It gives java.sql.SQLException: Could not process (--our error message from stored

ProcessAction - scaffold package

Greetings, Actually in the failure of one action mapping , i am forwarding to another action mapping which is not getting executed. (i.e if any sqlexception from component, it has to execute another action) Regards, Sen Greetings, We are using ProcessAction and Access Layer. Our Access Layer

Re: ProcessAction - Scaffold package

It's being caught and wrapped inside of a ResourceAction (which supports Exception chaining), as intended. -Ted. Senthivel U S wrote: Greetings, We are using ProcessAction and Access Layer. Our Access Layer Component throws SQLException. If exception is thrown , it should be caught by

Re: ProcessAction - Scaffold package

I just added response to the CheckOutcome signature and its friends, including exposeInScope(). Send me the changes that you make to get the cookies up and running and we'll get that up too. Thanks for bringing this up. It should have been there from the beginning =:0) -Ted. Senthivel U S

ProcessAction - Scaffold package

Greetings, The ProcessAction and ProcessResult were designed to understand the idea of storing something in a scope. Originally, these set to the equivalent of request, session, and application. If you like, we could also add a fourth scope that would be the equivalent of a cookie (or maybe

ProcessAction - Scaffold package

Greetings, We are planning to use Scaffold package (ProcessAction and AccessLayer). In the ProcessAction, sometimes we want to get some user data from database and set it in cookie. For another request we want to read it from cookie and merge it with the form bean and send the bean for process.

Re: ProcessAction - Scaffold package

The ProcessAction and ProcessResult were designed to understand the idea of storing something in a scope. Originally, these set to the equivalent of request, session, and application. If you like, we could also add a fourth scope that would be the equivalent of a cookie (or maybe client)