Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-4308

EJB3: Using @Remote* annotations in EAP "web" config or on EWP causes NPE

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • TBD EAP 5
    • EAP 5.0.1, EWP 5.0.1
    • EJB
    • None
    • Release Notes
    • Hide
      CAUSE

      CONSEQUENCE

      FIX

      RESULT
      Show
      CAUSE CONSEQUENCE FIX RESULT
    • Not Required

      As of EAP/EWP 5.0.1 the file jboss-ejb3-deployer.jar has added the following classes:

      org/jboss/ejb3/iiop/
      org/jboss/ejb3/iiop/BeanCorbaServant.class
      org/jboss/ejb3/iiop/EJB3IIOPWebClassLoader.class
      org/jboss/ejb3/iiop/IORFactory$1.class
      org/jboss/ejb3/iiop/IORFactory$2.class
      org/jboss/ejb3/iiop/IORFactory.class
      org/jboss/as/ejb3/deployers/IORDeployer.class

      but the AS 5 build (thus EAP 5) does not include jboss-iiop.jar in the "web" config, and thus it is not present in EWP either (which is basically EAP 5 "web"). The EWP does not have JMS, so @Remote* is perhaps expected not to work, but an NPE is not a nice way to state that.

      This results in an NPE.

      My suggestion is to separate the above classes in a jboss-ejb3-iiop-deployer.jar or have two different versions of the deployer with and without the iiop classes. So we can use one for "web" in EAP and for EWP, and the other for the ful configs in EAP.

      However, 'd like to register an observation from jcosta:

      jcosta> for me, the right thing to do in this case is to catch CNFE exceptions and log it in the server.log, without re-throwing it

            rhn-engineering-cdewolf Carlo de Wolf
            fnasser Fernando Nasser
            Russell Dickenson Russell Dickenson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: