[
https://jira.jboss.org/jira/browse/EJBTHREE-1853?page=com.atlassian.jira....
]
Andrew Lee Rubinger updated EJBTHREE-1853:
------------------------------------------
Environment:
JBAS: AS 5.1.0 (from the JBPAPP branch)
Sun JDK jdk1.5.0_17
was:
JBAS: jboss-5.0.0.Beta (from the JBPAPP branch)
Sun JDK jdk1.5.0_17
Probably some sort of assertion in the proxy code, instead of NPE, as well as a
jboss-metadata validation check (in the post-processing chain) that @Remote/@Local
contains an interface would be appropriate.
NPE upon lookup of errorneous EJB
---------------------------------
Key: EJBTHREE-1853
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1853
Project: EJB 3.0
Issue Type: Bug
Environment: JBAS: AS 5.1.0 (from the JBPAPP branch)
Sun JDK jdk1.5.0_17
Reporter: Ondrej Žižka
Assignee: Andrew Lee Rubinger
Attachments: EJBlookup-NPE.zip, log.txt
When a bad EJB is deployed and then looked up remotely, a NPE is thrown - see attached
stack trace.
Steps to reproduce:
1) Start AS 5 and deploy the attached EJB - ejb-stateful-1.0-SNAPSHOT.jar .
2) Run the client - EjbClient-1.0-SNAPSHOT.jar , class ejbtest.EjbClient.StatefulClient
This has quite many dependencies, so it's good idea to open the mvn project (in
the attached zip) and use some IDE's "Run file" function.
Upon ctx.lookup(), the NPE occurs.
----------------
The EJB has:
public interface Counter { }
@Remote
public interface CounterRemote extends Counter { }
@Stateful
@Remote(CounterBean.class)
public class CounterBean implements Counter { }
-------
The client jar contains (incomplete list):
public interface Counter { }
@Stateful
public class CounterBean implements Counter { }
(this wild combination arose when testing :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira