Re: Future of Prevayler?

(working on the baptism problem)

> I will not have the time to build up such a company and give
> Prevayler a pretty site, etc.

Having said that and caused some panic, let me say what I AM doing.

My team and I have invested some 8000 man-hours over the last couple
of years working on Sneer. http://sovereigncomputing.net

You can think of it as an OSGi+Skype crossover on a serious XML-free
diet. We are going to announce its first release this month, I
believe.

Its persistence is entirely based on Prevayler. At some point, we will
provide mirroring (what William called "robust replication") and it
will also be Prevayler-based.

In that context, we will eventually address needs such as
schema-evolution and startup-time.

Sneer also provides transparent prevalence without the need for
explicit transactions.

Sneer components are called bricks, as in Lego. The interface to a
brick is a plain-old-java-interface with a @Brick annotation. To make
it prevalent, you just have to annotate it like this:
@Brick(Prevalent.class). In Sneer terms, that gives your brick the
Prevalent "nature".

That way, the Sneer container will proxy your component and any other
object that your component returns, transparently transforming into
transactions all void method calls.

It already works for primitives and immutable value objects. We are
now working on instrumentation to solve the baptism problem too.

See you, Klaus.

------------------------------------------------------------------------------
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org