June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-383) Document isntrumentation modes

by Flavia Rainone (JIRA)

Document isntrumentation modes ------------------------------ Key: JBAOP-383 URL: http://jira.jboss.com/jira/browse/JBAOP-383 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Flavia Rainone Fix For: 2.0.0.alpha5 We need to document instrumentation modes. -- 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, 8 months

2
14
0 / 0

[JBoss JIRA] Created: (JBAS-3544) org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable

by Jaroslaw Kijanowski (JIRA)

org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable ------------------------------------------------------------------------------------------------------------ Key: JBAS-3544 URL: http://jira.jboss.com/jira/browse/JBAS-3544 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Environment: win xp Reporter: Jaroslaw Kijanowski Fix For: JBossAS-5.0.0.Beta org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails because the services jbossweb-tomcat55.sar and jboss-aop.deployer can't be registered, becasue in JB5.0 they changed their names to jbossweb-tomcat6.sar and jboss-aop-jdk50.deployer. FIX: change testsuite/src/main/org/jboss/test/management/test/DeploymentDescriptorUnitTestCase.java . . . public void testGetSarDescriptor() throws Exception { // String moduleName = "jbossweb-tomcat55.sar"; String moduleName = "jbossweb-tomcat6.sar"; . . . public void testGetDeployerDescriptor() throws Exception { // String moduleName = "jboss-aop.deployer"; String moduleName = "jboss-aop-jdk50.deployer"; -- 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, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-4410) JaasSecurityDomain settings need to be sent to SecurityConfiguration

by Anil Saldhana (JIRA)

JaasSecurityDomain settings need to be sent to SecurityConfiguration -------------------------------------------------------------------- Key: JBAS-4410 URL: http://jira.jboss.com/jira/browse/JBAS-4410 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 SECURITY-26 has a need for the MBean services and other security related integration aspects for the JBAS to get back into the AS workspace. I see an issue with the Ldapxxx login modules having a reliance on the DecodeAction privileged action, that internally used to call the JaasSecurityDomain mbean service to decode a b64 string. Now since the JaasSecurityDomain mbean service was the central source of the various jsse/crypto settings, we need to get away from this model and use the static SecurityConfiguration as the sink for the security settings. This static SecurityConfiguration can be populated from JaasSecurityDomain Mbean service, the security deployer or wherever. There certainly has to be a better way than the static SecuriytConfiguration. For now, it is sufficient. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1057) Create/update DTD/schemas for descriptors.

by Chris Laprun (JIRA)

Create/update DTD/schemas for descriptors. ------------------------------------------ Key: JBPORTAL-1057 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1057 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Roy Russo Priority: Minor Fix For: 2.4.1 Final -- 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, 8 months

7
11
0 / 0

[JBoss JIRA] Created: (JBAS-3918) jbossweb virtual-host processing not working

by Scott M Stark (JIRA)

jbossweb virtual-host processing not working -------------------------------------------- Key: JBAS-3918 URL: http://jira.jboss.com/jira/browse/JBAS-3918 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Scott M Stark Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.Beta2 Add a Host entry to the deployers/jbossweb.deployer/server.xml as described in the 4.0.x section of: http://wiki.jboss.org/wiki/Wiki.jsp?page=VirtualHosts for example: <Host name="succubus-vhost" autoDeploy="false" deployOnStartup="false" deployXML="false"> <Valve className="org.apache.catalina.valves.AccessLogValve" prefix="succubus-vhost" suffix=".log" pattern="common" directory="${jboss.server.home.dir}/log"/> </Host> add a virtual-host entry to the jmx-console.war/WEB-INF/jboss-web.xml: <jboss-web> <virtual-host>succubus-vhost</virtual-host> </jboss-web> and try to access the jmx-console using succubus-vhost: [starksm@succubus Security]$ wget http://succubus-vhost:8080/jmx-console/index.jsp --08:21:41-- http://succubus-vhost:8080/jmx-console/index.jsp => `index.jsp' Resolving succubus-vhost... 192.168.10.10 Connecting to succubus-vhost|192.168.10.10|:8080... connected. HTTP request sent, awaiting response... 400 No Host matches server name succubus-vhost 08:21:41 ERROR 400: No Host matches server name succubus-vhost. -- 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, 8 months

7
10
0 / 0

[JBoss JIRA] Created: (JBAS-4456) Replace JRMPProxyService with a remoting based bean.

by Scott M Stark (JIRA)

Replace JRMPProxyService with a remoting based bean. ---------------------------------------------------- Key: JBAS-4456 URL: http://jira.jboss.com/jira/browse/JBAS-4456 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Remoting Reporter: Scott M Stark Assigned To: Ron Sigal Fix For: JBossAS-5.0.0.Beta3 We need a pojo component that generates aop remoting proxies given a target and exposed interfaces, client aspects. -- 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, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1223) Look into the new JackRabbit release and its clustering support

by Sohil Shah (JIRA)

Look into the new JackRabbit release and its clustering support --------------------------------------------------------------- Key: JBPORTAL-1223 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1223 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6 Final Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6 Final -- 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, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1324) Multiple portals / custom url : set the default portal name

