[jboss-jira] [JBoss JIRA] (AS7-2873) EJB not defining an EJB 2 view method should not deploy
Dan Wilkin (JIRA)
jira-events at lists.jboss.org
Fri Sep 7 08:22:32 EDT 2012
[ https://issues.jboss.org/browse/AS7-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716599#comment-12716599 ]
Dan Wilkin edited comment on AS7-2873 at 9/7/12 8:20 AM:
---------------------------------------------------------
This same exception occurs in 7.1.0 Final also if two uniquely defined Session Beans reference the same interface in the {{@Remote}} annotation. This can occur from a copy-paste error:
{code:title=RedSLSB.java}
@Stateless
@Remote(Red.class)
public class RedSLSB implements Red {
...
}
{code}
{code:title=BlueSLSB.java}
@Stateless
@Remote(Red.class)
public class BlueSLSB implements Blue {
...
}
{code}
was (Author: dabble-balancer):
This same exception occurs in 7.1.0 Final also if two uniquely defined Session Beans reference the same interface in the @Remote annotation. This can occur from a copy-paste error:
{code:title=RedSLSB.java}
@Stateless
@Remote(Red.class)
public class RedSLSB implements Red {
...
}
{code}
{code:title=BlueSLSB.java}
@Stateless
@Remote(Red.class)
public class BlueSLSB implements Blue {
...
}
{code}
> EJB not defining an EJB 2 view method should not deploy
> -------------------------------------------------------
>
> Key: AS7-2873
> URL: https://issues.jboss.org/browse/AS7-2873
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Reporter: Carlo de Wolf
> Assignee: Stuart Douglas
> Fix For: 7.1.0.CR1
>
>
> A bean which does not implement the sayHello method of the following EJB 2 remote view:
> {code:title=HelloRemote.java}
> public interface HelloRemote extends EJBObject {
> String sayHello(String name) throws RemoteException;
> }
> {code}
> gets the following exception during invocation:
> {noformat}
> Caused by: javax.ejb.EJBException: org.jboss.invocation.CannotProceedException: INV-00002:Invocation cannot proceed (end of interceptor chain has been hit)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:241)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:201)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:86)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:70)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:56)
> ... 126 more
> {noformat}
> Instead the EJB should not have deployed properly and throw a DeploymentException.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list