October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-720) Clips Parser

by Mark Proctor (JIRA)

Clips Parser ------------ Key: JBRULES-720 URL: http://jira.jboss.com/jira/browse/JBRULES-720 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m2 Clips Parser -- 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

16 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4571) local ant config upsets junit spawns in test build

by Andrew Dinn (JIRA)

local ant config upsets junit spawns in test build -------------------------------------------------- Key: JBAS-4571 URL: http://jira.jboss.com/jira/browse/JBAS-4571 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Reporter: Andrew Dinn The build.sh script should insert --no_config into ANT_OPTIONS before invoking ant. Otherwise when the user has an ant.conf in $HOME/.ant or there is an ant.conf in /etc this can mess up the creation of junit tasks defined in build.xml -- 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

16 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4478) ignore local ant options when building

by Dennis Gregorovic (JIRA)

ignore local ant options when building -------------------------------------- Key: JBAS-4478 URL: http://jira.jboss.com/jira/browse/JBAS-4478 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Build System Affects Versions: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.4.GA Reporter: Dennis Gregorovic Assigned To: Rajesh Rajasekaran Priority: Minor build/build.sh should use --noconfig when invoking Ant so that the local Ant libraries and configurations do not get picked up. -- 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

16 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4918) for logging, server.xml references another variable than jboss-log4j.xml does

by Jon Stevens (JIRA)

for logging, server.xml references another variable than jboss-log4j.xml does ----------------------------------------------------------------------------- Key: JBAS-4918 URL: http://jira.jboss.com/jira/browse/JBAS-4918 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-4.2.0.GA Environment: all Reporter: Jon Stevens Assigned To: Scott M Stark jboss-log4j.xml has this as default: <param name="File" value="${jboss.server.log.dir}/server.log"/> jboss-web.deployer has this:  <Valve className="org.apache.catalina.valves.AccessLogValve" prefix="localhost_access_log." suffix=".log" pattern="common" directory="${jboss.server.home.dir}/log" resolveHosts="false" /> Now, because those two variables are different, I can't easily setup logging to say /var/log/jboss because #1. there is two different variables to define: ${jboss.server.home.dir} and ${jboss.server.log.dir} #2. the access logger has /log hard coded to the end of the directory attribute which makes it impossible to set the two variables to the same value. My preference would be that the default is made to a single variable ${jboss.server.log.dir} which can control everything. jon -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-120) Add support for an LRU cache to CachingMetaDataContext

by Adrian Brock (JIRA)

Add support for an LRU cache to CachingMetaDataContext ------------------------------------------------------ Key: JBMICROCONT-120 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-120 Project: JBoss MicroContainer Issue Type: Feature Request Components: MetaData Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The CachingMetaDataContext caches values indefinitely. Support for some kind of LRUCache (maybe across contexts) will help to relieve memory pressure when for example the metadata is actually only retrieved once and used at deployment. -- 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

16 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBJMX-108) Provide JAAS credentials in org.jboss.ant.JMX task so that calls can be made to security protected MBeans.

by Michael Small (JIRA)

Provide JAAS credentials in org.jboss.ant.JMX task so that calls can be made to security protected MBeans. ---------------------------------------------------------------------------------------------------------- Key: JBJMX-108 URL: http://jira.jboss.com/jira/browse/JBJMX-108 Project: JBoss JMX Issue Type: Feature Request Reporter: Michael Small I have MBeans (using the @Security and @Management annotations) that are associated with a security domain. It would great if the JBoss JMX Ant Task was enhanced to accept a username and password for JAAS security. -- 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

16 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4448) Properties MBean attribues don't update properly

by John Mazzitelli (JIRA)

Properties MBean attribues don't update properly ------------------------------------------------ Key: JBAS-4448 URL: http://jira.jboss.com/jira/browse/JBAS-4448 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.GA Reporter: John Mazzitelli Priority: Minor I have this in my jboss-service.xml for a custom MBean that has a Properties attribute: <attribute name="ConfigurationOverrides" serialDataType="jbxb"> <java:properties xmlns:java="urn:jboss:java-properties" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd"> <java:property> <java:key>my-data-directory</java:key> <java:value>${jboss.server.data.dir}/subdir</java:value> </java:property> ... and more java:property definitions ... I have other non-Properties attributes in my MBean as well. This works fine when starting up. My MBean's setConfigurationOverrides(Properties p) method is called with proper values and everything works. However, if I go to the JMX console, and edit one of my other attributes (simple String attribute), it seems my Properties attribute gets hosed - its values are all screwed up. -- 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

16 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4589) Upgrade to JSF RI 1.2_05

by Juergen Zimmermann (JIRA)

Upgrade to JSF RI 1.2_05 ------------------------ Key: JBAS-4589 URL: http://jira.jboss.com/jira/browse/JBAS-4589 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Juergen Zimmermann FYI: I ran my testsuite with JSF 1.2_05 RC1 and hadn't any problems. The release notes can be found at https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_05/changelog.html Citation: "Another change which may impact applications is that we've merged all ServletContextListeners into one listener. In 1.2_04, we had three separate listeners. If a container wasn't compliant in invoking listeners defined in a TLD, the developer had to know all three of these. It seemed to have been a mistake to have so many. The only listener to worry about at this point is com.sun.faces.config.ConfigureListener." ConfigureListener is just being used in org/jboss/web/jsf/integration/config/JBossJSFConfigureListener.java So everything looks fine. -- 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

16 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-717) Introduce JBoss-specific replication-only events that actually let you directly write/read the bytestream

by Ben Wang (JIRA)

Introduce JBoss-specific replication-only events that actually let you directly write/read the bytestream --------------------------------------------------------------------------------------------------------- Key: EJBTHREE-717 URL: http://jira.jboss.com/jira/browse/EJBTHREE-717 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Ben Wang Again, per email discussion. Idea is to let user has a fuller control of how replication process should be for sfsb. -- 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

16 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4732) Multihome support: HAJNDI`s HANamingServiceMBean needs a configurable RmiBindAddress (like Naming`s MainMBean)

by Thomas Wenckebach (JIRA)

Multihome support: HAJNDI`s HANamingServiceMBean needs a configurable RmiBindAddress (like Naming`s MainMBean) -------------------------------------------------------------------------------------------------------------- Key: JBAS-4732 URL: http://jira.jboss.com/jira/browse/JBAS-4732 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.0.3 SP1 Reporter: Thomas Wenckebach Assigned To: Brian Stansberry For multihomed servers, it is essential to be able to bind JBoss services to dedicated interfaces (bind address). This requirement is not fulfilled HAJNDI. Affected source files: $JBOSS_SRC/cluster/src/main/org/jboss/ha/jndi/HANamingServiceMBean.java $JBOSS_SRC/cluster/src/main/org/jboss/ha/jndi/HANamingService.java -- 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

16 years, 6 months

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007