Niclas Hedhman a écrit :
On Tue, Nov 27, 2012 at 12:57 AM, Paul Merlin<[email protected]> wrote:
org.qi4j.extension.cache-ehcache(false) -> beta, none, some
IMO this one should be in 2.0 as library/cache is.
Agree, but the whole cache extension isn't documented at all, which is
a major flaw. I will try to put love into the docs.
<3
org.qi4j.library.neo4j(false) -> beta, good, some
org.qi4j.extension.entitystore-neo4j(false) -> beta, none, some
Theses one use outdated Neo4j and don't work with new versions without
changes.
Need some love before being releasable.
Agree. Problem is that Neo Technology themselves wrote this.
Okay, theses can be added in 2.1 or 2.2 then.
org.qi4j.extension.indexing-solr(false) -> early, brief, none
This one do not provide an Index/Query service but only Index + native
solr queries.
In other words we can not use the Query API with it.
Keep it in. It will never be used for Query API as the underlying
language will not be able to support it.
Reading the Solr documentation I think it would be feasiblelike I did
with ElasticSearch. It will be in 2.0 as is and we'll see afterwards.
org.qi4j.library.eventsourcing(false) -> beta, none, some
org.qi4j.library.eventsourcing-jdbm(false) -> beta, none, some
org.qi4j.library.eventsourcing-rest(false) -> beta, none, some
We decided to postpone the native EventStore support in Qi4j.
Shall we release theses libraries with 2.0?
I don't know.
@Rickard, what do you think?
org.qi4j.library.metrics(false) -> early, none, none
I'm very interested on this one but had no time to get a detailled look.
Niclas?
There should be a corresponding extension for metrics (yammer), which
I think UnitOfWork will hook into, and Usecases drives the metrics.
Don't recall the details, but I suspect that it can be left out
(=disabled in Core), or we can keep it in as a non-documented feature.
I'd like to have metrics in 2.0. The extension is marked as releasable.
I'd go for the undocumented feature for 2.0, maybe I'll dive into this
and write the docs.
====
> What happened to "Play" ?
Play Framework support is in an external project for now:
http://eskatos.github.com/playqi/
Play Framework 2.1 will be released in the following months and I'm
aiming it, not Play 2.0.x.
Thus I kept the code in an external project in order to clear the path
for Qi4j 2.0 release.
The Play Qi4j plugin depends on SNAPSHOTs versions but is usable as is.
I'll import it in the SDK when appropriate.
Cheers
/Paul
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
