hi, best for now is to follow the 0.2 release of mailbox. i think we should be able to release 0.3 soon but till then you should not care to much about it. We will help you to migrate your code once it is out.
You should not use the low-level mailbox-api if possible. just extend the mailbbox-store api, thats the high-level one.. bye norman Am Montag, 13. Juni 2011 schrieb Ioan Eugen Stan <stan.ieu...@gmail.com>: > Hello everybody, > > I made some progress with the mailbox. I began by implementing > mailbox-hbase by following mailbox-jpa. > > I started my implementation by relaying heavily on the JPA > implementation which in turn uses mailbox-store. JPA (and the store??) > has transactions which, from my knowledge, are not supported in HBase. > Not in the traditional RDBMS way anyhow. > > I'm thinking of going duplicating the way JPA is implemented as much > as possible and do mock-ups when necessary. The other option is to > implement the Mailbox API interfaces directly. What do you think? > > By the way, following trunk is very tricky. Things get changed a lot > and rather fast. I implemented a class by extending an existing class > in store this morning and now it was changed. > What's the best way to you keep up with it? > > Code is available here: > http://code.google.com/a/apache-extras.org/p/mailbox-hdfs/source/browse/ > > You can get a copy by running: > hg clone https://stan.ieu...@hg.codespot.com/a/apache-extras.org/mailbox-hdfs/ > mailbox-hdfs > > Regards, > > -- > Ioan „happy coder” Eugen Stan > http://ieugen.blogspot.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org > For additional commands, e-mail: server-dev-h...@james.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
