John, Let's take an example. A web service gets triggered and returns an atom feed. It is easy to create a fairly generic participant that can execute the service and return the data in the workitem.
So now we have an atom feed in the workitem. 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. 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. ActiveStoreParticpant could also provide a count function and an iterator... That's one way to skin that cat but I am not sure if it is the most user-friendly way yet. So I was probing for user experience in that area. Custom participants are not a real solution here I think as I twoudl require users to know Ruby and too much knowledge of OpenWFE internals. V/R, Pat. > From: John Mettraux <[EMAIL PROTECTED]> > Reply-To: <[email protected]> > Date: Sun, 30 Sep 2007 22:55:06 +0900 > To: <[email protected]> > Subject: [openwferu-dev] Re: DB Participant > > > Pat, > > On 9/30/07, Pat Cappelaere <[EMAIL PROTECTED]> wrote: >> >> It could be done in a custom participant but it could not be done by an end >> user at the graphical interface level. This is where I am going with this. >> I need more generic participants that can be generically wired or have the >> capability to transform/aggregate their outputs. > > As already said, CsvParticipants are available for that. The interface > is google docs, publishing as CSV and here we go. There is thus a > transformation description format (CSV) and a designing interface (a > spreadsheet). > > That said, if you want to have something more point-and-clicky, isn't > it in the scope of your Matelot project ? > > I find CSV adapted as a support for transformation descriptions, of > course nothing beats ruby custom participants (although CsvParticipant > understands embedded ruby snippets). > > What format / description type would you propose ? > > Such transformation participants testing can easily be automated. > > > Best regards, > > -- > John Mettraux -///- http://jmettraux.openwfe.org > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
