Hey
Aaron Mulder wrote:
> I just ran Pet Store EJB JAR through EJX to create a
> jboss.xml. I loaded the existing ejb-jar.xml as type "EJB+jBoss" and
> added entries for the EJB references. Here's an example:
>
> beans TheCart, TheCatalog
> TheCart has an EJB reference to TheCatalog:
> ejb-ref-name=ejb/catalog
> ejb-link=TheCatalog
>
> When I go into the jBoss configuration section, there's a blank
> for "JNDI Name" for the referenced bean. I enter "TheCatalog". The
> output jboss.xml has:
>
> ejb-ref-name=ejb/TheCatalog
> jndi-name=TheCatalog
>
> This is clearly wrong, and jBoss refuses to start. The
> ejb-ref-name in the output should match the one in ejb-jar.xml, namely
> "ejb/catalog" not "ejb/TheCatalog".
> Now, I'm not sure I should even be using this setting, since the
> referenced EJB is named by the ejb-link.
No, you should not use this. Nevertheless, you found a bug!
> But I'm extra unsure how it came
> up with the ejb-ref-name it used, which is something I never typed in
> anywhere - it's a mix of new and old!
>
> Finally, this only happened on 2 or 3 of 10 EJB references. If
> no one has any immediate thoughts, I'll enter a bug report.
The problem is in the EjbReference code from EJX. When a ejb-link is
specified it tries to find the bean that is linked to and updates the
settings. This should be turned off during XML import, but it is
not...add this to BugZilla.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
