recent news

[thewebs...@gmail.com]

I gave a presentation on JenaBeans at the SFO semantic web meetup.
While writing examples I realized there's no way to get the xml lang
attribute...so I created a special type "LocalizedString" and special
handing features in JenaBean. Any properties of your beans of this
type will get the lang attribute for you. since 1.0.6

Download the preso:
http://tcowan.s3.amazonaws.com/sfo_semweb_meetup.pptx

[David Donohue]

Impressive stuff, Taylor! Clear and powerful presentation. I have
immediate use for LocalizedString and this:
Collection<Woman> women = Sparql.exec(m, Woman.class, query);

I don't understand what bindAll does? which API operations require
that you first call
RDF2Bean.bind() or RDF2Bean.bindAll()?

Dave Donohue

> --
> You received this message because you are subscribed to the Google Groups "jenabean-dev" group.
> To post to this group, send email to jenabe...@googlegroups.com.
> To unsubscribe from this group, send email to jenabean-dev...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/jenabean-dev?hl=en.
>
>

[Taylor Cowan]

Dave,

Only when you are reading RDF which you did not create. When a
jenabean is saved, the type and ontology type are bound via an
annotation which won't exist in a fresh model. Calling "bindAll"
makes the reader aware of the package containing your jenabeans. It
then creates the necessary meta-info to bind the ontology class to the
java class representing it.

In the preso we were hitting the extranet and consuming FOAF, so the
bind call is needed. In the JPA manifestation this is indicated in
the assembler, and the container wires it together by calling
bindAll() for you, given the packages mentioned in the assembler file.

Taylor