I just noticed that you are using that... it looks like.
I'm not able to reproduce it. The only way I could do it was by using the
regular...
<dependency>
<groupId>org.apache.openejb</groupId>
<artifactId>javaee-api</artifactId>
<version>yourversion</version>
</dependency>
... in the tomcat web app. Make sure that you are using the "tomcat"
classifier version of that jar.
[]s,
Thiago.
On Wed, Oct 29, 2014 at 4:06 PM, Thiago Veronezi <[email protected]>
wrote:
> Use this dependency instead...
>
> <dependency>
> <groupId>org.apache.openejb</groupId>
> <artifactId>javaee-api</artifactId>
> <version>yourversion</version>
> <classifier>tomcat</classifier>
> </dependency>
>
> Please note the "classifier".
>
> []s,
> Thiago.
>
>
>
> On Wed, Oct 29, 2014 at 1:42 PM, Romain Manni-Bucau <[email protected]
> > wrote:
>
>> 2014-10-29 18:28 GMT+01:00 sapozal <[email protected]>:
>> > to be honest- those projects are linked to our inner projects, will be
>> not
>> > simple to disconnect it.
>> > But I posted a client code, server could be any ejb that you want- just
>> call
>> > it MyEjb.
>> > I am pretty sure this is a reproducable problem, however it is always a
>> > possibility that I am wrong and everything is ok
>> >
>> >
>>
>> just a matter of time we can spend "reproducing", if you give us 2
>> modules fast to build then testing is quick, if we need to create a
>> project etc...we need to dedicate more time. Personally I can't do it
>> right now
>>
>> >
>> > --
>> > View this message in context:
>> http://tomee-openejb.979440.n4.nabble.com/Cant-invite-EJB-from-another-Tomcat-tp4672650p4672669.html
>> > Sent from the TomEE Dev mailing list archive at Nabble.com.
>>
>
>
