Hi,

I am using WebSphere Community Edition 1.0.1.2, what would the syntax look
like here?


Thanks and regards,

- Vimalan


On 8/29/06, David Jencks <david_jencks@yahoo.com> wrote:
>
> The intention in g 1.1.1 is that if A is a dependency of B then an
> ejb-link in B will find the appropriately named ejb in A.  This is
> only likely to work if all ejbs have different names so you don't
> need the moduleLocation#ejbname syntax.
>
> I think I tested this, but it could still be broken despite my best
> recollections.
>
> thanks
> david jencks
>
> On Aug 28, 2006, at 1:19 PM, Aaron Mulder wrote:
>
> > Is this for Geronimo 1.0 or Geronimo 1.1?  The bottom line is that you
> > want to set EAR A to be a parent of (G 1.0) or dependency of (G 1.1)
> > EAR B.  That should ensure that EAR A is started first and that the
> > EJB classes in EAR A are exposed to the components running in EAR B.
> > There was a bug in G 1.1 (fixed in the upcoming G 1.1.1) that related
> > to EJB references, but I don't remember whether it would impact this
> > case.  So the first step is to configure the parent or dependency to
> > make sure the classes are there, and then we may need a little
> > experimentation to get the EJB reference syntax right.
> >
> > Thanks,
> >    Aaron
> >
> > On 8/28/06, Arunanthisivam Vimalathithen <vimalathithen@gmail.com>
> > wrote:
> >>
> >> Hi,
> >>
> >> How can you refer an EJB that is deployed in another EAR. For
> >> example I have
> >> an EAR called ear a which contains an EJB ejb a, I want to refer
> >> this EJB
> >> from another EJB (ejb b) which is packaged and deployed in another
> >> EAR ear
> >> b. Currently I cannot seem to find any other way other than
> >> packaging ejb a
> >> in ear b as well. Is there any way to avoid this?
> >>
> >> Thanksa and regards,
> >>
> >> Vimalan.
>
>