Hi john,
John Mettraux ha escrito:
> 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.
Thank you, it's working now!. The weird thing is that I think I was
doing the same on friday (I'm on another machine now), I will check
that out tomorrow.
> > 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.
Well, I only used the LdapService class, and created a new PasswdCodec
based on XmlPasswdCodec, because I wanted to authenticate against an
ldap directory, so I just needed to uncomment LdapService from
engine-configuration.xml and worklist-configuration and set its
parameters (I modified LdapService to get user passwords).
On a different topic, I'd like to know if you found the solution to the
problem with owfe-suite.bat in windows 2000, because I think the CP
variable gets overwritten in the for loops. I found a bug report about
this, but you only mentioned the white space issue, and I don't have
any white space in the path. I will have to solve this problem in the
right way eventually, so, if you don't have the solution, I will
probably be able to send you the fix in the next days.
Thanks for your help,
Gustavo González
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
