Hi David,
Thanks for your reply.
I think i might need the second option. Cause what my legacy server does is
a kind of RPC invokation. So I need to embed it into openejb so that it
could accept requests and map requests to specific session ejbs.
If I understand correctly, i need to code up a
Hi -dain
the last build error I mailed in,
was what it said it was, increasing the JAVA heap did the trick.
I successfully compiled openejb3 ...
mit freundlichen Grüßen/best regards
Wolfgang Schrecker
Der Inhalt eines Begriffs nimmt ab, wenn sein Umfang zunimmt; wird dieser
allumfassend, so
This would only be needed if the build fails (and it is only for the
maven process). The problem is we generate and compile a large number
of classes, and the plugin is using javac which isn't very efficient
memory wise. When I get a chance, I'll update the plugin to
optionally support
Thanks for clarification :)
On Wed, Jun 11, 2008 at 8:57 PM, Dain Sundstrom [EMAIL PROTECTED] wrote:
This would only be needed if the build fails (and it is only for the maven
process). The problem is we generate and compile a large number of classes,
and the plugin is using javac which isn't
On Jun 9, 2008, at 3:53 PM, Jon Carrera wrote:
I went for the naughty option for printing out the classpath and it
worked
from within the test case, but didn't work with the bean factory.
Apparently
the problem is in org.springframework.test.jpa.AbstractJpaTests which
internally uses
Hi Chad,
This looks like the exact same issue that Juan Manuel is facing.
I'm going to try and cook up a solution for this and put up some
snapshot binaries that you both can try out. I'll likely be next week
before I can get to this, but hopefully it will only take a couple
days to get
