[Lift] Re: JPA w/Scala

2008-09-10 Thread Oliver
Hi Derek, this is looking good On Wed, Sep 10, 2008 at 2:55 AM, Derek Chen-Becker [EMAIL PROTECTED]wrote: OK, the code is merged in and the latest version is attached. I made a few minor modifications to the JPA code that Oliver sent: 1. I made the openEM and closeEM methods abstract and

[Lift] Re: JPA w/Scala (and hibernate validator)

2008-09-10 Thread Tim Perrett
Out of interest, I tried playing around with hibernate-validator on this demo to see if it works, and (as you can see below), it doesnt. Any ideas why its doing this? Looking at the compiled bytecode, its trying to invoke the synthesized method name_$eq(String x$1), and for some reason, failing

[Lift] Re: JPA w/Scala (and hibernate validator)

2008-09-10 Thread Viktor Klang
Or just write a PropertyAccessor implementation for Scala vars? That should do the trick. Cheers, Viktor On Wed, Sep 10, 2008 at 3:22 PM, Derek Chen-Becker [EMAIL PROTECTED]wrote: Two lines lower it looks like it's trying to fetch the value (ClassValidator.getMemberValue), but name_$eq is the

[Lift] Re: JPA w/Scala

2008-09-09 Thread Oliver Lambert
On 09/09/2008, at 7:47 PM, Tim Perrett wrote: I agree - its strange and not what we would expect. What version of SQL server are you running? Im using 2005 Enterprise here... I think thats what they are using at my company Its just a really strange thing, the 100 is always ignored... I

[Lift] Re: JPA w/Scala

2008-09-09 Thread Derek Chen-Becker
Looks like I missed a lot in the two days I was gone :). I'm going to look at Oliver's code and merge it. As for Tim's problem with the insertions, the AUTO ID generation should usually just work. I don't have a SQL Server instance to try it out on, but after I merge the code I'll test it again

[Lift] Re: JPA w/Scala

2008-09-09 Thread Derek Chen-Becker
OK, the code is merged in and the latest version is attached. I made a few minor modifications to the JPA code that Oliver sent: 1. I made the openEM and closeEM methods abstract and protected. The idea is that the JPA class shouldn't be tied to the way the user wants to access JPA. Rather, when

[Lift] Re: JPA w/Scala

2008-09-08 Thread Tim Perrett
Just been doing some more debugging on this - it appears that the correct values are being passed through and are assigned to an entity instance, but they blow up when trying to do the em.merge(author) call. The stack trace I get is: ### AUTHOR [EMAIL PROTECTED] ### AUTHOR ID 0 ### AUTHOR NAME

[Lift] Re: JPA w/Scala

2008-09-08 Thread Oliver Lambert
You know I always forget those long winded archetype creation commands and thinking about this I guess I would hope for something more. Something like specify a set of tables (and stuff) and have LiftBuilder go and create mappings, validation and default html for me. I haven't looked at it

[Lift] Re: JPA w/Scala

2008-09-08 Thread Oliver Lambert
I think sql server uses @GeneratedValue(strategy=GenerationType.IDENTITY) You could try this instead of GenerationType.AUTO (though this should translate to the above) Oliver On 09/09/2008, at 12:43 AM, Tim Perrett wrote: Hmmm, I've tried: @Id @GeneratedValue(){val strategy =

[Lift] Re: JPA w/Scala

2008-09-08 Thread Oliver Lambert
or, you could try @GeneratedValue(strategy = GenerationType.AUTO, generator = system-guid) @GenericGenerator(name = system-guid, strategy = guid) with or without the Microsoft driver property name=driverClassName

[Lift] Re: JPA w/Scala

2008-09-08 Thread Tim Perrett
Hey all, Very strange, I re-wrote the classes in Java and I still see the same issue!!! What on earth could be going on here? I tried calling persist rather than merge, but it appeared to have no impact. Cheers Tim --~--~-~--~~~---~--~~ You received this

[Lift] Re: JPA w/Scala

2008-09-08 Thread Oliver
Doesn't look right. The id is the primary key - it could now be inserted with a value of 100, always. I can do an insert here with @Id @GeneratedValue(){val strategy = GenerationType.AUTO} Still works without GeneratedValue being present. My pom dependencies are dependency

[Lift] Re: JPA w/Scala

2008-09-07 Thread Tim Perrett
Ah cool - this is quite nice actually; good work Oliver! @Derek, what are your thoughts? It certainly strikes me that as time wears on and more people are using the lift/jpa stuff that we should really create an archetype for it would others find that useful? Cheers Tim

[Lift] Re: JPA w/Scala

2008-09-07 Thread Charles F. Munat
Oh, hell yeah. Please! And down the road, when the mapper becomes agnostic, would there be an archetype that used JPA as the back end for the Lift mapper? Chas. Tim Perrett wrote: Ah cool - this is quite nice actually; good work Oliver! @Derek, what are your thoughts? It certainly

[Lift] Re: JPA w/Scala - never mind

2008-09-03 Thread Derek Chen-Becker
Sorry I didn't get back to you on that. I'm working on an improved version of the tutorial to include a complete example but it's dependent on 0.10-SNAPSHOT right now. As soon as 0.10 goes GA I'll revise the tutorial page. Derek On Tue, Sep 2, 2008 at 8:35 PM, Charles F. Munat [EMAIL PROTECTED]

[Lift] Re: JPA w/Scala - never mind

2008-09-02 Thread Charles F. Munat
I figured it out, I think. Should be author.name, without the parentheses. Charles F. Munat wrote: Has anyone followed the JPA tutorial using pure Scala instead of Java? I've got it very close to running, but I am getting the following error: [WARNING]