Re: Getting involved in werkflow
Edgar González <[email protected]> Fri, 23 May 2003 11:20:45 -0400
| Newsgroups | gmane.comp.java.werkflow |
|---|---|
| Message-ID | <00c001c3213e$e29d1460$46c8c8c8@PORT2000P01> |
This is a multi-part message in MIME format. ------=_NextPart_000_00BD_01C3211D.5A5CDF70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi David, Thanks for sharing your comments. I take a look at werkflow now, because I'm using OpenSymphony's = workflow, but I'm very disappointed with it (nice ideas, but unclear = RoadMap, no patrons, not OO, etc) :-( And I know the good work make it by Jason and Bob. :-) In addition, I'm exploring to move my applications from Turbine 2.2 to = Plexus+Summit, in order to be Avalonised. regards, Edgar ----- Original Message -----=20 From: David Wynter=20 To: [email protected]=20 Sent: Friday, May 23, 2003 4:14 AM Subject: RE: [werkflow-interest] Getting involved in werkflow Hi Edgar, I too have to do something like this, but must migrate from T2.1 = first. So I have had a look to see where werkflow is most actively being = used. That is as a part of Plexus, I think the brain child of Jason Van = Zyl. Now the point of this is that Plexus uses Summit which is = essentially a parallel to Turbine. Have a look at = http://cvs.werken.com/viewcvs.cgi/plexus-components/?cvsroot=3Dplexus = Note that werkflow is already a plexus component, also that all our = familiar friends (rundata, pull, resolver, parser, parameter, module) = are all under Summit. Also note that under = http://cvs.werken.com/viewcvs.cgi/fulcrum/?cvsroot=3Dplexus the db = package is actually a Avalon wrapper for Torque, because the Torque = developers haven't got there yet. This is very important to me as I have = a lot of investment in using Torque. Plexus components are all = Avalonised so have very clean service lifecycle management, actually = understandable now. So my conclusion is that I should save myself a lot of work in the = long run by switching directly to Plexus and I get 2 things, werkflow = already integrated and a service infrastructure I can actually = understand, and possibly a bunch of stuff I don't even know yet. Note = also that it provides support for the much better Quartz scheduler and = Axis amongst other things.=20 I suppose the big question is how 'ready' is it for consumption by = mere mortals ;-) I feel the risk is mitigated by the fact it is being = used by Zenplex in a production system (I think). rgds, David -----Original Message----- From: [email protected] = [mailto:[email protected]]On Behalf Of Edgar = Gonz=E1lez Sent: 22 May 2003 23:41 To: [email protected] Subject: [werkflow-interest] Getting involved in werkflow Hello, I would like to get involved in the werkflow project (development or = docs), because I need to integrate a workflow engine in several web = applications.=20 My web applications are based on Turbine 2.2 + Torque 3.0 The cvs change log shows a recent lot of work, unless the last = update for the project site was in 07 March 2003 and the most recent = version available in http://ibiblio.org/maven is 04-Feb-2003. - what is the project status? - which is the roadmap?=20 Thanks Edgar ------=_NextPart_000_00BD_01C3211D.5A5CDF70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi David,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks for sharing your = comments.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I take a look at werkflow now, because = I'm=20 using OpenSymphony's workflow, but I'm very disappointed with = it=20 (nice ideas, but unclear RoadMap, no patrons, not OO, etc) = :-(</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>And I know the good work make = it by Jason and=20 Bob. :-)</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>In addition, I'm exploring to move my = applications=20 from Turbine 2.2 to Plexus+Summit, in order to be = Avalonised.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>regards,</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Edgar</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV> <DIV=20 style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: = black"><B>From:</B>=20 <A [email protected] = href=3D"mailto:[email protected]">David=20 Wynter</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20 [email protected]=20 = href=3D"mailto:[email protected]">[email protected]= rken.com</A>=20 </DIV> <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, May 23, 2003 4:14 = AM</DIV> <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: = [werkflow-interest] Getting=20 involved in werkflow</DIV> <DIV><BR></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff size=3D2>Hi=20 Edgar,</FONT></SPAN></DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff size=3D2>I=20 too have to do something like this, but must migrate from T2.1 first. = So I=20 have had a look to see where werkflow is most actively being used. = That is as=20 a part of Plexus, I think the brain child of Jason Van Zyl. Now the = point of=20 this is that Plexus uses Summit which is essentially a parallel to = Turbine.=20 Have a look at <A=20 = href=3D"http://cvs.werken.com/viewcvs.cgi/plexus-components/?cvsroot=3Dpl= exus">http://cvs.werken.com/viewcvs.cgi/plexus-components/?cvsroot=3Dplex= us</A> Note=20 that werkflow is already a plexus component, also that all our = familiar=20 friends (rundata, pull, resolver, parser, parameter, module) are all = under=20 Summit. Also note that under <A=20 = href=3D"http://cvs.werken.com/viewcvs.cgi/fulcrum/?cvsroot=3Dplexus">http= ://cvs.werken.com/viewcvs.cgi/fulcrum/?cvsroot=3Dplexus</A> the=20 db package is actually a Avalon wrapper for Torque, because the Torque = developers haven't got there yet. This is very important to me as I = have a lot=20 of investment in using Torque. Plexus components are all Avalonised so = have=20 very clean service lifecycle management, actually understandable=20 now.</FONT></SPAN></DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff size=3D2>So=20 my conclusion is that I should save myself a lot of work in the = long run=20 by switching directly to Plexus and I get 2 things, werkflow already=20 integrated and a service infrastructure I can actually understand, and = possibly a bunch of stuff I don't even know yet. Note also that it = provides=20 support for the much better Quartz scheduler and Axis amongst other = things.=20 </FONT></SPAN></DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff size=3D2>I=20 suppose the big question is how 'ready' is it for consumption by mere = mortals=20 ;-) I feel the risk is mitigated by the fact it is being used by = Zenplex in a=20 production system (I think).</FONT></SPAN></DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff=20 size=3D2>rgds,</FONT></SPAN></DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D372544706-23052003><FONT face=3DArial = color=3D#0000ff=20 size=3D2>David</FONT></SPAN></DIV></FONT></DIV> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT = face=3DTahoma=20 size=3D2>-----Original Message-----<BR><B>From:</B>=20 [email protected]=20 [mailto:[email protected]]<B>On Behalf Of = </B>Edgar=20 Gonz=E1lez<BR><B>Sent:</B> 22 May 2003 23:41<BR><B>To:</B>=20 [email protected]<BR><B>Subject:</B> = [werkflow-interest]=20 Getting involved in werkflow<BR><BR></FONT></DIV> <DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I would like to get involved in the = werkflow=20 project (development or docs), because <FONT face=3DArial size=3D2>I = need to=20 integrate a workflow engine in several web applications.</FONT> = <DIV><FONT face=3DArial size=3D2></FONT> </DIV></FONT></DIV> <DIV><FONT face=3DArial size=3D2>My web applications are based = on Turbine=20 2.2 + Torque 3.0</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The cvs change log shows a recent = lot of work,=20 unless the last update for the project site was in <FONT=20 face=3D"Times New Roman" size=3D3>07 March 2003 and the most recent = version=20 available in <A = href=3D"http://ibiblio.org/maven">http://ibiblio.org/maven</A>=20 is 04-Feb-2003.</FONT></FONT></DIV> <DIV><FONT face=3DArial size=3D2><FONT face=3DArial=20 size=3D2></FONT></FONT> </DIV> <DIV>- what is the project status?</DIV> <DIV>- which is the roadmap? </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial=20 size=3D2>Edgar</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_00BD_01C3211D.5A5CDF70--