0 Replies Latest reply on Jun 26, 2003 8:57 AM by betaniik

    jboss-web.xml: order matters

    betaniik

      Using 3.0.4, I've noticed that the order of the <ejb-ref> elements actually can make or break a deployment.

      This is even in cases where there are no dependencies between the beans concerned, and within our team, an order that will work for one member can break another's.

      E.g.

      <ejb-ref>
      <ejb-ref-name>Ax</ejb-ref-name>
      <jndi-name>Ay</jndi-name>
      </ejb-ref>

      <ejb-ref>
      <ejb-ref-name>Bx</ejb-ref-name>
      <jndi-name>By</jndi-name>
      </ejb-ref>

      may deploy, whereas:

      <ejb-ref>
      <ejb-ref-name>Bx</ejb-ref-name>
      <jndi-name>By</jndi-name>
      </ejb-ref>

      <ejb-ref>
      <ejb-ref-name>Ax</ejb-ref-name>
      <jndi-name>Ay</jndi-name>
      </ejb-ref>

      will cause an DeploymentException (no ejb-link match, use jndi-name in jboss-web.xml)

      Anyone else notice this?

      B