geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Łukasz Budnik" <>
Subject Re: extremely annoying G2.0.2 behaviour
Date Tue, 12 Feb 2008 18:50:22 GMT
Hi Jacek!

On 11/02/2008, Jacek Laskowski <> wrote:
> Yes, it's been very annoying, but it's over now. It's fixed in
> Geronimo 2.1 so you may want to try out the just-voted 2.1 release -
> Let us know how it works so we may fix issues before Geronimo 2.1's
> published.


that bombs...

The only one thing that was "wrong" with G2.0.2 was the need of
restarting Geronimo after every deploy.

But in G2.1.0 I cannot deploy my application at all!

Here's the stack trace of this error (occurs when deploying application):

Unable to resolve resource reference
'ProcessInvocationOrderConnectionFactory' (Could not auto-map to
resource.  Try adding a resource-ref mapping to your Geronimo
deployment plan.
Search conducted in current module and dependencies:
[ALL: org.apache.geronimo.configs/j2ee-server//car]
[ALL: org.apache.geronimo.configs/activemq-broker//car]
[ALL: org.apache.geronimo.configs/openjpa//car]
[ALL: org.apache.geronimo.configs/openejb//car]
[ALL: org.apache.geronimo.configs/system-database//car]
[ALL: org.apache.geronimo.configs/tomcat6//car]
[ALL: org.apache.geronimo.configs/transaction//car]
[ALL: org.apache.geronimo.configs/j2ee-corba-yoko//car]
[ALL: org.apache.geronimo.configs/axis//car]
[ALL: org.apache.geronimo.configs/axis2//car]

The thing is it worked in G2.0.2...

What has changed since G2.0.2?

Can I see an example of deploying MDB in G2.1.0, please?

best regards
View raw message