{"issue":{"milestone":null,"user":{"id":124929,"login":"dlaidlaw","url":"https://api.github.com/users/dlaidlaw","avatar_url":"https://secure.gravatar.com/avatar/20b30359f3b92d532a0da19ea41f917b?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"20b30359f3b92d532a0da19ea41f917b"},"title":"Create an API","created_at":"2011-12-12T17:10:58Z","labels":[],"updated_at":"2011-12-16T14:30:25Z","state":"open","id":2525494,"html_url":"https://github.com/BryanHunt/mongo-emf/issues/9","closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"Extract the core features of the plugin to an API that can be used generically to convert EObjects to DBObjects and vice versa.\r\n\r\nBy doing this it will enable users of the conversion library to use the code in their own persistence frameworks, and allow converted objects to be customized individually before persistence. This would also have the side effect of removing the dependency on the IMongoDB object for those using the code outside of OSGi, and let users handle persistence in their own way. ","number":9,"url":"https://api.github.com/repos/BryanHunt/mongo-emf/issues/9","comments":2,"assignee":null},"comment":{"user":{"id":124929,"login":"dlaidlaw","url":"https://api.github.com/users/dlaidlaw","avatar_url":"https://secure.gravatar.com/avatar/20b30359f3b92d532a0da19ea41f917b?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"20b30359f3b92d532a0da19ea41f917b"},"created_at":"2011-12-16T14:30:25Z","updated_at":"2011-12-16T14:30:25Z","id":3177738,"body":"I don't really mind the eClass name and can't think of any reason I would\r\nneed to abstract it away. But I suppose someday it might be required.\r\n\r\nDon Laidlaw | Sr Research Eng. | Infor | Cell +1-902-401-6771 | Home\r\nOffice +1-902-576-5185\r\n\r\n\r\n\r\n\r\nOn 12/16/11 2:41 AM, \"Bryan Hunt\"\r\n<reply+i-2525494-bd16df7ddb3415bfc5f20934f264ea990eeb9cd2-124929@reply.gith\r\nub.com> wrote:\r\n\r\n>Would you expect this API to abstract away the reserved keys like\r\n>_eClass, or would that still be managed by the base algorithm?\r\n>\r\n>--- \r\n>Reply to this email directly or view it on GitHub:\r\n>https://github.com/BryanHunt/mongo-emf/issues/9#issuecomment-3174000","url":"https://api.github.com/repos/BryanHunt/mongo-emf/issues/comments/3177738"},"action":"created"}