ScalaJPA returns things as either Options or BufferWrappers. The limitation
on entities is due to JPA wanting something implementing the Java Set, List,
Map interfaces and not Scala's. User types are similarly not included in
standard JPA 1.0, although there's talk of putting that into JPA 2.0.
Yes, I helped with the code!
On Sat, May 23, 2009 at 9:28 PM, Timothy Perrett timo...@getintheloop.euwrote:
To what degree are you wanting to re-invent the wheel? Derek has done
amazing work with JPA and Scala - the resulting output being scala-jpa and
the jpa archetypes for lift. Are you
Lol! Sorry oliver... I remember now :)
What did you have in mind for ³scala solution using JPA²? Is this not what
we have already?
Cheers, Tim
On 23/05/2009 12:33, Oliver Lambert olambo...@gmail.com wrote:
Yes, I helped with the code!
On Sat, May 23, 2009 at 9:28 PM, Timothy Perrett
When I want to have user defined types, I have to write them as a Hibernate
hack to JPA - Id rather not be wedded to Hibernate.When I get a collection
out of a returned entity, I have to use JCL to wrap it. I'd rather, have
everything in Scala collections.
When I have a read only entity, I'd like
Interesting...
Have you seen jorge's scala utils? Perhaps we could do some magic with
that to manage translations between java.util.list etc to native scala
types...?
Cheers, Tim
Sent from my iPhone
On 23 May 2009, at 12:58, Oliver Lambert olambo...@gmail.com wrote:
When I want to have
Hey there,
Is their a particular reason you wouldn't or couldn't use existing java
persistence infrastructure inside your scala application? That's the
recommended advice right now; JPA (for instance) will slot right into your
app :-)
Cheers, Tim
On 22/05/2009 20:43, braver
On May 22, 7:06 pm, Timothy Perrett timo...@getintheloop.eu wrote:
Hey there,
Is their a particular reason you wouldn't or couldn't use existing java
persistence infrastructure inside your scala application? That's the
recommended advice right now; JPA (for instance) will slot right into
