Bugs: Browse | Submit New | Admin

[#26262] Module::const_missing_not_from_s3_library affects all classes ending in Bucket or S3Object in the global namespace.

Date:
2009-06-17 16:22		 Priority:
3
Submitted By:
Nobody 		Assigned To:
Nobody (None)
Category:
None		 State:
Open
Summary:
Module::const_missing_not_from_s3_library affects all classes ending in Bucket or S3Object in the global namespace.

Detailed description 
Specifically, this is a problem with Rails in development mode because aws-s3 gets loaded after Rails, placing
its const_missing definition at the top of the chain. Therefore a reference to, for example, a Rails model ending in
Bucket mistakenly returns an instance of AWS::S3::Bucket.

Add A Comment: Notepad

Please login


Followup

Message 
Date: 2010-09-23 22:21
Sender: Joe Fiorini

Just ran into this in my app. We have a class that ends in Bucket
that does not have anything to do with Amazon. What was mentioned
in the description is EXACTLY what happened to me. I'm not sure
if anyone is maintaining this project, but please, could you
fix this? This is very bad form for a Ruby library. I'd happily
submit a patch to remove this abhorrence.

Attached Files:

Name Description Download
No Files Currently Attached

Changes:

No Changes Have Been Made to This Item