You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomee.apache.org by "gabriel.ozeas" <ga...@gmail.com> on 2012/04/24 19:39:56 UTC

[Resolved]Re: Dumb doubt: No module found for deployment.

Hi Romain,

It works now, this is funny. 

Do you have any idea why we can't start the project name with openejb?

Thanks for the help

--
View this message in context: http://openejb.979440.n4.nabble.com/Dumb-doubt-No-module-found-for-deployment-tp4583796p4584304.html
Sent from the OpenEJB User mailing list archive at Nabble.com.

Re: [Resolved]Re: Dumb doubt: No module found for deployment.

Posted by Romain Manni-Bucau <rm...@gmail.com>.

yep,

because we exclude our internals jar from scanning in a normal deployment.
There are ways to include them but IMO you should simply use another name.

- Romain


2012/4/24 gabriel.ozeas <ga...@gmail.com>

> Hi Romain,
>
> It works now, this is funny.
>
> Do you have any idea why we can't start the project name with openejb?
>
> Thanks for the help
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/Dumb-doubt-No-module-found-for-deployment-tp4583796p4584304.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>