Hi Gustavo,
On 12/17/06, Gustavo González <[EMAIL PROTECTED]> wrote:
>
> I hadn't tried with a "file:" url, that does work, but I need another
> solution, because later we will need to load the workflow definition
> from an xml db, that's why I was testing and loading the definition as
> a string from a file, and then doing as the embedded example:
>
> li.getAttributes().puts("__definition__", flowDef);
> workSession.launch("mainEngine", li);
>
> but I guess that doesn't work in openwfe stand-alone, because I get an
> OpenWfeException.
I work hard to make any thrown exception meaningful, but I guess it
just complains about a missing process definition.
> Is there a way to launch a workflow with the definition being already
> in memory? (maybe a String, jdom Document, etc). If there isn't, maybe
> you can tell me what I should do to patch the engine and make that
> work.
Before launching your 'LaunchItem' do that with it :
li.setWorkflowDefinitionUrl("field:__definition__");
I can't find anywhere where I documented that, I'll have to do it.
It's within the embedded engine and not much used for the stand-alone
one.
The next problem you might run into is a permission one, but that
might be solved by adding a LaunchPermission entry to
etc/worklist/passwd.xml if that ever occurs.
> btw, I tried LdapService some days ago and it works perfectly.
Maybe you have some time to write some lines on how to set it up,
that'd be great.
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
-~----------~----~----~----~------~----~------~--~---
