March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6611) EJB Classloader does not distinguish two classes with the same name but from two EJB JARS

by Wen Zhu (JIRA)

EJB Classloader does not distinguish two classes with the same name but from two EJB JARS ----------------------------------------------------------------------------------------- Key: JBAS-6611 URL: https://jira.jboss.org/jira/browse/JBAS-6611 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.0.1.GA Environment: Windows XP, JBossAS 5.0.1 GA with JBoss Web Service (Native Implementation) 3.1.0 Reporter: Wen Zhu Assignee: Scott M Stark We have two EJB Web Services deployed in two separate JARs. In both JAR, there is a class public class MessageObjectProperty { public static final String[] someConstant = new String[] {"some JAR specific value"}; ... ... } When MessageObjectProperty.someConstant is read from the second EJB JAR, it returns defined in the first EJB JAR. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-419) Move @JMX functionality out of jmx-mc-int

by Kabir Khan (JIRA)

Move @JMX functionality out of jmx-mc-int ----------------------------------------- Key: JBMICROCONT-419 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-419 Project: JBoss Microcontainer Issue Type: Feature Request Components: JMX Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossMC-2.2.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6429) StandardBindings unable to start with IBM JDK 1.6 - IllegalArgumentException

by Martin Malina (JIRA)

StandardBindings unable to start with IBM JDK 1.6 - IllegalArgumentException ---------------------------------------------------------------------------- Key: JBAS-6429 URL: https://jira.jboss.org/jira/browse/JBAS-6429 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.0.0.GA Environment: IBM JDK 1.6 (latest release) Reporter: Martin Malina Assignee: Scott M Stark Attachments: ibm16.log JBoss AS is unable to start at all in any configuration, but minimal. The StandardBindings service fails to start with the following error: 13:33:08,459 ERROR [AbstractKernelController] Error installing to Instantiated: name=StandardBindings state=Described java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[int] actual=[java.util.HashSet] at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395) ... Failed to boot JBoss: java.lang.IllegalStateException: Incompletely deployed: *** DEPLOYMENTS IN ERROR: Name -> Error StandardBindings -> java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[int] actual=[java.util.HashSet] *** DEPLOYMENTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} SystemPropertyBinder#1 -> ServiceBindingManager{Installed:Described} SystemPropertyBinder -> SystemPropertyBinder#1{Installed:Described} ServiceBindingManager -> ServiceBindingStore{Installed:Instantiated} ServiceBindingStore -> StandardBindings{Installed:**ERROR**} at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:290) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:174) at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:148) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:394) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:735) The AS instance stops immediately. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-176) Skip an deployer if *all* of the required inputs (for the deployer) are not available

by jaikiran pai (JIRA)

Skip an deployer if *all* of the required inputs (for the deployer) are not available ------------------------------------------------------------------------------------- Key: JBDEPLOY-176 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-176 Project: JBoss Deployers Issue Type: Feature Request Components: deployer Reporter: jaikiran pai Assignee: Ales Justin Consider the following deployer: public class MyDeployer extends AbstractDeployer { public MyDeployer() { addInput(InputOne.class); addInput(InputTwo.class); } } If either of InputOne.class or InputTwo.class is not available in the unit (as an attachment), then skip the deployer from deploying the corresponding unit. Please refer to the referenced forum thread for a discussion about this -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2346) Upgrade to jCaptcha 2 that is not dependent on Sun JVM

by Thomas Heute (JIRA)

Upgrade to jCaptcha 2 that is not dependent on Sun JVM ------------------------------------------------------ Key: JBPORTAL-2346 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2346 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Reporter: Thomas Heute Fix For: 2.8 Final If jCaptcha 2 is out by then... An issue is that today you can use Captcha with OpenJDK for example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2345) User profile portlet shows JSF auto generated id in password field error message

by Takayoshi Kimura (JIRA)

User profile portlet shows JSF auto generated id in password field error message -------------------------------------------------------------------------------- Key: JBPORTAL-2345 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2345 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.7.1 Final Reporter: Takayoshi Kimura Attachments: boot.log, screenshot.png, server.log.zip When input short string for password field it shows error message like this: _jbpns_2fdefault_2fdefault_2fIdentityUserPortletWindowsnpbj:j_id42:register-form:password: Validation Error: Value is less than allowable minimum of '6' Please see attached screenshot and log for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1734) "edit mode" could be checked for authorization

by Thomas Heute (JIRA)

"edit mode" could be checked for authorization ---------------------------------------------- Key: JBPORTAL-1734 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1734 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Reporter: Thomas Heute Assigned To: Julien Viet Fix For: 2.8 Final An admin should be able to define which roles have access to the edit mode for a particular portlet. Since it would break backward compatibility, it has to be part of a major release. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-929) Promiscuous traffic on Mac OS

by Bela Ban (JIRA)

Promiscuous traffic on Mac OS ----------------------------- Key: JGRP-929 URL: https://jira.jboss.org/jira/browse/JGRP-929 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.8 Confirm on Tiger and Leopard whether promiscuous traffic happens. From Manik's mac: Using Leopard (10.5.6) Gemini:Downloads root# java -version java version "1.5.0_16" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-284) Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode, sharing) Gemini:Downloads root# java -jar promiscuoustraffic.jar Listening on address /229.10.11.12 Listening on address /229.10.11.13 Sending 'Hello' on /229.10.11.12:64000 /229.10.11.12:64000 -- Received Hello /229.10.11.13:64000 -- Received Hello Bad news. Detected the Promiscuous Traffic problem. Received Hello on undesired address /229.10.11.13 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1774) Remove StatefulSessionProxy

by Andrew Lee Rubinger (JIRA)

Remove StatefulSessionProxy --------------------------- Key: EJBTHREE-1774 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1774 Project: EJB 3.0 Issue Type: Task Components: proxy-spi Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.1.3 This interface is no longer used, and should not be exposed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1072) Synchronize access to static maps in MarshalFactory

by Ron Sigal (JIRA)

Synchronize access to static maps in MarshalFactory --------------------------------------------------- Key: JBREM-1072 URL: https://jira.jboss.org/jira/browse/JBREM-1072 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP10 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder) Users have experienced the exception org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a valid marshaller for data type: serializable at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:79) 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:67) 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:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107) This is strange, since a marshaller for the datatype "serializable" is hardcoded in org.jboss.remoting.marshal.MarshalFactory. However, access to the static Map marshallers is not synchronized, so it's possible that one subsystem is adding a marshaller (e.g., EJB2, JBossMessaging) at the same time that EJB3 is trying to extract a marshaller. The same observation applies to unmarshallers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
5
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 March 2009