If no object_class is present, do not try to instantiate an object when building the bundle. This does not affect model-based resources; however, the assumption that had been made that an object_class is always going to be present is not valid when using custom Resource objects that are not necessarily model-based.
Added test case to demonstrate resources without object_class defined failing on build_bundle
Made proper test for checking Resource objects without a defined object_class.
Merge pull request #877 from terpsquared/master

Fixed assumption that breaks non-model based resources during bundle building