Search:

Your DataNucleus exceptions were due to the fact that your Datanucleus enhancer didn't run. If you are running eclipse or STS, cleaning the project usually does the trick.

Regarding you two latest...

I've dug into it and it seems there is a regression in 1.1.2.BUILD-SNAPSHOT [rev 6c006f1].
I tried with 1.1.1.RELEASE [rev 156ccd6] and I don't get the Long id error.
(but I do get the hardcoded...

I tried creating a new project based on jaredrowell's script and using the latest roo from git (1.1.2.BUILD-SNAPSHOT [rev 6c006f1]). It still fails because the primary key of Address is a long.
...

I tried a (somewhat dirty) hack:

This thread seemed promising at first: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/f21380e5f375b112

I was hoping to read the body of...

I'm glad somebody else is working on it too. It was a bit of a blocker for me. I ended up removing Roo in order to be able to implement security.


I agree that your second solution seems to be...

You could try a

perform eclipse

And then import it as an eclipse project instead of a maven project?

Add the following vm arg:



-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl

Hi,

I wonder if this is a bug or if I did something wrong but the server side validation doesn't seem to be implemented on GAE.

I get the validation errors on the client side and I'm able to...

That's what I did:



@Configurable
@Entity
@RooJavaBean
@RooToString
@RooEntity
@UniqueEmail

When using JSP, it's easy to setup Spring security for authentication and authorisation purposes (based on controllers/servlets). However, I'm using GWT (and it's RequestFactory) so there is only one...

In my case, I'm using GWT so only the following error got "fixed"



org.springframework.beans.factory.BeanCreationExce ption: Error creating bean with name...

I have a painfull workround: keep trying.

It happened to me a week ago but the after re-compiling and re-deploying several times it worked.
Then the same error happened again yesterday so I ended...

I get the same error.

1.0.7.final is within [1.0.4, 1.1.5.final] so I guess there is some configuration error somwhere.

Did you find a fix ?

I think it's a bug. I get the same error.

Modifying the web.xml as Justin says works though.