May 2007 - jboss-jira - Jboss List Archives

[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: (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

[JBoss JIRA] Created: (JBPORTAL-1467) URL's of page's whose <page-name> attribute has ampersand used as an entity (&) is not encoded correctly

by deepashree krishnamurthy (JIRA)

URL's of page's whose <page-name> attribute has ampersand used as an entity (&) is not encoded correctly ------------------------------------------------------------------------------------------------------------ Key: JBPORTAL-1467 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1467 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4.1 Final Environment: All Reporter: deepashree krishnamurthy Assigned To: Julien Viet URL's of page's whose <page-name> attribute has ampersand used as an entity (&) is not encoded correctly. Define a page in *-object.xml eith ampersand in page-name ex: <deployment> <if-exists>overwrite</if-exists> <parent-ref>default</parent-ref> <properties/> <page> <page-name>Auto & Navigator</page-name> : </page> : </deployment> The page is unaccessible on FireFox. Seems that it is not encoded correctly. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-4059) JBoss5 RARDeployer deploys RAR's twice

by Weston Price (JIRA)

JBoss5 RARDeployer deploys RAR's twice -------------------------------------- Key: JBAS-4059 URL: http://jira.jboss.com/jira/browse/JBAS-4059 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Weston Price Assigned To: Weston Price Fix For: JBossAS-5.0.0.Beta2 Because of the new deployment structure in JBoss5, the RAR deployer is now deploying RAR's twice. I assume this has to do with the RARDeployer using a deprecated API of the DeploymentUnit. As a result, the JMX console records deployments such as: # name='jboss-ha-local-jdbc.rar#jboss-ha-local-jdbc.rar',service=RARDeployment # name='jboss-ha-local-jdbc.rar',service=RARDeployment This is causing issues with programmatic deployment, as well as the new metadata repository. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBREM-687) allow binding to 0.0.0.0

by Tom Elrod (JIRA)

allow binding to 0.0.0.0 ------------------------ Key: JBREM-687 URL: http://jira.jboss.com/jira/browse/JBREM-687 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: transport Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta2 (Boon) Need to be able to really bind to 0.0.0.0. Currently, remoting will swap out 0.0.0.0 with local host name or address. Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used. For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding. -- 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, 10 months

2
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-751) ignoreModifications cache loader flag to be extended to all cache loaders, not just ones configured in a chaining cache loader

by Manik Surtani (JIRA)

ignoreModifications cache loader flag to be extended to all cache loaders, not just ones configured in a chaining cache loader ------------------------------------------------------------------------------------------------------------------------------ Key: JBCACHE-751 URL: http://jira.jboss.com/jira/browse/JBCACHE-751 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0, 1.3.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0 -- 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, 10 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 May 2007