by Antoine Herzog (JIRA)

Multiple portals / custom url : set the default portal name ----------------------------------------------------------- Key: JBPORTAL-1324 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1324 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Environment: JBoss Portal 2.4.0 final Reporter: Antoine Herzog Assigned To: Julien Viet Here the code of the jmx service class public class ConfigurableDefaultPortalCommandFactory extends DefaultPortalCommandFactory { private static final Log logger = LogFactory .getLog(ConfigurableDefaultPortalCommandFactory.class); /** * The JMX attribute for default portal name. */ private String defaultPortalName; /** * */ public ConfigurableDefaultPortalCommandFactory() { super(); } /* * (non-Javadoc) * * @see org.jboss.portal.core.model.portal.DefaultPortalCommandFactory#doMapping(org.jboss.portal.server.ServerInvocation, * java.lang.String, java.lang.String) */ public ControllerCommand doMapping(ServerInvocation invocation, String portalContextPath, String portalRequestPath) { // orginal code : ControllerCommand cmd = // nextFactory.doMapping(invocation, ControllerCommand cmd = getNextFactory().doMapping(invocation, portalContextPath, portalRequestPath); if (cmd == null) { // orginal code : Context ctx = container.getContext(); Context ctx = getContainer().getContext(); if (ctx == null) { throw new IllegalStateException( "Default context does not exist"); } // orginal code : Portal portal = ctx.getDefaultPortal(); PortalObject portalObject = ctx.getChild(getDefaultPortalName()); if (portalObject == null) { throw new IllegalStateException( "PortalObject as Default Portal is not found. Default Portal name is defined to : " + getDefaultPortalName()); } Portal portal = null; if (portalObject instanceof Portal) { portal = (Portal) portalObject; } else { throw new IllegalStateException( "Can't find PortalObject with default portal name : " + getDefaultPortalName()); } // if (portal == null) { // throw new IllegalStateException("Default portal does not exist"); // } Page page = portal.getDefaultPage(); if (page == null) { throw new IllegalStateException("Default page does not exist"); } String handle = page.getId(); cmd = new RenderPageCommand(handle); } return cmd; } /** * The JMX attribute for default portal name. * * @return the defaultPortalName */ public String getDefaultPortalName() { return this.defaultPortalName; } /** * The JMX attribute for default portal name. * * @param defaultPortalName * the defaultPortalName to set */ public void setDefaultPortalName(String defaultPortalName) { this.defaultPortalName = defaultPortalName; } /** * Call the super method first, then check the {@link #defaultPortalName} is * not null and not "". Throw an exception if so. */ protected void createService() throws Exception { super.createService(); if (getDefaultPortalName() == null || getDefaultPortalName().compareTo("") == 0) { throw new Exception( "The attribute DefaultPortalName can't be null or empty string. Set it in the JMX service descriptor."); } } /* * (non-Javadoc) * * @see org.jboss.system.ServiceMBeanSupport#startService() */ @Override protected void startService() throws Exception { logger.info(this.getName() + " service starting. Default portal name : getDefaultPortalName() = "+getDefaultPortalName()); super.startService(); } /* * (non-Javadoc) * * @see org.jboss.system.ServiceMBeanSupport#stopService() */ @Override protected void stopService() throws Exception { super.stopService(); logger.info(this.getName() + " service stoping."); } } And add the attribute in the jmx service descriptor :  <attribute name="DefaultPortalName">MyDefaultPortalNameHere</attribute> -- 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, 8 months

4
17
0 / 0

[JBoss JIRA] Created: (JBAOP-430) ConcurrentModificationException in JoinpointSimpleClassifier.classifyJoinpoint

by Bart Vanhaute (JIRA)

ConcurrentModificationException in JoinpointSimpleClassifier.classifyJoinpoint ------------------------------------------------------------------------------ Key: JBAOP-430 URL: http://jira.jboss.com/jira/browse/JBAOP-430 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.5.5.GA Environment: JBossAS 4.2.0.GA Sun JDK 1.5.0_11 (build 1.5.0_11-b03) Reporter: Bart Vanhaute Priority: Minor With Load time weaving enabled, a ConcurrentModificationException is printed out in the jboss log output (probably a e.printStackTrace() somewhere). Luckily, the code that I want AOP interceptors applied to is indeed woven. So this is not a big issue for me (at the moment). -- 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, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (JBAS-4192) Evaluate having ProxyFactoryFinderInterceptor clear the ProxyFactory ThreadLocal on request exit

by Brian Stansberry (JIRA)

Evaluate having ProxyFactoryFinderInterceptor clear the ProxyFactory ThreadLocal on request exit ------------------------------------------------------------------------------------------------ Key: JBAS-4192 URL: http://jira.jboss.com/jira/browse/JBAS-4192 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry On the way in, ProxyFactoryFinderInterceptor invokes Container.setProxyFactory, which in turn sets a ThreadLocal. On the way out there is no corresponding call that clears the ThreadLocal. Effect is the ProxyFactory leaks to the thread. Need to confirm that clearing the TL on each request doesn't cause issues. -- 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, 8 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 June 2007