On 11/14/06, Boris Kraft <[EMAIL PROTECTED]> wrote:
>
> John Mettraux wrote:
> >
> > Hi Boris,
> >
> > the analysis seems fine.
> >
> > 1). is only this 'translate' subprocess concerned ? Are other missing
> > subprocesses causing this "preapply failed" ?
>
> no, it looks as if many or all subprocess definitions are affected
>
> > > 2). is the "translate" string used as a variable name in some other
> > flow ? (i.e. could the translate variable get unbound at engine level
> > due to something like <unset variable="//translate" />, just an
> > hypothesis).

Hi Boris,

I had a look at your root environment (the XML file you sent to me)
and I found the translate in it.

I would suggest a small test :

1). stop the suite
2). comment out the library loading component (out of
etc/engine/engine-configuration.xml)
3). make sure by yourself that the "//translate" command (and others)
is (are) present in the engine env .xml
4). restart the engine
5). launch a flow to see if translate & co are found

Normally, the subprocesses have to be loaded from the pool (from the
engine environment).


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
-~----------~----~----~----~------~----~------~--~---

Reply via email to