On Jul 10, 7:29 pm, "Nicolas H. Modrzyk" <[EMAIL PROTECTED]> wrote:
Hi John and Nicolas:
thanks for your replies.
> Given the link below it could be that you have an old version of ruby
> gems installed on your
> machine.http://rubyforge.org/pipermail/rubygems-developers/2007-February/
> 002601.html
>
> Looks like some methods were conflicting.
>
> Can you let us know if that is the case ?
>
We added the workaround suggested by John (passing the
RAILS_DEFAULT_LOGGER to the constructor), which temporarily fixed the
problem. However, we then hit a similar problem again when we
included a reference to the OpenWFE::Engine in one of our rails
controllers. We observed that our test suite (unit, functional,
integration) was breaking again: the failing tests were entirely
unrelated to the code referencing OpenWferu (OpenWferu would just
mysteriously trigger the failure).
After some detailed investigation, my peer discovered that this was an
issue related with the rest-open-uri gem: our code had the inclusion:
require 'rest-open-uri'
but instead needed:
require 'open-uri'
require 'rest-open-uri'
So adding the 'open-uri' inclusion fixed the problem. Why this
problem was only exposed when adding Openwferu is still a mystery to
me, I guess it has to do with the order in which gems get included/
loaded???
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenWFEru users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
