December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1071) Business Interface must not extend EJBObject or EJBLocalObject

by Andrew Rubinger (JIRA)

Business Interface must not extend EJBObject or EJBLocalObject -------------------------------------------------------------- Key: EJBTHREE-1071 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1071 Project: EJB 3.0 Issue Type: Bug Reporter: Andrew Rubinger Assigned To: Andrew Rubinger Fix For: HEAD EJB3 Spec 4.6.6 Bullet 1: "The following are the requirements for the session bean's business interface: * The interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface." ...thus the following construct: public interface StatefulRemote extends EJBObject{...} ...and: @Stateful @Remote(StatefulRemote.class) @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE) public class StatefulRemoteBean ...should fail with a deployment exception referencing the specification. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1067) Refactor EJB 3 onto the unified metadata

by Carlo de Wolf (JIRA)

Refactor EJB 3 onto the unified metadata ---------------------------------------- Key: EJBTHREE-1067 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1067 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical Fix For: AS 5.0.0.Beta3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1066) Business interfaces defined in the descriptor are ignored

by Carlo de Wolf (JIRA)

Business interfaces defined in the descriptor are ignored --------------------------------------------------------- Key: EJBTHREE-1066 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

3
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1041) Suppling a RemoteHome or LocalHome is not registered

by Carlo de Wolf (JIRA)

Suppling a RemoteHome or LocalHome is not registered ---------------------------------------------------- Key: EJBTHREE-1041 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1041 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1042) Container should register a dependency on JNDI name if specified

by Carlo de Wolf (JIRA)

Container should register a dependency on JNDI name if specified ---------------------------------------------------------------- Key: EJBTHREE-1042 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1042 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD A container should register a dependency on a JNDI name, if specified, instead of on a container or interface. Suppose that an interface is used twice by different beans and as diffentiator JNDI name is used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1058) Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined

by Andrew Rubinger (JIRA)

Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined ------------------------------------------------------------------------------- Key: EJBTHREE-1058 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 5.0.0.Beta3, HEAD Reporter: Andrew Rubinger Assigned To: Andrew Rubinger Fix For: AS 5.0.0.Beta3, HEAD Assuming: public interface StatefulRemote extends EJBObject{...} ...and: @Stateful @Remote(StatefulRemote.class) @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE) public class StatefulRemoteBean ..when invoking: Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE); EJBObject ejbObject = (EJBObject) obj; ejbObject.remove(); ...the following exception is encountered: Could not resolve beanClass method from proxy call java.lang.RuntimeException: Could not resolve beanClass method from proxy call at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:1634) at org.jboss.remoting.Client.invoke(Client.java:548) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135) at $Proxy2.remove(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1033) Add EJB2.x JMX metrics to EJB3

by Carlo de Wolf (JIRA)

Add EJB2.x JMX metrics to EJB3 ------------------------------ Key: EJBTHREE-1033 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1033 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Assigned To: William DeCoste Fix For: AS 4.2.0 GA Stateless: AvailableCount, MaxSize, CurrentSize, CreateCount, RemoveCount Stateful: CacheSize, PassivatedCount, CreateCount, RemoveCount, AvailableSize, CurrentSize, MaxSize MDB: MinPoolSize, MaxPoolSize, MaxMessages, KeepAliveMillis -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1014) Deployment dependencies in new VDF

by Carlo de Wolf (JIRA)

Deployment dependencies in new VDF ---------------------------------- Key: EJBTHREE-1014 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1014 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC11 - FD Containers are started in the wrong order. This needs a proper supply / demand chain. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1004) EJBRegistrationDeployer doesn't come up

by Carlo de Wolf (JIRA)

EJBRegistrationDeployer doesn't come up --------------------------------------- Key: EJBTHREE-1004 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1004 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Blocker -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1020) java:comp/EJBContext broken

by Carlo de Wolf (JIRA)

java:comp/EJBContext broken --------------------------- Key: EJBTHREE-1020 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1020 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD java:comp/EJBContext is bound at semi-random times, which results in broken behaviour. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007