June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-815) test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)

by Len DiMaggio (JIRA)

test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions) ---------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-815 URL: http://jira.jboss.com/jira/browse/EJBTHREE-815 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798 OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux JDK/JVM: Sun 1.5 java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode) EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 Reporter: Len DiMaggio Priority: Minor EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions) Testcase: testQuerySingleResultExceptions took 0.058 sec Caused an ERROR javax.persistence.NoResultException: No entity found for query javax.ejb.EJBException: javax.persistence.NoResultException: No entity found for query at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263) 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:828) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) Caused by: javax.persistence.NoResultException: No entity found for query at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:82) at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySingleResultExceptions(ExceptionTestBean.java:269) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java: 54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263) 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:828) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) 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:53) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) at $Proxy1.testQuerySingleResultExceptions(Unknown Source) at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySingleResultExceptions(EntityExceptionTestCa se.java:96) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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

18 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-817) test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)

by Len DiMaggio (JIRA)

test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException) --------------------------------------------------------------------------------- Key: EJBTHREE-817 URL: http://jira.jboss.com/jira/browse/EJBTHREE-817 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798 OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux JDK/JVM: Sun 1.5 java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode) EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 Reporter: Len DiMaggio Priority: Minor EJB3 test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException) Testcase: testRuntimeException took 2.058 sec FAILED expected:<1> but was:<0> junit.framework.AssertionFailedError: expected:<1> but was:<0> at org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase.testRuntimeException(MDBUnitTestCase.java:292) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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

18 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-786) String remove() method on SFSB

by Gavin King (JIRA)

String remove() method on SFSB ------------------------------ Key: EJBTHREE-786 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786 Project: EJB 3.0 Issue Type: Bug Reporter: Gavin King Assigned To: Bill Burke I get the following exception if I try to declare a method with the signature String remove() on the local interface: 17:53:02,953 WARN [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3 java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610) at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420) at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306) at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501) at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58) at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66) at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61) at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105) at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124) at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy96.start(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

18 years, 9 months

6
15
0 / 0

[JBoss JIRA] Created: (JBAS-4180) Reduce coupling between JMX and HASingleton

by Brian Stansberry (JIRA)

Reduce coupling between JMX and HASingleton ------------------------------------------- Key: JBAS-4180 URL: http://jira.jboss.com/jira/browse/JBAS-4180 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff. For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX. Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work. -- 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

18 years, 9 months

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-4361) java.util.logging.FileHandler.formatter cannot be changed to java.util.logging.SimpleFormatter

by Wolfgang Knauf (JIRA)

java.util.logging.FileHandler.formatter cannot be changed to java.util.logging.SimpleFormatter ---------------------------------------------------------------------------------------------- Key: JBAS-4361 URL: http://jira.jboss.com/jira/browse/JBAS-4361 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-4.2.0.CR2 Environment: JDK is 1.5.0_11-b03 Reporter: Wolfgang Knauf Assigned To: Scott M Stark Priority: Minor I tried to create a plain text log output with this logging.properties file: handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler .level= INFO java.util.logging.FileHandler.pattern = c:/temp/logfile.log java.util.logging.FileHandler.level = INFO java.util.logging.FileHandler.limit = 50000 java.util.logging.FileHandler.count = 1 java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter java.util.logging.ConsoleHandler.level = INFO java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter I startup the server with this commandline: run.bat -c default -Djava.util.logging.config.file=c:/temp/logging.properties The log file is placed in c:\temp\logfile.log and contains my output, but it is in XML, not in Simple format. Console output is in SimpleFormat as expected. -- 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

18 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-24) Get OpenSaml2 snapshot libraries into the JBoss repository

by Anil Saldhana (JIRA)

Get OpenSaml2 snapshot libraries into the JBoss repository ---------------------------------------------------------- Key: SECURITY-24 URL: http://jira.jboss.com/jira/browse/SECURITY-24 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OnDemand, Repository Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 The Open Saml version 2 development is happening in the community. To create a set of tests that will use an implementation of the Security SPI with federation capabilities, it is necessary to have snapshot archives of opensaml2 in the JBoss repositories. -- 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

18 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1300) Default a portlet window to maximized.

by David Roberts (JIRA)

Default a portlet window to maximized. -------------------------------------- Key: JBPORTAL-1300 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Roberts Priority: Optional When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page. -- 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

18 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-987) display non GMT+0 time zones

by Jean-Louis Rastapoc (JIRA)

display non GMT+0 time zones ---------------------------- Key: JBPM-987 URL: http://jira.jboss.com/jira/browse/JBPM-987 Project: JBoss jBPM Issue Type: Feature Request Components: Web Interface Affects Versions: jBPM jPDL 3.2 Reporter: Jean-Louis Rastapoc Assigned To: Tom Baeyens The web-console currently uses the default JSF timezone conversion and displays GMT+0. Other time zones should be read from the client or be configurable. -- 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

18 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAOP-415) Advice Matching algorithm is ignoring generics

by Flavia Rainone (JIRA)

Advice Matching algorithm is ignoring generics ---------------------------------------------- Key: JBAOP-415 URL: http://jira.jboss.com/jira/browse/JBAOP-415 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.alpha5 Advice Matching does not takes into account generic types; it is working with the old reflection API instead (Class instead of Type). To modifiy this, we need to update code in classes: - org.jboss.aop.advice.annotation.AdviceInfo - org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo - org.jboss.aop.advice.AdviceMethodProperties - joinpoint generators that pass the return, arguments and exception types to AdviceMethodProperties instances. This includes updating the assignability degree algorithm of org.jboss.aop.advice.annotation package. The methods for this task are partly written in org.jboss.test.aop.beforeafterArgs.ArgAspectGenerics. Tests for generic return types are also necessary, and need to be written. -- 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

18 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1038) Allow export of database to xml

by William DeCoste (JIRA)

Allow export of database to xml ------------------------------- Key: JBPORTAL-1038 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1038 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: William DeCoste Priority: Minor This feature was requested by Intuit. -- 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

18 years, 9 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007