Backgroundrb devel - Aug 2008 - Jabber namespace strangeness in workers when config.gem ''xmpp4r'' is set

Just spent three bloody hours looking for the cause of this, so I thought
I''d save anyone else having the same problem the trouble:

In the process of porting our existing app to 2.1.0 and decided I''d use
the
config.gem functionality.  I''ve got a legacy worker?working that passes
off
messages to our ejabberd server and works fine.  It depends on xmpp4r.
Yesterday, as part of a larger set of changes, I checked in environment.rb
with the line: config.gem ''xmpp4r'', :version =>
''0.3.2''.  Today, on
restarting backgroundrb, the xmpp worker suddenly starts throwing the
following exception:

  uninitialized constant XmppWorker::Jabber (NameError)

I went through everything I could think of before finally digging back
through the svn diff and noticing the config.gem ''xmpp4r''. 
Commented it out
and, hey presto!, everything went back to normal.

I''m hoping the complete silence of google on the topic means no one
else has
encountered it.  However, if not, I hope this helps.

Best,
Todd
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080807/a594420f/attachment-0001.html>

Todd Tyree wrote:
> Just spent three bloody hours looking for the cause of this, so I 
> thought I''d save anyone else having the same problem the trouble:
>
> In the process of porting our existing app to 2.1.0 and decided
I''d
> use the config.gem functionality.  I''ve got a legacy
worker?working
> that passes off messages to our ejabberd server and works fine.  It 
> depends on xmpp4r.  Yesterday, as part of a larger set of changes, I 
> checked in environment.rb with the line: config.gem
''xmpp4r'', :version
> => ''0.3.2''.  Today, on restarting backgroundrb, the
xmpp worker
> suddenly starts throwing the following exception:
>
>   uninitialized constant XmppWorker::Jabber (NameError)
>
> I went through everything I could think of before finally digging back 
> through the svn diff and noticing the config.gem
''xmpp4r''.  Commented
> it out and, hey presto!, everything went back to normal. 
Could it possibly be causing the gems to load in a different order to 
normal (hence triggering the error due to some dependency issue?)

Ed W

> Could it possibly be causing the gems to load in a different order to
> normal (hence triggering the error due to some dependency issue?)
>
> Ed W
>

Seems reasonable.  When I have a bit more time I''ll investigate.  In
the
meantime, I''ll just have to keep track of the dependency manually.

--T
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080811/b7b9ffe5/attachment-0001.html>