General design question-nanning/prevayler

Hi,

I'm designing a small e-commerce web app and I'm using
the nanning/prevayler combination.

I've got a couple of questions as regards how the
design is affected. From what I've seen, for 'aspects'
to be persisted, they need to be created within the
prevaylent system (i.e. IdentifyingSystem).

So I basically need to have one
interface/implementation, responsible for creating
/holding all persistable business objects in the
system??? 

I tried to split up the prevaylent system,
into sub interfaces, sub-implementations but it's
obvious that nanning requires the 'target' interface
to contain the creationmal methods (even though it
extends other interfaces that do so...).

How have other's approached this? Or is this just the
way to do it? What about multiple prevaylent
systems/prevaylers?


On another topic, Jon ,  on the prevayler wiki you
were talking about a rollback system you were using at
lecando. Could you expand a bit on that?

Thanks,

Saimon

=====


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf