July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMDR-28) Optimize the Signature handling when we already know the "joinpoint" artifact

by Adrian Brock (JIRA)

Optimize the Signature handling when we already know the "joinpoint" artifact ----------------------------------------------------------------------------- Key: JBMDR-28 URL: https://jira.jboss.org/jira/browse/JBMDR-28 Project: JBoss MetaData Repository Issue Type: Task Components: MetaData Affects Versions: JBossMDR-2.0.0.Beta15 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossMDR-2.0.0.CR1 Optimize away Class.findMethod/Constructor/Field and make the getParameter(Types) retrieval lazy. -- 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, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5792) jboss-cache-jdk50.jar missing for default configuration

by Michael Brackx (JIRA)

jboss-cache-jdk50.jar missing for default configuration ------------------------------------------------------- Key: JBAS-5792 URL: https://jira.jboss.org/jira/browse/JBAS-5792 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Michael Brackx Fix For: JBossAS-4.2.3.GA ear working on 4.2.2.GA does not deploy on 4.2.3.GA due to missing jboss-cache-jdk50.jar in default configuration exception: ... Caused by: java.lang.NoClassDefFoundError: org/jboss/cache/CacheException ... workaround: copy jar from all configuration -- 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, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1392) Use the correct MBeanServer if multiple MBeanServers are present.

by Robert Buck (JIRA)

Use the correct MBeanServer if multiple MBeanServers are present. ----------------------------------------------------------------- Key: JBCACHE-1392 URL: https://jira.jboss.org/jira/browse/JBCACHE-1392 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Reporter: Robert Buck Assignee: Manik Surtani The prior bug did not fix the issue of running the cache under jboss when the following options are present: set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote The code is presently as follows (which is incorrect, by the way): {code} 157 List servers=MBeanServerFactory.findMBeanServer(null); 158 if(servers == null || servers.size() == 0) 159 throw new Exception("TreeCacheView.init(): no MBeanServers found"); {code} TreeCacheView fails to deploy because it is using the wrong MBeanServer. Rather than doing the above, you should either do something like: {code} import org.jboss.mx.util.MBeanServerLocator; ... // find the local MBeanServer MBeanServer server = MBeanServerLocator.locateJBoss(); {code} , or you should do something like this: {code} public static MBeanServer getDefaultMBeanServer() { return findMBeanServer("jboss"); } private static MBeanServer findMBeanServer(String agentId) { List servers = MBeanServerFactory.findMBeanServer(null); if (servers != null && servers.size() > 0) { for (Object object : servers) { MBeanServer server = (MBeanServer) object; if (server.getDefaultDomain().equals(agentId)) { return server; } } } return null; } {code} The reason is because with Java 5, when the "-Dcom.sun.management.jmxremote" switch is turned on, the default platform MBeanServer is the zeroth instance rather than "jboss". See: http://fisheye.jboss.com/browse/JBossCache/core/support-branches/1.4.1.SP... To test, deploy the tree cache view, and start JBoss with the JAVA_OPTS mentioned above. -- 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, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1832) -object.xml files should be orderable

by Sylvain FRANCOIS (JIRA)

-object.xml files should be orderable ------------------------------------- Key: JBPORTAL-1832 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1832 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.2 Final Reporter: Sylvain FRANCOIS -object.xml files are loaded without any order rule. This makes mangement of portal/page definitions very difficult with "overwrite" mode since you can't assume if parent has already been loaded or not. It should be easy to fix this (I've made a temporary patch) : descriptors URL are already sorted before parsing, but their parsing results are put in a non-sorted Map (cf. org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext). PS : my -object.xml files follow this structure (all with 'overwrite' mode) : portal-object.xml toppage-x-object.xml (with all its subpages) toppage-y-object.xml (with all its subpages) toppage-z-object.xml (with all its subpages) ... -- 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, 12 months

5
19
0 / 0

[JBoss JIRA] Created: (JBVFS-47) Collapse repeated '/' into a single '/'

by Ales Justin (JIRA)

Collapse repeated '/' into a single '/' --------------------------------------- Key: JBVFS-47 URL: https://jira.jboss.org/jira/browse/JBVFS-47 Project: JBoss VFS Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.Beta20 Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.0.0.CR1 There is no such thing as an empty, nameless directory in the vfs so repeated '/' should be collapsed into a single '/' by the tokenizer. -- 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, 12 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-3019) Add support for CRL validation to the certificate based login modules

by Anil Saldhana (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3019?page=com.atlassian.jira.plug... ] Anil Saldhana commented on JBAS-3019: ------------------------------------- An use case : http://www.jboss.com/index.html?module=bb&op=viewtopic&t=139585 > Add support for CRL validation to the certificate based login modules > --------------------------------------------------------------------- > > Key: JBAS-3019 > URL: https://jira.jboss.org/jira/browse/JBAS-3019 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Reporter: Scott M Stark > Assignee: Anil Saldhana > > We need to add support for validating certificates against certificate revocation lists (CRLs). -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2080) Page restriction improvement

by Thomas Heute (JIRA)

Page restriction improvement ---------------------------- Key: JBPORTAL-2080 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2080 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.6 Final Reporter: Thomas Heute Assignee: Sohil Shah Say you have a portal named A *restricted* to everybody Say that on this portal you have a page B which is the default page, with *read* permission to everybody Accessing: http://localhost:8080/portal/portal/A/B will be granted since B can be read http://localhost:8080/portal/portal/A will not be granted since A cannot be read (even though it would show page B since it's the default page) The behavior is understandable, but a bit weird when used. We should define: - Do we need all parents (recursively) to be readable to read a certain page ? or - Do we just check the final node ? In that case we should still check access to the default page of a portal This could be configurable in config.xml -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2068) WSRP Producer does not throw InvalidRegistration when a Consumer does not provide registration information when registration is required

by Chris Laprun (JIRA)

WSRP Producer does not throw InvalidRegistration when a Consumer does not provide registration information when registration is required ---------------------------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-2068 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2068 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 Alpha1, 2.6.5 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.6 Final, 2.7.0 Beta1 -- 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, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5794) Administration and configuration guide

by samson kittoli (JIRA)

Administration and configuration guide -------------------------------------- Key: JBAS-5794 URL: https://jira.jboss.org/jira/browse/JBAS-5794 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Reporter: samson kittoli Fix For: JBossAS-5.0.0.CR2, JBossAS-5.0.0.GA -- 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, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-133) LDAP LoginModule for just roles query.

by Darran Lofthouse (JIRA)

LDAP LoginModule for just roles query. -------------------------------------- Key: SECURITY-133 URL: http://jira.jboss.com/jira/browse/SECURITY-133 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse SPNEGO authentication only identifies the user not their roles. -- 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, 12 months

1
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 July 2008