Closed GoogleCodeExporter closed 9 years ago
I did some testing and I isolated the offending method to this one
public void setPersister(Persister persister)
When I comment this method out, the NullPointerException goes away, and
Bean2RDF.saveDeep(myBean) works properly
So this Persister class is not a Jenabean, and not intended to be saved.
Is this a bug? Should Jenabean ignore fields that it cannot handle? Or is
there a
way to annotate the persister field and the setPersister() method to make
Jenabean
ignore it?
Original comment by drdono...@gmail.com
on 1 Mar 2008 at 2:03
>Should Jenabean ignore fields that it cannot handle?
Yes, it really should. It's just a matter of indicated which ones they are.
We can do several things...annotation based @ignore, use the java feature of
marking
the field as "transient", or only save properties that are "serializable", or
only
persist fields that are annotated with @RdfProperty.
Original comment by thewebse...@gmail.com
on 4 Mar 2008 at 3:53
Original comment by thewebse...@gmail.com
on 4 Mar 2008 at 3:54
Original comment by thewebse...@gmail.com
on 6 Nov 2008 at 4:20
Original issue reported on code.google.com by
drdono...@gmail.com
on 1 Mar 2008 at 4:06