Hi echo, a couple of advices - Don't make commits without log message. Logs are very useful to follow activity or to know why something has changed. - Try to follow a set of formatting rules so as the code is more readable with the repo viewer [1], especially use spaces instead of tabs. - Add license header to new files.
[1] http://james.apache.org/contribute.html On Thu, Jul 12, 2012 at 9:35 AM, echo <[email protected]> wrote: > Hi there, > >> Actually the mail server is our datasource, and we get from it very few >> type of objects, just folders and messages. >> >> Folders and messages are not entities in the traditional sense of the >> concept because normally they do not change, so I would not use entities >> but values. >> >> It is pretty easier deal with valueproxies instead of entityproxies >> because the first one have less constrains. >> >> I would create an interface for each value, and I would use this >> interface as the valueproxy in the client. In the server side I would >> implement the valueproxy interface in the valueimplementation class. It >> have to work because I have used this approach some time. >> >> Said that, we need just one service class (or many depending of code >> readability) to interact with the server side. >> > This is really helpful. Hupa-Evo has already been working after I change > the EntityProxy to ValueProxy. > > -- > *echo* >
