All tests pass and everything compiles on a clean checkout of
hector-jpa for me.
I'm not sure how you got that error from hector-jpa, there is no
reference in that project to
me.prettyprint.hom.CassandraPersistenceProvider. Are you sure you
don't have a reference to hector-object-mapper
yeah, I saw that one, I was more interested in hector-jpa because I
don't think this one supports @OneToMany.
Was hoping the test failures were a temporary thing
On Mon, Jun 6, 2011 at 6:41 PM, Ed Anuff wrote:
> I'd recommend looking into Hector Object Mapper, it provides
>
he next generation of
> JPA
> > in Hector. There is a more lightweight version present in the release
> > version of Hector called Hector Object Mapper. I'm sure Nate or Todd
> who've
> > worked more on hector-jpa can elaborate.
> >
> > Ed
> &
lly represents the next generation of JPA
> in Hector. There is a more lightweight version present in the release
> version of Hector called Hector Object Mapper. I'm sure Nate or Todd who've
> worked more on hector-jpa can elaborate.
>
> Ed
>
> On Mon, Jun 6, 2011 at
That's a work in progress and actually represents the next generation of JPA
in Hector. There is a more lightweight version present in the release
version of Hector called Hector Object Mapper. I'm sure Nate or Todd who've
worked more on hector-jpa can elaborate.
Ed
On Mon, Jun
un 6, 2011 at 5:55 PM, Patrick Julien wrote:
> https://github.com/riptano/hector-jpa
>
> Is this solution usable?
>
> I had problems building it, now tests won't pass.
>
https://github.com/riptano/hector-jpa
Is this solution usable?
I had problems building it, now tests won't pass.
