i'm retesting it with ruote 2.0 and Fsparticipant instead

On 23 août, 14:32, lanfeust21 <[email protected]> wrote:
> Well in  the version 2.0 that i plan to use there is no
> YamlParticipant , just a DM one ! (if i can use DM  and AR in // i can
> use it)
>
> i was even able to store a workitem and without that i cannot use it
>
> so i add to switch back !!
>
> By the way on you last commit (2.0), the patch you've done for the nil
> compatibility , you have to switch
> the '&&' condition by the 'and' otherwise it will not run on ruby
> 1.8.7
>
> when i set a condition like "${f:match_profile_status} == yes"
> if a put a space after yes the pattern does not strip it
>
> On 23 août, 14:21, John Mettraux <[email protected]> wrote:
>
> > On Sun, Aug 23, 2009 at 9:15 PM, lanfeust21<[email protected]> wrote:
>
> > > usefull from line 88 before that the singlecon was closing de
> > > connection each time :(
>
> > OK,
>
> > may I ask why you're switching from 2.0 to 0.9.21 ?
>
> > The singlecon stuff is the result of the pure nightmare that
> > activerecord put me into a while back. I hate that trick... Made me a
> > DM and "works as expected" worshipper.
>
> > I don't know what ActiveRecord became lately, but I don't want to get
> > back into those long debugging sessions. The problem is that 2.2.x
> > became "thread-unsafe" and was kind of volatile...
>
> > Do you really want me to help you debug something I don't intend to 
> > maintain ?
>
> > You could try to comment out the stuff in singlecon.rb, if you search
> > in this mailing list, you'll find that it somehow seems to have worked
> > for others...
>
> > Cheers,
>
> > --
> > John Mettraux   -  http://jmettraux.wordpress.com
>
>
--~--~---------~--~----~------------~-------~--~----~
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to