# Should I be able to dynamically load metals at runtime?

**URL:** <https://www.ruby-forum.com/t/should-i-be-able-to-dynamically-load-metals-at-runtime/176264>\
**Category:** Rails\
**Created:** [September 28, 2009, 8:05am UTC](https://www.ruby-forum.com/t/should-i-be-able-to-dynamically-load-metals-at-runtime/176264 "2009-09-28T08:05:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ranjeetsmith](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/858c86/32.png) [@ranjeetsmith](https://www.ruby-forum.com/u/ranjeetsmith)\
**Post date:** [September 28, 2009, 8:05am UTC](https://www.ruby-forum.com/t/should-i-be-able-to-dynamically-load-metals-at-runtime/176264/1 "2009-09-28T08:05:12Z")

</div>

My goal is to be able to poke a metal endpoint into an app from a  
plugin’s init.rb AND not have said metal class’ name camelized since it  
contains acronyms. I didn’t think this was going to be difficult at all,  
but my attempts to replicate the metal loading procedure just gets me  
error spew (the “env” argument isn’t passed through to my class’ call  
method), and metal.rb seems to suggest that such functionality was never  
intended to be available.
