> From: John Mettraux <[EMAIL PROTECTED]>
> Reply-To: <[email protected]>
> Date: Tue, 2 Oct 2007 10:06:12 +0900
> To: <[email protected]>
> Subject: [openwferu-dev] Re: DB Participant
>
>
> On 9/30/07, Pat Cappelaere <[EMAIL PROTECTED]> wrote:
>>
>> Next participant really wants a file name and time input (for instance). So
>> we need a transformer that can transform the workitem into a more
>> appropriate workitem for the next guy.
>
> Should we really care about the next guy ?
> Isn't it more appropriate to think about services struggling to
> transform their input into something usable ?
> Let's fight on 1 front.
My workflows are really for external web services orchestration so this is
quite critical for my application. Front 1 and 2 are actually similar (see
next)
>> This would call for an XSLT
>> participant, I guess. It would take an XSLT file as an input parameter.
>> That's one easy idea but not very super user friendly (user needs to know
>> XSLT).
>>
>> In my case, I could have an ActiveStoreParticipant that outputs a record in
>> XML in workitem. This gets transformed by XSLTParticipant to accommodate
>> the next participant.
>
> Within the engine, workitems are just plain ruby instances, the
> 'attributes' is a hash. Would this generic XsltParticipant imply that
> all workitems are transferred as XML between participants (even
> between expressions) ?
Yes. The web services I deal with usually return XML. I just store the
results as is in the workitem. So the problem becomes an XSLT transform.
Not sure if it is better yet.
Regards,
Pat.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenWFEru dev" 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/openwferu-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
