December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-308) Upgrade commons-logging from 1.0.3 to 1.1.0

by Bela Ban (JIRA)

Upgrade commons-logging from 1.0.3 to 1.1.0 ------------------------------------------- Key: JGRP-308 URL: http://jira.jboss.com/jira/browse/JGRP-308 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 Needs some testing -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3936) 'Class does not expose a management interface:' class will allways be java.lang.Object

by Hugo Hallman (JIRA)

'Class does not expose a management interface:' class will allways be java.lang.Object -------------------------------------------------------------------------------------- Key: JBAS-3936 URL: http://jira.jboss.com/jira/browse/JBAS-3936 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.5.GA Environment: Any Reporter: Hugo Hallman Assigned To: Scott M Stark Priority: Trivial The error message given when deploying a non-jmx bean will allways be: "Class does not expose a management interface: java.lang.Object", and should instead obviously be mentioning the given implementation class. The problem is that when looping down the object hierarchy to find a JMX compatible class, the requested class is forgotten for the error message. Proposed solution: \jboss-4.0.4.GA-src.tar\jboss-4.0.4.GA-src\jmx\src\main\org\jboss\mx\metadata\MBeanCapability.java (Problem remains in 4.0.5.GA: http://fisheye.jboss.com/browse/JBossAS/tags/JBoss_4_0_5_GA/jmx/src/main/...) // If the MyClass MBean is an instance of a MyClassMBean interface, MyClass is a standard MBean for(Class current = mbeanClass; current != null; current = current.getSuperclass()) { Class [] interfaces = current.getInterfaces(); for (int i = 0; i < interfaces.length; i++) { Class anInterface = interfaces[i]; if (anInterface.getName().equals(current.getName() + "MBean")) { return new MBeanCapability(STANDARD_MBEAN); } } } throw new NotCompliantMBeanException("Class does not expose a management interface: " + mbeanClass.getName()); Note that the proposed solution has NOT been tested. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-368) Port anycasting from 2.4.1 to CVS head (2.5)

by Bela Ban (JIRA)

Port anycasting from 2.4.1 to CVS head (2.5) -------------------------------------------- Key: JGRP-368 URL: http://jira.jboss.com/jira/browse/JGRP-368 Project: JGroups Issue Type: Task Affects Versions: 2.4.1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3560) shutdown.sh fails because it cannot find org/jboss/logging/Logger

by Ovidiu Feodorov (JIRA)

shutdown.sh fails because it cannot find org/jboss/logging/Logger ----------------------------------------------------------------- Key: JBAS-3560 URL: http://jira.jboss.com/jira/browse/JBAS-3560 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta Reporter: Ovidiu Feodorov Priority: Minor org/jboss/logging/Logger is no longer shipped with jbossall-client.jar, so the shutdown script fails: $ ./shutdown.sh -S Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jnp.interfaces.NamingContext.<clinit>(NamingContext.java:159) .... -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-931) jBPM Integration for CMS

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-931?page=all ] Sohil Shah updated JBPORTAL-931: -------------------------------- Fix Version/s: 2.6.Alpha1 > jBPM Integration for CMS > ------------------------ > > Key: JBPORTAL-931 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-931 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6 Final > Reporter: Roy Russo > Assigned To: Sohil Shah > Fix For: 2.6.Alpha1 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-730) "Copy" should copy the live revision

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-730?page=all ] Roy Russo updated JBPORTAL-730: ------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) Affects Version/s: 2.6.Beta1 (was: 2.2 Branch) Assignee: Roy Russo (was: Sohil Shah) > "Copy" should copy the live revision > ------------------------------------ > > Key: JBPORTAL-730 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-730 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6.Beta1 > Reporter: Thomas Heute > Assigned To: Roy Russo > Fix For: 2.6.Beta1 > > > The current "copy" feature using Jackrabbit Workspace.copy() seems to copy the latest revision and only that one. > Jackrabbit implementation won't help here (since it should be faster to do it at this level) > If we decide to copy a unique revision we should copy the Live version. (can be different from the latest) > Now the question is: should we copy all revisions or only the live one ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1151) jboss:service=DefaultPartition hardcoded in CMS cluster config

by Poul Bildsoee Moeller (JIRA)

jboss:service=DefaultPartition hardcoded in CMS cluster config -------------------------------------------------------------- Key: JBPORTAL-1151 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1151 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4.1 Final Reporter: Poul Bildsoee Moeller Assigned To: Roy Russo Priority: Minor Fix For: 2.4.1 Final When naming my own cluster partition I found that the default name had been hardcoded once in the CMS cluster configuration: In jboss-portal-ha.sar/portal-cms.sar/META-INF/jboss-service.xml The part: <mbean code="org.jboss.portal.jems.ha.HASingletonInvoker" name="portal:service=HASingletonInvoker,type=CMS"> <depends>jboss:service=DefaultPartition</depends> <attribute name="RetryWaitingTimeMS">2000</attribute> <attribute name="MaxRetries">5</attribute> <attribute name="JNDIName">MyServiceInvokeTarget</attribute> <attribute name="JNDIProperties"> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=${jboss.bind.address:localhost}:1100 jnp.disableDiscovery=false jnp.partitionName=${jboss.partition.name:DefaultPartition} jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4} jnp.discoveryPort=1102 jnp.discoveryTTL=16 jnp.discoveryTimeout=5000 jnp.maxRetries=1 </attribute> <depends optional-attribute-name="Callback" proxy-type="attribute">portal:service=CMS</depends> <depends optional-attribute-name="ProxyFactory">portal:service=ProxyFactory,type=CMS</depends> </mbean> where jboss:service=DefaultPartition should be replaced by: jboss:service=${jboss.partition.name:DefaultPartition} -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-528) Management portlet creating inaccessible instance with empty name field

by Boleslaw Dawidowicz (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-528?page=all ] Boleslaw Dawidowicz resolved JBPORTAL-528. ------------------------------------------ Resolution: Duplicate Issue > Management portlet creating inaccessible instance with empty name field > ----------------------------------------------------------------------- > > Key: JBPORTAL-528 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-528 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2 Final > Reporter: Boleslaw Dawidowicz > Assigned To: Julien Viet > Priority: Minor > Fix For: 2.6.Alpha1 > > > as in forum post: > "From the management portlet (page view), I clicked the button "Add instance" without entering anything in the text field. It created a blank portlet window. Since it has no names, there are no links associated with it. As a result, I can't delete it." -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-718) Expose monitoring informations for JBoss ON

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-718?page=all ] Julien Viet resolved JBPORTAL-718. ---------------------------------- Resolution: Done > Expose monitoring informations for JBoss ON > ------------------------------------------- > > Key: JBPORTAL-718 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-718 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.6 Final > Reporter: Julien Viet > Fix For: 2.6.Alpha1 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-677) Secure Portlet Modes

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-677?page=all ] Julien Viet updated JBPORTAL-677: --------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) > Secure Portlet Modes > -------------------- > > Key: JBPORTAL-677 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-677 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.4 Final, 2.2 Branch > Reporter: Jouni Rajala > Fix For: 2.6.Beta1 > > > Request for feature that allows me to secure portlet mode per User's Role. I need this to prevent anonymous and 'normal' users to customize portlets while allowing advanced users to enter into edit mode. > For me this feature is blocker, because I can't deploy my application to JBoss portal if modes can't be secured. -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006