...@gmail.com wrote:
I may be misunderstanding this, but if you just do bidirectional mappings in
JPA then the DB query is generally efficient and transparent. Could you post
a little snippet showing what you're trying to do?
Derek
On Mon, Apr 27, 2009 at 2:44 PM, TSP tim.pig...@optrak.co.uk wrote
But you don't want the Session in the domain model I thought.
Anyway, after a few hours digging around looking at how other people
do this stuff with respect to DDD in particular, it looks like I am
asking the wrong question to a certain extent. The way it is done in
the DDD site sample app
you think that
there's some performance issue with bidirectional mappings (AFAIK, there
aren't any).
Derek
On Mon, Apr 27, 2009 at 6:01 PM, TSP tim.pig...@optrak.co.uk wrote:
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Question for Derek
my jpa 1.1-SNAPSHOT version seems to have disappeared from the maven
repo to be replaced with 1.1
But at the same time now I've done a maven clean it looks like
RequestVarEM doesn't exist any more. I just got the source from git
and this seems to be the case. So what do I do
I'm at early stages of a fairly big project at the moment and mainly
working in my domain model. Is M1 safe to use, since I doubt we'll get
onto serious UI stuff for at least a month and production is likely
2-3 months after that.
Tim
--~--~-~--~~~---~--~~
You
OK to answer own question in case anyone has similar problems:
ScalaEntityManager returns a bufferWrapper from the jcl.Conversions
not a List. However, it can be treated as a Seq[Postcode]
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Examples, examples, examples, including scala.
The scala-lang site is a bit daunting. I think you'll get more
traction on Lift if you help people to get to grips with scala as well
as lift. I have no idea whether I'm a typical newcomer, but I have
come from Java (previously other things going
Does the lift logging framework support the classed based loggers that
are the normal use pattern:
Logger logger = Logger.getLogger(com.foo);
and the class is automatically attached to the message.
If so how do you call it - with a direct java import or is there
something more lift-esque
In my own defense ... failed to realize the problem that would arise from
defining the EM factory as a singleton
Are you being honest here Derek? Was not the real problem that you
failed to truly embrace the shape of the paradoxical combinator?
Derek
Would you distinguish between what is achievable in a specific ORM
such as Hibernate from JPA in this statement or would you think it
applies to all. I've got to go with hibernate in any case because of
widespread use of UserTypes. Unlike Greg, in my case I can hand-craft
all my hibernate
I tried to construct a test case and the problem seems to have
mysteriously disappeared. Possibly something to do with clean builds.
Sorry to cry wolf.
Tim
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift
11 matches
Mail list logo