Rails - Jun 2006 - Module nastiness

Yesterday I was having problems getting fixtures to load correctly
after moving my models into separate modules.   Wrote a patch for
fixtures and all was fine.

Then I put my app into production mode.  I''ve got two classes named
Player.  HHConv::Player and Trainer::Player.  Rails seems to only care
about the Player class that first gets loaded in, even if I name them
explicitly using the full namespace.

What''s going on here?  The only problems I''ve heard are with
fixtures,
but I got past that...now I''m having this problem that only occurs in
production.  Any ideas?

Pat

Pat,

Did you ever figure out what was going on with this?  I''m interested in
your solution, or what you were able to find out about the class loading.

Thanks,
Josh


On Thursday, June 08, 2006, at 5:03 AM, Pat Maddox
wrote:
>Yesterday I was having problems getting fixtures to load correctly
>after moving my models into separate modules.   Wrote a patch for
>fixtures and all was fine.
>
>Then I put my app into production mode.  I''ve got two classes named
>Player.  HHConv::Player and Trainer::Player.  Rails seems to only care
>about the Player class that first gets loaded in, even if I name them
>explicitly using the full namespace.
>
>What''s going on here?  The only problems I''ve heard are
with fixtures,
>but I got past that...now I''m having this problem that only occurs
in
>production.  Any ideas?
>
>Pat
>_______________________________________________
>Rails mailing list
>Rails@lists.rubyonrails.org
>http://lists.rubyonrails.org/mailman/listinfo/rails



-- 
Posted with http://DevLists.com.  Sign up and save your mailbox.