hi, i read the documentation regarding claim checks, i was wondering if it could be changed to a nonpersistent state?
i need to store sockets and i don't think i could serialize it. thanks carlo On Mon, May 31, 2010 at 4:00 PM, Carlo Camerino <[email protected]>wrote: > nice > > thanks a lot! > > > On Wed, May 26, 2010 at 4:58 PM, Claus Ibsen <[email protected]>wrote: > >> Hi >> >> Its a bit like the Claim Check EIP pattern. Eg you just impl. your own >> Registry to store the data, which you can retrieve again later. >> >> >> On Tue, May 25, 2010 at 4:08 PM, Carlo Camerino >> <[email protected]> wrote: >> > i think the proper term i'm looking for is >> > >> > java "continuations" >> > >> > On Tue, May 25, 2010 at 10:04 PM, Carlo Camerino >> > <[email protected]>wrote: >> > >> >> hi willem, >> >> >> >> sorry for the confusiuon here. >> >> um actually it's regardless of user interface. it maybe wicket or any >> other >> >> web framework. >> >> >> >> i'm planning on doing this in the integration side >> >> >> >> >> >> On Tue, May 25, 2010 at 9:34 PM, Willem Jiang <[email protected] >> >wrote: >> >> >> >>> Hi Carlo, >> >>> >> >>> I'm sure you post the mail to a wrong mailing list. >> >>> Maybe you are planing to ask the question in apache wicket user >> mailing >> >>> list. >> >>> >> >>> Willem >> >>> >> >>> Carlo Camerino wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> I have this requirement in which I need to save a state of execution. >> >>>> >> >>>> Here is my scenario: >> >>>> I need to get information coming from a remote computer. >> >>>> I am using a java Socket object in order to connect to this computer. >> >>>> Each time a reply returns I go back to the user interface screen and >> the >> >>>> thread is cut. >> >>>> >> >>>> For my requirement, however... I need to go back to that state of >> >>>> execution >> >>>> >> >>>> btw, i am implementing an application using apache wicket as the user >> >>>> interface. >> >>>> >> >>>> normal >> >>>> >> >>>> Open Socket --> Send Messge --> Wait For Reply --> Close Socket --> >> >>>> return >> >>>> to ui screen >> >>>> >> >>>> my scenario >> >>>> >> >>>> Open Socket --> Send Message --> Wait For Reply --> Store State Of >> >>>> Execution >> >>>> --> Go Back to UI Screen --> get inputs --> Get Back Stdate Of >> Execution >> >>>> --> >> >>>> Send Message -- Wait For Reply --> Close Socket --> Return to ui >> screen. >> >>>> >> >>>> Is there an enterprise integration pattern for this? One in which I >> can >> >>>> store an execution state and then go back to in a future time? >> >>>> >> >>>> btw, i can't close the socket, have to keep it open. >> >>>> >> >>>> thanks >> >>>> carlo >> >>>> >> >>>> >> >>> >> >> >> > >> >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Author of Camel in Action: http://www.manning.com/ibsen/ >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> > >
