perl-workflow-devel Mailing List for Perl Workflow (Page 8)
Brought to you by:
jonasbn
Menu
▾
▴
perl-workflow-devel — discussion list for developers of Perl Workflow
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(12) |
Feb
|
Mar
(4) |
Apr
|
May
(1) |
Jun
(11) |
Jul
(10) |
Aug
(7) |
Sep
(16) |
Oct
(2) |
Nov
(4) |
Dec
(11) |
| 2008 |
Jan
(1) |
Feb
(1) |
Mar
(9) |
Apr
(19) |
May
(3) |
Jun
(4) |
Jul
|
Aug
(8) |
Sep
(1) |
Oct
(6) |
Nov
(13) |
Dec
(17) |
| 2009 |
Jan
(5) |
Feb
(2) |
Mar
(3) |
Apr
(17) |
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
(14) |
Oct
(2) |
Nov
|
Dec
(13) |
| 2010 |
Jan
(6) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(4) |
Sep
(3) |
Oct
|
Nov
(10) |
Dec
|
| 2011 |
Jan
(8) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(6) |
Nov
(7) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(4) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jonas B. N. <jo...@gm...> - 2008-08-18 10:00:49
|
Hello All, The latest release has resulted in plenty of failure reports, I am have located the bug (in a test) and I will fix is ASAP. http://cpantesters.perl.org/show/Workflow.html#Workflow-0.32_3 Just so you do not dispair, take care, jonasbn |
|
From: Jonas B. N. <jo...@gm...> - 2008-08-16 19:37:53
|
Hello All, We have received two bug reports via http://rt.cpan.org/ on Workflow from Robert Stockdale. One was a simple bug (http://rt.cpan.org/Ticket/Display.html?id=38023) blocking from the examination of the other so I fixed this rapidly and have now uploaded a release 0.32_3. The other one is a bit more interesting, the perliminary release lets Robert do some more investigation, but you are of course welcome to have a look also: http://rt.cpan.org/Ticket/Display.html?id=38024 From Robert: -- It looks like conditions specified with a 'test' attribute instead of a 'name' attribute are cached with the name 'evaluate' regardless of the test being performed so if more than one of these conditions exists at a particular state the cached value will always be used. This is a major problem when using autorun states where one condition is the negation of another. Unfortunately I have not yet been able to verify this because of the other bug I just submitted. -- Hope you all had a nice summer - I know I did, jonasbn |
|
From: Jonas B. N. <jo...@gm...> - 2008-06-28 06:37:10
|
Hello All, I have set up Workflow in Ohloh this morning. The project is listed as perl-Workflow as in Sourceforge, Ohloh reported that the Workflow name was occupied. http://www.ohloh.net/projects/perl-Workflow The code analysis report I hope will become available shortly. Ohloh tells me the report is done, but nothing has appeared yet. jonasbn On 28/06/2008, at 03.48, Jim Brandt wrote: > Seems like a good idea to me. A while back someone posted to > use.perl (I think) encouraging CPAN authors to register. > > Jim > > Jonas Brømsø Nielsen wrote: >> Hi All, >> I am considering registering Workflow with Ohloh in an attempt to >> evaluate it and get some more exposure, any thoughts on this? >> http://www.ohloh.net/ >> jonasbn >> -- >> pauseid: JONASBN >> email: jo...@cp... >> blog: http://use.perl.org/~jonasbn/journal/ >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Perl-workflow-devel mailing list >> Per...@li... >> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel > > -- > Jim Brandt > Administrative Computing Services > University at Buffalo > |
|
From: Jonas B. N. <jo...@gm...> - 2008-06-28 06:33:36
|
Hello, I have examined the failure report some more and I have come to the conclusion that the problem is with XML::SAX. http://www.nntp.perl.org/group/perl.cpan.testers/2008/04/msg1370740.html It seems the cpan-tester reporting the failure is using XML::Simple 2.18 and we require version 2.00 so this is not the direct problem. XML::Simple however utilizes XML::SAX or XML::Parser internally and we do not know how the actual cpan-testers XML::Simple is configured - if I can find the time I might do some regression testing with XML::SAX, but since this is not the easiest to set up it make take some time before we can address this report. I do however think that we can conclude that the problem is not in Workflow and we can commence with the release of 0.32. Any thoughts or comments on this? jonasbn On 20/05/2008, at 13.39, Jonas Brømsø Nielsen wrote: > Hi Jim, > > Looking at the number of successful tests I assume this is a cpan- > tester problem. Not that we should not take it seriously. Anyhow I > have not come closer to a conclusion yet. > > jonasbn > > On 19/05/2008, at 17.15, Jim Brandt wrote: > >> >> Jonas Brømsø Nielsen wrote: >>> Hello All, >>> Have anybody had the time to evaluate the latest development >>> release 0.32_2? >> >> We're now running in production with it and have processed >> thousands of transactions for hundreds of incidents (workflows) and >> we haven't yet seen any problems in the engine itself. >> >>> We have a failing test reported from cpan-testers, I expect to >>> have a look at it later today. >> >> If it's one of the one's I added and I can help, let me know. >> >> Jim >> >>> If anybody else can spot the problem please let me know. >>> jonasbn >>> -- >>> pauseid: JONASBN >>> email: jo...@cp... >>> blog: http://use.perl.org/~jonasbn/journal/ >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft Defy all challenges. >>> Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Perl-workflow-devel mailing list >>> Per...@li... >>> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel >> >> -- >> Jim Brandt >> Administrative Computing Services >> University at Buffalo >> > |
|
From: Jim B. <cb...@bu...> - 2008-06-28 01:48:53
|
Seems like a good idea to me. A while back someone posted to use.perl (I think) encouraging CPAN authors to register. Jim Jonas Brømsø Nielsen wrote: > Hi All, > > I am considering registering Workflow with Ohloh in an attempt to > evaluate it and get some more exposure, any thoughts on this? > > http://www.ohloh.net/ > > jonasbn > -- > pauseid: JONASBN > email: jo...@cp... > blog: http://use.perl.org/~jonasbn/journal/ > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Perl-workflow-devel mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel -- Jim Brandt Administrative Computing Services University at Buffalo |
|
From: Jonas B. N. <jo...@gm...> - 2008-06-27 07:21:51
|
Hi All, I am considering registering Workflow with Ohloh in an attempt to evaluate it and get some more exposure, any thoughts on this? http://www.ohloh.net/ jonasbn -- pauseid: JONASBN email: jo...@cp... blog: http://use.perl.org/~jonasbn/journal/ |
|
From: Jonas B. N. <jo...@gm...> - 2008-05-20 11:39:34
|
Hi Jim, Looking at the number of successful tests I assume this is a cpan- tester problem. Not that we should not take it seriously. Anyhow I have not come closer to a conclusion yet. jonasbn On 19/05/2008, at 17.15, Jim Brandt wrote: > > Jonas Brømsø Nielsen wrote: >> Hello All, >> Have anybody had the time to evaluate the latest development >> release 0.32_2? > > We're now running in production with it and have processed thousands > of transactions for hundreds of incidents (workflows) and we haven't > yet seen any problems in the engine itself. > >> We have a failing test reported from cpan-testers, I expect to have >> a look at it later today. > > If it's one of the one's I added and I can help, let me know. > > Jim > >> If anybody else can spot the problem please let me know. >> jonasbn >> -- >> pauseid: JONASBN >> email: jo...@cp... >> blog: http://use.perl.org/~jonasbn/journal/ >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft Defy all challenges. >> Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Perl-workflow-devel mailing list >> Per...@li... >> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel > > -- > Jim Brandt > Administrative Computing Services > University at Buffalo > |
|
From: Jim B. <cb...@bu...> - 2008-05-19 15:16:10
|
Jonas Brømsø Nielsen wrote: > Hello All, > > Have anybody had the time to evaluate the latest development release > 0.32_2? We're now running in production with it and have processed thousands of transactions for hundreds of incidents (workflows) and we haven't yet seen any problems in the engine itself. > > We have a failing test reported from cpan-testers, I expect to have a > look at it later today. If it's one of the one's I added and I can help, let me know. Jim > > If anybody else can spot the problem please let me know. > > jonasbn > -- > pauseid: JONASBN > email: jo...@cp... > blog: http://use.perl.org/~jonasbn/journal/ > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Perl-workflow-devel mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel -- Jim Brandt Administrative Computing Services University at Buffalo |
|
From: Jonas B. N. <jo...@gm...> - 2008-05-19 06:00:09
|
Hello All, Have anybody had the time to evaluate the latest development release 0.32_2? We have a failing test reported from cpan-testers, I expect to have a look at it later today. If anybody else can spot the problem please let me know. jonasbn -- pauseid: JONASBN email: jo...@cp... blog: http://use.perl.org/~jonasbn/journal/ |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-22 20:29:02
|
Hello All, I have initiated a migration of all the web page stuff I created into a Wiki, hosted by SourceForge, I am far from done, but you are welcome to have a look at: http://perl-workflow.wiki.sourceforge.net/ This makes it easier to maintain and structurize, if any of you are interested in participating or you have feedback, please let me know. Take care, jonasbn -- pauseid: JONASBN email: jo...@cp... blog: http://use.perl.org/~jonasbn/journal/ |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-22 20:14:46
|
Hello All, I have just uploaded developer release 0.32_2 to CPAN. This release holds Jim Brandts implementation of transactionional control of the persisters. Please test it out if you have the time. Thanks to Jim for yet another important contribution. Comments, feedback, patches welcome, jonasbn -- pauseid: JONASBN email: jo...@cp... blog: http://use.perl.org/~jonasbn/journal/ |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-19 18:04:24
|
Hi Jim, Sounds fantastic, I will create a new development release. Again, thanks for yet another contribution to our little project. jonasbn On 18/04/2008, at 20.44, Jim Brandt wrote: > Jonas, > > You can go ahead. Our initial application tests are passing, so it > looks good so far with our application. > > Thanks, > Jim > > Jonas Brømsø Nielsen wrote: >> Hi Jim, >> Sounds good, tomorrow is a holiday day here and then it is weekend, >> so I could get a release out any time. >> Just let me know when you are ready, I will checkout your branch >> and run the tests. If I see anything out of the normal I will get >> back to you. >> jonasbn >> On 17/04/2008, at 20.48, Jim Brandt wrote: >>> >>> >>> Jonas Brømsø Nielsen wrote: >>>> Good job Jim, >>>> Do you want me to make a release? >>> >>> Give me a day to kick it around our dev environment and I'll >>> report back. Then we could go ahead. >>> >>>> jonasbn >>>> Sent from my iPhone >>>> On 17/04/2008, at 15.59, Jim Brandt <cb...@bu...> wrote: >>>>> >>>>> I've got a beta version of the transaction (autocommit off) >>>>> feature >>>>> checked into the branch I've been working with. As with the other >>>>> changes, the hardest part was building valid tests. >>>>> >>>>> When it came to the coding, it wasn't too bad as there was a >>>>> comment in >>>>> the code to the effect, "we should add a commit or rollback here >>>>> to >>>>> implement transactions." That was quite helpful in deciding >>>>> where to put >>>>> the commit and rollback calls. :) >>>>> >>>>> The new branch is here: >>>>> >>>>> http://perl-workflow.svn.sourceforge.net/viewvc/perl-workflow/branches/autocommit/ >>>>> >>>>> Test if you get a chance. All tests are passing for me. >>>>> >>>>> One note: it appears the sample ticket app in eg/ was broken. I >>>>> think I >>>>> fixed it, but I didn't test much. If you have some time, it >>>>> would be >>>>> great if someone could try to get that sample ticket app up and >>>>> running. >>>>> >>>>> My next step is to put the newest version in our dev environment >>>>> and see >>>>> if it works with our real workflow application. >>>>> >>>>> Jim >>>>> >>>>> -- >>>>> Jim Brandt >>>>> Administrative Computing Services >>>>> University at Buffalo >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------- >>>>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>>>> Don't miss this year's exciting event. There's still time to >>>>> save $100. >>>>> Use priority code J8TL2D2. >>>>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >>>>> _______________________________________________ >>>>> Perl-workflow-devel mailing list >>>>> Per...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel >>> >>> -- >>> Jim Brandt >>> Administrative Computing Services >>> University at Buffalo >>> > > -- > Jim Brandt > Administrative Computing Services > University at Buffalo > |
|
From: Jim B. <cb...@bu...> - 2008-04-18 18:44:36
|
Jonas, You can go ahead. Our initial application tests are passing, so it looks good so far with our application. Thanks, Jim Jonas Brømsø Nielsen wrote: > Hi Jim, > > Sounds good, tomorrow is a holiday day here and then it is weekend, so I > could get a release out any time. > > Just let me know when you are ready, I will checkout your branch and run > the tests. If I see anything out of the normal I will get back to you. > > jonasbn > > On 17/04/2008, at 20.48, Jim Brandt wrote: > >> >> >> Jonas Brømsø Nielsen wrote: >>> Good job Jim, >>> Do you want me to make a release? >> >> Give me a day to kick it around our dev environment and I'll report >> back. Then we could go ahead. >> >>> jonasbn >>> Sent from my iPhone >>> On 17/04/2008, at 15.59, Jim Brandt <cb...@bu...> wrote: >>>> >>>> I've got a beta version of the transaction (autocommit off) feature >>>> checked into the branch I've been working with. As with the other >>>> changes, the hardest part was building valid tests. >>>> >>>> When it came to the coding, it wasn't too bad as there was a comment in >>>> the code to the effect, "we should add a commit or rollback here to >>>> implement transactions." That was quite helpful in deciding where to >>>> put >>>> the commit and rollback calls. :) >>>> >>>> The new branch is here: >>>> >>>> http://perl-workflow.svn.sourceforge.net/viewvc/perl-workflow/branches/autocommit/ >>>> >>>> >>>> Test if you get a chance. All tests are passing for me. >>>> >>>> One note: it appears the sample ticket app in eg/ was broken. I think I >>>> fixed it, but I didn't test much. If you have some time, it would be >>>> great if someone could try to get that sample ticket app up and >>>> running. >>>> >>>> My next step is to put the newest version in our dev environment and >>>> see >>>> if it works with our real workflow application. >>>> >>>> Jim >>>> >>>> -- >>>> Jim Brandt >>>> Administrative Computing Services >>>> University at Buffalo >>>> >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> >>>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>>> Don't miss this year's exciting event. There's still time to save $100. >>>> Use priority code J8TL2D2. >>>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >>>> >>>> _______________________________________________ >>>> Perl-workflow-devel mailing list >>>> Per...@li... >>>> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel >> >> -- >> Jim Brandt >> Administrative Computing Services >> University at Buffalo >> > -- Jim Brandt Administrative Computing Services University at Buffalo |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-17 19:04:52
|
Hi Jim, Sounds good, tomorrow is a holiday day here and then it is weekend, so I could get a release out any time. Just let me know when you are ready, I will checkout your branch and run the tests. If I see anything out of the normal I will get back to you. jonasbn On 17/04/2008, at 20.48, Jim Brandt wrote: > > > Jonas Brømsø Nielsen wrote: >> Good job Jim, >> Do you want me to make a release? > > Give me a day to kick it around our dev environment and I'll report > back. Then we could go ahead. > >> jonasbn >> Sent from my iPhone >> On 17/04/2008, at 15.59, Jim Brandt <cb...@bu...> wrote: >>> >>> I've got a beta version of the transaction (autocommit off) feature >>> checked into the branch I've been working with. As with the other >>> changes, the hardest part was building valid tests. >>> >>> When it came to the coding, it wasn't too bad as there was a >>> comment in >>> the code to the effect, "we should add a commit or rollback here to >>> implement transactions." That was quite helpful in deciding where >>> to put >>> the commit and rollback calls. :) >>> >>> The new branch is here: >>> >>> http://perl-workflow.svn.sourceforge.net/viewvc/perl-workflow/branches/autocommit/ >>> >>> Test if you get a chance. All tests are passing for me. >>> >>> One note: it appears the sample ticket app in eg/ was broken. I >>> think I >>> fixed it, but I didn't test much. If you have some time, it would be >>> great if someone could try to get that sample ticket app up and >>> running. >>> >>> My next step is to put the newest version in our dev environment >>> and see >>> if it works with our real workflow application. >>> >>> Jim >>> >>> -- >>> Jim Brandt >>> Administrative Computing Services >>> University at Buffalo >>> >>> >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>> Don't miss this year's exciting event. There's still time to save >>> $100. >>> Use priority code J8TL2D2. >>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >>> _______________________________________________ >>> Perl-workflow-devel mailing list >>> Per...@li... >>> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel > > -- > Jim Brandt > Administrative Computing Services > University at Buffalo > |
|
From: Jim B. <cb...@bu...> - 2008-04-17 18:48:29
|
Jonas Brømsø Nielsen wrote: > Good job Jim, > > Do you want me to make a release? Give me a day to kick it around our dev environment and I'll report back. Then we could go ahead. > > jonasbn > > Sent from my iPhone > > On 17/04/2008, at 15.59, Jim Brandt <cb...@bu...> wrote: > >> >> I've got a beta version of the transaction (autocommit off) feature >> checked into the branch I've been working with. As with the other >> changes, the hardest part was building valid tests. >> >> When it came to the coding, it wasn't too bad as there was a comment in >> the code to the effect, "we should add a commit or rollback here to >> implement transactions." That was quite helpful in deciding where to put >> the commit and rollback calls. :) >> >> The new branch is here: >> >> http://perl-workflow.svn.sourceforge.net/viewvc/perl-workflow/branches/autocommit/ >> >> >> Test if you get a chance. All tests are passing for me. >> >> One note: it appears the sample ticket app in eg/ was broken. I think I >> fixed it, but I didn't test much. If you have some time, it would be >> great if someone could try to get that sample ticket app up and running. >> >> My next step is to put the newest version in our dev environment and see >> if it works with our real workflow application. >> >> Jim >> >> -- >> Jim Brandt >> Administrative Computing Services >> University at Buffalo >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save $100. >> Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> >> _______________________________________________ >> Perl-workflow-devel mailing list >> Per...@li... >> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel -- Jim Brandt Administrative Computing Services University at Buffalo |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-17 16:57:48
|
Good job Jim, Do you want me to make a release? jonasbn Sent from my iPhone On 17/04/2008, at 15.59, Jim Brandt <cb...@bu...> wrote: > > I've got a beta version of the transaction (autocommit off) feature > checked into the branch I've been working with. As with the other > changes, the hardest part was building valid tests. > > When it came to the coding, it wasn't too bad as there was a comment > in > the code to the effect, "we should add a commit or rollback here to > implement transactions." That was quite helpful in deciding where to > put > the commit and rollback calls. :) > > The new branch is here: > > http://perl-workflow.svn.sourceforge.net/viewvc/perl-workflow/branches/autocommit/ > > Test if you get a chance. All tests are passing for me. > > One note: it appears the sample ticket app in eg/ was broken. I > think I > fixed it, but I didn't test much. If you have some time, it would be > great if someone could try to get that sample ticket app up and > running. > > My next step is to put the newest version in our dev environment and > see > if it works with our real workflow application. > > Jim > > -- > Jim Brandt > Administrative Computing Services > University at Buffalo > > > > --- > ---------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Perl-workflow-devel mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel |
|
From: Jim B. <cb...@bu...> - 2008-04-17 14:00:57
|
I've got a beta version of the transaction (autocommit off) feature checked into the branch I've been working with. As with the other changes, the hardest part was building valid tests. When it came to the coding, it wasn't too bad as there was a comment in the code to the effect, "we should add a commit or rollback here to implement transactions." That was quite helpful in deciding where to put the commit and rollback calls. :) The new branch is here: http://perl-workflow.svn.sourceforge.net/viewvc/perl-workflow/branches/autocommit/ Test if you get a chance. All tests are passing for me. One note: it appears the sample ticket app in eg/ was broken. I think I fixed it, but I didn't test much. If you have some time, it would be great if someone could try to get that sample ticket app up and running. My next step is to put the newest version in our dev environment and see if it works with our real workflow application. Jim -- Jim Brandt Administrative Computing Services University at Buffalo |
|
From: Jim B. <cb...@bu...> - 2008-04-08 16:57:01
|
Jonas Brømsø Nielsen wrote: > Hi Jim, > > There has been some problems with PAUSE, but it should be on > search.cpan.org by now. > > jonasbn > Now I see it. Latest Dev. Release. Very cool. Thanks, Jim > On 08/04/2008, at 16.09, Jim Brandt wrote: >> >> >> Jonas Brømsø Nielsen wrote: >>> Hi Jim, >>> A branch would be magnificent. >>> I am getting better and better at merging, I can almost do it with no >>> scew-ups. Anyway I need the practice. >>> The lastest release 0.32_1 (the developer release) could be the point >>> you use and we can perhaps create a 0.32_2 prior to 0.32. >> >> That sounds like a good approach. I'll start from 0.32_1. >> >> FYI, I can see the developer release in your directory: >> >> http://search.cpan.org/src/JONASBN/Workflow-0.32_1/ >> >> but search.cpan.org doesn't show it as a download option: >> >> http://search.cpan.org/~jonasbn/Workflow-0.31/ >> >> Is that by design? I was thinking it would show up in red or something >> as a developer release? >> >> Jim >> >> -- >> Jim Brandt >> Administrative Computing Services >> University at Buffalo >> > -- Jim Brandt Administrative Computing Services University at Buffalo |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-08 16:45:39
|
Hi Jim, There has been some problems with PAUSE, but it should be on search.cpan.org by now. jonasbn On 08/04/2008, at 16.09, Jim Brandt wrote: > > > Jonas Brømsø Nielsen wrote: >> Hi Jim, >> A branch would be magnificent. >> I am getting better and better at merging, I can almost do it with >> no scew-ups. Anyway I need the practice. >> The lastest release 0.32_1 (the developer release) could be the >> point you use and we can perhaps create a 0.32_2 prior to 0.32. > > That sounds like a good approach. I'll start from 0.32_1. > > FYI, I can see the developer release in your directory: > > http://search.cpan.org/src/JONASBN/Workflow-0.32_1/ > > but search.cpan.org doesn't show it as a download option: > > http://search.cpan.org/~jonasbn/Workflow-0.31/ > > Is that by design? I was thinking it would show up in red or > something as a developer release? > > Jim > > -- > Jim Brandt > Administrative Computing Services > University at Buffalo > |
|
From: Jim B. <cb...@bu...> - 2008-04-08 14:11:03
|
Jonas Brømsø Nielsen wrote: > Hi Jim, > > A branch would be magnificent. > > I am getting better and better at merging, I can almost do it with no > scew-ups. Anyway I need the practice. > > The lastest release 0.32_1 (the developer release) could be the point > you use and we can perhaps create a 0.32_2 prior to 0.32. That sounds like a good approach. I'll start from 0.32_1. FYI, I can see the developer release in your directory: http://search.cpan.org/src/JONASBN/Workflow-0.32_1/ but search.cpan.org doesn't show it as a download option: http://search.cpan.org/~jonasbn/Workflow-0.31/ Is that by design? I was thinking it would show up in red or something as a developer release? Jim -- Jim Brandt Administrative Computing Services University at Buffalo |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-07 20:45:46
|
Hi Jim,
A branch would be magnificent.
I am getting better and better at merging, I can almost do it with no
scew-ups. Anyway I need the practice.
The lastest release 0.32_1 (the developer release) could be the point
you use and we can perhaps create a 0.32_2 prior to 0.32.
Or if you think your contributions in 0.32_1 require more incubation,
your could branch from the 0.31 release, the latest official release
and we could merge this branch into 0.32_1 later on.
I am thinking/dreaming about getting started on some of our other
outstandings on the road map. But I find it hard to find the time with
my current workload - I would love to get one of my clients hooked on
workflow so I could get some paid time on Workflow.
From the road map file:
--
* Implement dynamically loading of workflows
* Implement versioning of workflows
There are several feature requests. These have not been inserted into
the road map yet.
Documentation is getting out of date, this need to be addressed as well.
--
So there should be enough to go around, plus some minor feature
requests/bugs that we need to get out of the way.
I would also like to consolidate all this information in the Wiki.
jonasbn
On 07/04/2008, at 21.39, Jim Brandt wrote:
>
> Jonas Brømsø Nielsen wrote:
>> Hmmm this might be the actual challenge, from my standpoint; the
>> workflow engine should keep it own state and transactions. But
>> getting this to balance with transactions in applications
>> utilizing Workflow, might be a question of discipline and can
>> prove - difficult.
>
> As far as how it 'should' work, I think the workflow app should
> commit when a single unit of work (a transaction, which may be
> multiple executes against the DB) is complete. This can be
> challenging since you need to then define what this means to workflow.
>
> In practice, it might not be too bad. I looked at the code a bit and
> all the inserts and updates are in the Persister/DBI module and most
> actions require just a few inserts updates. It might get tricky with
> an update to the main workflow table, an update to an optional
> extra_data table, and the insert of a few history items.
>
> It gets trickier when you think about a passed in DB handle. Without
> autocommit, the outside app might leave transactions pending. But I
> think this has to be the user's problem. We could insert a warning,
> or perhaps commit before we do anything. It would then be workflow's
> job to make sure there were no exit points where you could return
> the handle with a pending transaction.
>
> I'd be interested in trying out some options. Should I create a
> separate branch?
>
> Jim
>
> --
> Jim Brandt
> Administrative Computing Services
> University at Buffalo
>
|
|
From: Jim B. <cb...@bu...> - 2008-04-07 19:39:18
|
Jonas Brømsø Nielsen wrote: > > Hmmm this might be the actual challenge, from my standpoint; the > workflow engine should keep it own state and transactions. But getting > this to balance with transactions in applications utilizing Workflow, > might be a question of discipline and can prove - difficult. > As far as how it 'should' work, I think the workflow app should commit when a single unit of work (a transaction, which may be multiple executes against the DB) is complete. This can be challenging since you need to then define what this means to workflow. In practice, it might not be too bad. I looked at the code a bit and all the inserts and updates are in the Persister/DBI module and most actions require just a few inserts updates. It might get tricky with an update to the main workflow table, an update to an optional extra_data table, and the insert of a few history items. It gets trickier when you think about a passed in DB handle. Without autocommit, the outside app might leave transactions pending. But I think this has to be the user's problem. We could insert a warning, or perhaps commit before we do anything. It would then be workflow's job to make sure there were no exit points where you could return the handle with a pending transaction. I'd be interested in trying out some options. Should I create a separate branch? Jim -- Jim Brandt Administrative Computing Services University at Buffalo |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-07 07:12:04
|
On 06/04/2008, at 23.50, Andrew O'Brien wrote: > >> Hello all, > >> Workflow defaults to AutoCommit and I was wondering if there would be >> any interest in allowing this to be a passed in parameter. We could >> still allow AutoCommit to be set, but we could also put in manual >> commits at appropriate points in a transaction. This would result in >> some warnings from DBI whan you manually ran the commits (unless we >> shielded the commits with a test for AutoCommit). >> >> Any thoughts one way or the other? > > I certainly don't see any issue with allowing the AutoCommit setting > to > be overridden as long as the default remains the same so we don't > surprise too many people :) > > I know that we assume AutoCommit is on by default, for example. > > As long at the extra commits that are added into the Workflow codebase > are optionally executed depending on the AutoCommit setting then the > real question then becomes one of intent: > > Are you intending that Workflow still commits regularly internally > (which is what I think you're saying) or are you intending to never > call > commit in the Workflow codebase at all and leave that to the external > application? > Hmmm this might be the actual challenge, from my standpoint; the workflow engine should keep it own state and transactions. But getting this to balance with transactions in applications utilizing Workflow, might be a question of discipline and can prove - difficult. > Cheers, > > Andrew > jonasbn |
|
From: Andrew O'B. <an...@or...> - 2008-04-06 21:51:14
|
> Hello all, > Workflow defaults to AutoCommit and I was wondering if there would be > any interest in allowing this to be a passed in parameter. We could > still allow AutoCommit to be set, but we could also put in manual > commits at appropriate points in a transaction. This would result in > some warnings from DBI whan you manually ran the commits (unless we > shielded the commits with a test for AutoCommit). > > Any thoughts one way or the other? I certainly don't see any issue with allowing the AutoCommit setting to be overridden as long as the default remains the same so we don't surprise too many people :) I know that we assume AutoCommit is on by default, for example. As long at the extra commits that are added into the Workflow codebase are optionally executed depending on the AutoCommit setting then the real question then becomes one of intent: Are you intending that Workflow still commits regularly internally (which is what I think you're saying) or are you intending to never call commit in the Workflow codebase at all and leave that to the external application? Cheers, Andrew |
|
From: Jonas B. N. <jo...@gm...> - 2008-04-06 08:48:01
|
Hi Jim, Nice, this is included in the 0.32_1 developer release. I keep referring to this as alpha, developer release is of course the correct term. jonasbn On 29/02/2008, at 14.10, Jim Brandt wrote: > Hello all, > > We wanted to be able to set a local timezone for all dates for > workflow > and it currently defaults to GMT, so I added an option for the main > workflow.xml file to allow you to pass in a time_zone. The valid > values > are the timezones you can pass to a DateTime object. > > If anyone wants to test, I'm working in this branch: > > http://perl-workflow.svn.sourceforge.net/viewvc/perl-workflow/branches/config_types/ > > Currently all of the workflow tests pass for me and I'll be testing > with > our workflow application in development in the next week or so. > > Thanks, > Jim > > -- > Jim Brandt > Administrative Computing Services > University at Buffalo > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Perl-workflow-devel mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel |
