[
https://issues.apache.org/jira/browse/DTACLOUD-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599665#comment-13599665
]
Tzu-Mainn Chen commented on DTACLOUD-507:
-----------------------------------------
Hi,
This fix doesn't quite work for me; it results in errors like this:
`load_missing_constant': Expected
/home/tzumainn/development/aeolus/wingedmonkey/app/models/provider.rb to define
Provider (LoadError)
And when I try to run the Winged Monkey app, the app tries to use the
Deltacloud provider model instead of the Winged Monkey provider model.
The error does go away if I remove the Deltacloud provider model. I did some
digging, and it looks like this sort of issue can happen if a module is not
properly defined. I noticed that there's no deltacloud.rb file that defines
the Deltacloud module; could that be an issue?
Thanks,
Tzu-Mainn Chen
> Possible conflict of Deltacloud model classes with Rails classes
> ----------------------------------------------------------------
>
> Key: DTACLOUD-507
> URL: https://issues.apache.org/jira/browse/DTACLOUD-507
> Project: DeltaCloud
> Issue Type: Bug
> Reporter: Michal Fojtik
> Assignee: Michal Fojtik
>
> Right now the models we have in Deltacloud does not have any namespece.
> Models like 'Provider' or 'Image' exists in the 'global' namespace.
> This could be a problem when you have an Rails app that define models with
> same name (Provider for example).
> I think this is a good argument to make *all* Deltacloud models live in the
> Deltacloud namespace (Deltacloud::Provider).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
