scratch that, I see some other classes with Edm prefix already. Surely as you 
can see even after looking at the code for sometime I still get confused with 
similarly named classes. Renaming them to correctly represent their function is 
really going help understand for service developers IMO. I understand they are 
in different packages, but does not do whole lot of good. 

I am still learning -:)

Ramesh..

----- Original Message -----
> Hi,
> 
> Since we are refactoring lot of common-api, common-core code, is it possible
> to rename classes in "org.apache.olingo.commons.api.edm.provider" package in
> the common-api module to prefix something like "Edm", so they are EdmAction,
> EdmActionImport etc? I always get confused which classes to select when some
> of the classes with same name show up from
> "org.apache.olingo.commons.api.data" package. By adding this prefix, it
> would be much more clear IMO.
> 
> what do you guys think?
> 
> Ramesh..
> http://teiid.org
> 
> 

Reply via email to