January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1127) Rework implementation requirements for @Remote, @RemoteHome

by Andrew Lee Rubinger (JIRA)

Rework implementation requirements for @Remote, @RemoteHome ----------------------------------------------------------- Key: EJBTHREE-1127 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1127 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.Beta3 @RemoteHome is sufficient for a 2.1 view; the Remote Interface can be inferred from the return type of the create method. @Remote specifying a 2.1 Interface requires a @RemoteHome. @Remote specifying a Business Interface does not require a home; results in remote 3.0 view. -- 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

16 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1125) getEJBHome and getEJBLocalHome should throw IllegalStateException instead of EJBException

by Carlo de Wolf (JIRA)

getEJBHome and getEJBLocalHome should throw IllegalStateException instead of EJBException ----------------------------------------------------------------------------------------- Key: EJBTHREE-1125 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1125 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.Beta3 getEJBHome and getEJBLocalHome should throw IllegalStateException instead of EJBException when there is no home interface. See http://java.sun.com/javaee/5/docs/api/javax/ejb/EJBContext.html#getEJBHome() -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1124) Default remote interface is incorrectly determined

by Carlo de Wolf (JIRA)

Default remote interface is incorrectly determined -------------------------------------------------- Key: EJBTHREE-1124 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1124 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Priority: Blocker Fix For: AS 5.0.0.Beta3 java.lang.RuntimeException: Use of empty @Remote on bean class and there are more than one default interface: test-bean-for-stateful at org.jboss.ejb3.ProxyFactoryHelper.getRemoteAndBusinessRemoteInterfaces(ProxyFactoryHelper.java:591) at org.jboss.ejb3.Ejb3DescriptorHandler.addDescriptorAnnotations(Ejb3DescriptorHandler.java:862) at org.jboss.ejb3.Ejb3DescriptorHandler.addDescriptorAnnotations(Ejb3DescriptorHandler.java:853) at org.jboss.ejb3.Ejb3DescriptorHandler.getStatelessContainer(Ejb3DescriptorHandler.java:467) at org.jboss.ejb3.Ejb3AnnotationHandler.getContainers(Ejb3AnnotationHandler.java:142) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:511) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:471) at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:453) at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:419) at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:361) at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:134) ... 63 more -- 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

16 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1122) Bean with multiple definitions of the same @Local or @Remote interface fails to deploy

by Carlo de Wolf (JIRA)

Bean with multiple definitions of the same @Local or @Remote interface fails to deploy -------------------------------------------------------------------------------------- Key: EJBTHREE-1122 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1122 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Priority: Blocker Fix For: AS 5.0.0.Beta3 If a bean implements an interface designated as @Local (or @Remote) and it extends a base which implements the same interface, the interface is reported multiple times. Thus the ProxyFactory fails to start. java.lang.IllegalArgumentException: repeated interface: com.sun.ts.tests.ejb30.common.appexception.AppExceptionLocalIF at java.lang.reflect.Proxy.getProxyClass(Proxy.java:370) at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:93) at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:99) at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:93) at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:90) at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211) at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:140) -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1123) Determining the messagingType of a MDB considers too many interfaces

by Carlo de Wolf (JIRA)

Determining the messagingType of a MDB considers too many interfaces -------------------------------------------------------------------- Key: EJBTHREE-1123 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1123 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Priority: Blocker Fix For: AS 5.0.0.Beta3 For determining the messagingType only directly implemented interfaces should be considered, not inherited. java.lang.RuntimeException: Unable to choose messagingType interface for MDB CallbackBean from [interface javax.jms.MessageListener, interface javax.jms.MessageListener, interface com.sun.ts.tests.ejb30.common.callback.CallbackIF] at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:77) at org.jboss.ejb3.mdb.MDB.resolveBusinessInterfaces(MDB.java:116) at org.jboss.ejb3.EJBContainer.instantiated(EJBContainer.java:1256) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:519) ... 72 more -- 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

16 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1119) Handle null or empty "value" on @Pool

by Andrew Lee Rubinger (JIRA)

Handle null or empty "value" on @Pool ------------------------------------- Key: EJBTHREE-1119 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1119 Project: EJB 3.0 Issue Type: Bug Reporter: Andrew Lee Rubinger Fix For: AS 5.0.0.Beta3 Compile-time constraints ensure that "value" attribute of @Pool is specified; this may be bypassed when configuring via XML. Handle this case. -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1104) Annotation overrides from dd are not picked up properly

by Carlo de Wolf (JIRA)

Annotation overrides from dd are not picked up properly ------------------------------------------------------- Key: EJBTHREE-1104 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1104 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.Beta3, AS 4.2.3.GA This throws an exception: unsupported field type int on field public in org.jboss.annotation.ejb.PoolClassImpl.maxSize. <annotation> <annotation-class>org.jboss.annotation.ejb.PoolClass</annotation-class> <annotation-implementation-class>org.jboss.annotation.ejb.PoolClassImpl</annotation-implementation-class> <property> <property-name>value</property-name> <property-value>org.jboss.ejb3.StrictMaxPool</property-value> </property> <property> <property-name>maxSize</property-name> <property-value>5</property-value> </property> <property> <property-name>timeout</property-name> <property-value>10000</property-value> </property> </annotation> In 4 the setting is is ignored. -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1102) Split test methods in dd/mdb so failures are correctly reported

by Carlo de Wolf (JIRA)

Split test methods in dd/mdb so failures are correctly reported --------------------------------------------------------------- Key: EJBTHREE-1102 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1102 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1103) Ensure javax.ejb.EJBTransactionRolledbackException is logged

by Andrew Lee Rubinger (JIRA)

Ensure javax.ejb.EJBTransactionRolledbackException is logged ------------------------------------------------------------ Key: EJBTHREE-1103 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1103 Project: EJB 3.0 Issue Type: Bug Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.Beta3 EJB3 Core Specification 14.3.1 Table 14: When EJBTransactionRolledbackException is returned to the caller (client), the system should log the error (ERROR-level verbosity) -- 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

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1099) Create EJB3 External API JAR (Bean Provider)

by Andrew Lee Rubinger (JIRA)

Create EJB3 External API JAR (Bean Provider) -------------------------------------------- Key: EJBTHREE-1099 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1099 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Critical Fix For: HEAD Should include all annotations and classes that need visibility on the CP of a bean provider, hiding all implementation internals -- 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

16 years, 11 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008