Niclas Hedhman wrote:
* org.qi4j.entity.Entity no longer has a unitOfWork() method. Call
Qi4j.getUnitOfWork( entity ) instead.
Is this because of tanglement? My code injects UOWF all the time to do
currentUnitOfWork() and I was actually considering replacing that with
@This Entity to get the UoW. When you say Qi4j.getUnitOfWork(entity)
that is not a static method right? I.e. I have to inject @Structure Qi4j
api; instead? If so, then I have to do two injections if I want to avoid
the UOWF injection: one for the API and one for the composite. Hm... not
sure I like it.
Changes that probably does not affect client code
* ValueType becomes an interface, the implementations are moved to
qi4j-runtime in .types package.
ValueType is also moved to the .property package since it is
strongly bound to PropertyType. Alternatively we could move both to a
.spi.types package.
ValueType has received a bunch of isXyz() methods to query what
kind of ValueType it is. Also types() method has been exposed to
handle RDF Indexer, but should be worked away...
Why is it an interface? Was there something wrong with the baseclass
approach?
Pretty sure I have forgotten something.
I am analyzing qi4j-runtime to see if it is possible to untangle some
major chunks, but that shouldn't hold up the 1.0 release, IMHO.
Great stuff!
While you're at it, can you move Annotations util to API? I need it in
some other projects and don't want a dependency on Runtime.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
