Hi Andrea, 2007/3/13, miden2ena <[EMAIL PROTECTED]>: > > > hi , i have the following problem ... > i'm using openwfe rmi interface to comunicate beetwen my webapp and openwfe > engine ... > when i call (rmi)workSession.launch(store,launchitem) i need that the method > launch doesn't come back until > the new workitem is really in the store... > if i launch a workitem and then read the headers of the store it's not > there, but if i do read 2sec later it's ok ... > > please help me, i've seen that engine.launch() has a bool parameter that > allows setting an async callback, how can i do the similar thing for > rmiworksession?
The 2 second wait workaround is already a good thing. There would be another solution : step back and take a look at your process definitions, if you need the launch to be so tightly integrated with the first participant (that points to a workitem store), then maybe you can merge the the "steps" and make sure the launchitem is properly editable from your application and then discard the first participant. You could also modify the source and make sure that the launch operation is called synchronously. Best regards, -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFE users" 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/openwfe-users?hl=en -~----------~----~----~----~------~----~------~--~---
