Hi Nicolas, On 7/20/06, Nicolas Modrzyk <[EMAIL PROTECTED]> wrote: > > > Have you tried binding the core (bulk) of the process definition at > > the engine level from the library so that it's already in Expression > > form in the memory ? I mentioned that in one of my first replies. > > > I'm not sure I know how to deal with this... But that looks like > basic OpenWfe API usage right ? Do you have a link to the > documentation ?
The formal link would be : http://www.openwfe.org/docbook/build/ch12s07.html But that's oriented towards the 'standalone' OpenWFE, not the embedded one you're using. The workaround could be : 1). at engine startup launch a 'library' flow that contains core flows binding <process-definition name="//my-core-activation-flow"> ... </process-definition> 2). your activation flows become things like <process-definition name="my-activition-flow"> <my-core-activation-flow/> </process-definition> Whoah, that's not very elegant... Caching is way better. I'll have a look at it. Best regards, -- John Mettraux -///- http://jmettraux.openwfe.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ OpenWFE - Open source WorkFlow Engine OpenWFE-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openwfe-users
