On Sep 30, 2004, at 6:24 PM, karan singh malhi wrote:
Assuming we only
find one matching ejb, we will use that one for the ref. If we find
two or more matches, you would get an AmbiguousEJBRefException, and if
we find none you would get a DeploymentException.
if the ejb-ref maps to the home and r
Assuming we only
> find one matching ejb, we will use that one for the ref. If we find
> two or more matches, you would get an AmbiguousEJBRefException, and if
> we find none you would get a DeploymentException.
>
if the ejb-ref maps to the home and remote interface, what would be a scenario
On Sep 30, 2004, at 3:51 PM, karan singh malhi wrote:
Thanks Dain,
How will the match be determined? is the ejb-ref name going to match
the
home interface name?
No, and ejb-ref contains the name of the home interface and remote
interface (or local and local-home). Here is an example from one of
Thanks Dain,
How will the match be determined? is the ejb-ref name going to match the
home interface name?
Is it possible that to remove ambiguity, we could make an entry into the
geronimo dd where we could map the ejb-ref with a fully qualified name
of the home interface.
On Thu, 2004-09-30 a
On Sep 30, 2004, at 3:31 PM, karan singh malhi wrote:
Some applications assume that ejb-refs can be resolved by matching on
interface types.
What does this mean?
Some applications like Petstore (at least the version Rajesh used)
don't have ejb-links so you have to resolve the reference by hand (a
Some applications assume that ejb-refs can be resolved by matching on
interface types.
What does this mean?
On Thu, 2004-09-30 at 16:57, [EMAIL PROTECTED] wrote:
> Message:
>
> A new issue has been created in JIRA.
>
> -
> V
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-340
Here is an overview of the issue:
-
