Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of fakod666@googlemail.com
 designates 74.125.82.46 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=QIGSO7N3b6kQq0FrAtn55wjNNu1tmyfLm2DBtfpjFFHG9RdSK1X0R9uBpC8MNX2f4u
         +uQcBpQrLHR6ZeiqZnWXTGeJIk1uO1sNy3c+++QQi5Q52sCXe2eMlwZHhR1QqdtrxkUf
         V/K4GutR8ieaJJ6PoU3IoTFTqynH0bbTMdfbI=
MIME-Version: 1.0
In-Reply-To: <AANLkTiklfe_YBsotWnLHpp35a1vmjngAymW5CA8eUZIN@mail.gmail.com>
References: <AANLkTilRHPUigC_8i6AWgaMyfWfwUuIH5nyxL56EDtnB@mail.gmail.com>
	 <AANLkTikQKu6D-ysA7H0OBzHN6UeAfFYX4QEJ8qfAQz1Y@mail.gmail.com>
	 <AANLkTikV4IjwZvl190cTYMHEgR8P3dF7gW71aBFSDO52@mail.gmail.com>
	 <AANLkTimQ-ZPdglnUVF60u0GRAiFtQtO9HIljWnNK_XRK@mail.gmail.com>
	 <AANLkTik-ru342udISBX1bvEikL96C9GSSN9CJb63x6zm@mail.gmail.com>
	 <AANLkTiklfe_YBsotWnLHpp35a1vmjngAymW5CA8eUZIN@mail.gmail.com>
Date: Mon, 24 May 2010 11:15:03 +0200
Message-ID: <AANLkTikZiHqDdizwOJ003jfH7wD-iKmwHzSLNjbRNA6x@mail.gmail.com>
Subject: Re: JPA and Scala
From: Christopher Schmidt <fakod666@googlemail.com>
To: dev@openjpa.apache.org
Content-Type: text/plain; charset=ISO-8859-1

John, I am not sure if I understand you right... (JPAExtension is not
a application, it is a library)

5 years ago we started to use a really complex relational schema (that
uses really every relational modeling feature available regarding
primary keys and subclassing). We used Hibernate (non JPA) for access,
AspectJ (for transaction and rights handling) and Sun's Jersey (JAX-RS
implementation) to deploy it (in a Tomcat) as several webservices.

This year we started to switch to JPA 2.0 (and OpenJPA. Bender1199
posted already some questions here or to the user list) as persistence
layer. Next step was to think about using Scala as "backend language"
and therefore we started to use it together with OpenJPA. The first
thing what came out was wrapping EntitiyManager, EntityManagerFacory
and Query (to make it more type safe). The filter-object concept was
to simplify the query parameter handling (and make it more typesafe
again). The result is the JPAExtension - thats all.

The "Server Side Example" in my blog came from a small geo tagging
project (mainly a test for replacing Aspects by Scala's functional
elements)

Hope thats what you wanted to know...

Christopher

On Sun, May 23, 2010 at 1:30 PM, Web developer <webautomator2@gmail.com> wrote:
> Who will use your application? What process it automates? John
>
> 2010/5/22 Christopher Schmidt <fakod666@googlemail.com>
>
>> Just to be sure: what do you mean with practical purpose?
>>
>> Christopher
>>
>> Am 22.05.2010 13:49 schrieb "Web developer" <webautomator2@gmail.com>:
>>
>> Interesting, and what is a practical purpose of application(s) that you
>> develop? John
>>
>> 2010/5/21 Christopher Schmidt <fakod666@googlemail.com>
>>
>>
>> > Hi all,
>> > I am working on a JPA wrapper for Scala and I think that I have found
>> > an elegant way ...
>>
>