You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Michal Fojtik (JIRA)" <ji...@apache.org> on 2013/04/09 17:48:15 UTC

[jira] [Commented] (DTACLOUD-507) Possible conflict of Deltacloud model classes with Rails classes

    [ https://issues.apache.org/jira/browse/DTACLOUD-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626731#comment-13626731 ] 

Michal Fojtik commented on DTACLOUD-507:
----------------------------------------

Hmm, that is weird, the Provider class is placed properly into Deltacloud module namespace. What you mentioned could be the issue. What happen if you define this in the initializer:

module Deltacloud; end

Otherwise I'll do more investigation on this.
                
> 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