Hello,
I couldn't find any other place to post this, so I'm doing it here,
(it's related to java web development anyway). I've been working on a
project where wicket has access to the domain layer through interfaces
because I didn't want my project to depend on any dbms, however I've
been thinking and the main problem here lies with db4o, since it cannot
make use of JPA annotations on entities (domain models). I would like to
get rid of those interfaces and use concrete implementations to handle
business code inside the entities, but then the above problem arises. So
what recommendations can you give to have a fully implemented domain
model (using jpa annotations) but still be able to use any dbms (or
orm/dmbs) without having to map those the domain model at the service
layer? I hope I can get some feedback on this, as it has been the main
problem I've been facing when coding scalable web applications.
Regards,
Edgar Merino
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
