June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3611) Find better solution to AS7-2815 than using EnumValidator to store the allowed value

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3611: ------------------------------------- Summary: Find better solution to AS7-2815 than using EnumValidator to store the allowed value Key: AS7-3611 URL: https://issues.jboss.org/browse/AS7-3611 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Fix For: 7.2.0.Alpha1 AS7-2815 solution uses a hack in EnumValidator to store the allowed value instead of the user provided value. That goes beyond the contract of a "validate" method. See if something better can be found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-4437) Pls add a dmr handler to add and remove a single environment variable

by Michael Voegele (JIRA)

Michael Voegele created AS7-4437: ------------------------------------ Summary: Pls add a dmr handler to add and remove a single environment variable Key: AS7-4437 URL: https://issues.jboss.org/browse/AS7-4437 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Michael Voegele Assignee: Brian Stansberry For adding a single jvm-option, operations exist for convenience: add-jvm-option remove-jvm-option The same would be good for environment variables: add-environment-variable remove-environment-variable At the moment, the same can only be achieved by writing the whole attribute environment-variables, which does not allow to add a *single* variable (if some already exist, the existing ones have to be included when writing the attribute): {code:xml} { "operation" => "write-attribute", "address" => [ ("host" => "master"), ("server-config" => "server-1"), ("jvm" => "default") ], "name" => "environment-variables", "value" => [ {"foo1" => "bar1"}, {"foo2" => "bar2"} ] } {code} Operations write-attribute and undefine-attribute have to be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
7
0 / 0

[JBoss JIRA] (AS7-3739) Add local-only web cache container to enable session persistence in non-HA environments

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3739: --------------------------------- Summary: Add local-only web cache container to enable session persistence in non-HA environments Key: AS7-3739 URL: https://issues.jboss.org/browse/AS7-3739 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] (AS7-4353) Upgrade JavaMail to 1.4.5

by Julio Pires (JIRA)

Julio Pires created AS7-4353: -------------------------------- Summary: Upgrade JavaMail to 1.4.5 Key: AS7-4353 URL: https://issues.jboss.org/browse/AS7-4353 Project: Application Server 7 Issue Type: Library Upgrade Reporter: Julio Pires Release notes: http://www.oracle.com/technetwork/java/javamail145changes-1562616.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] (AS7-4793) Convert ConfigAdmin subsystem to ResourceDefinition

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4793: -------------------------------- Summary: Convert ConfigAdmin subsystem to ResourceDefinition Key: AS7-4793 URL: https://issues.jboss.org/browse/AS7-4793 Project: Application Server 7 Issue Type: Sub-task Components: ConfigAdmin Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Tomaz Cerar Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 Convert ConfigAdmin subsystem to use ResourceDefinition and AttributeDefinition -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (AS7-1459) Add a commandline flag to the startup script to enable debugging

by Dan Allen (JIRA)

Add a commandline flag to the startup script to enable debugging ---------------------------------------------------------------- Key: AS7-1459 URL: https://issues.jboss.org/browse/AS7-1459 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.0.0.Final Reporter: Dan Allen Assignee: Alexey Loubyansky The startup script (standalone.sh & standalone.bat) should honor a commandline option that can be used to start the server with debugging enabled. Currently, the developer has to uncomment the JAVA_OPTS line in the standalone.conf file manually. Proposal for starting the server with debugging enabled: ./bin/standalone.sh --debug If necessary, the optional flag could accept the port as an optional argument. ./bin/standalone.sh --debug 8787 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

6
9
0 / 0

[JBoss JIRA] (AS7-4461) Operation transformation infrastructure

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4461: ------------------------------------- Summary: Operation transformation infrastructure Key: AS7-4461 URL: https://issues.jboss.org/browse/AS7-4461 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.2.Final-redhat1 Ability for extensions to register operation transformers. (This will likely be part of the resource transformation task AS7-4457.) Hooks to access that transformation registry during operation execution. This is to include: 1) Host level operations that target the slave HC directly but are proxied by the master HC. 2) Server level operations that target the slave HC's servers directly but are proxied by the master HC. 3) The first phase of domain-wide 2 phase operations where the master HC transmits the op to the slave HCs. 4) The second phase of domain-wide 2 phase operations where the master HC transmits server-level ops to the slave HCs for forwarding to their servers. Item 4) above may be simple, as all the master HC is doing is executing ops according to instructions provided by the slave HCs in step 3). Those instructions will be correct for that slave HC. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] (AS7-4832) Undeployment from a subfolder of deployments folder not working

by Jan Reznik (JIRA)

Jan Reznik created AS7-4832: ------------------------------- Summary: Undeployment from a subfolder of deployments folder not working Key: AS7-4832 URL: https://issues.jboss.org/browse/AS7-4832 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Environment: Windows XP Reporter: Jan Reznik I cannot undeploy a jar from a subdirectory of deployments folder by deleting *.deployed file. *.undeployed is created in deployments folder, not in the subfolder, causing Deploy Scanner to immediately deploy my jar again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] (AS7-5028) ability to removethe response-header Server:Apache-Coyote/1.1

by nimo stephan (JIRA)

nimo stephan created AS7-5028: --------------------------------- Summary: ability to removethe response-header Server:Apache-Coyote/1.1 Key: AS7-5028 URL: https://issues.jboss.org/browse/AS7-5028 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.1.Final Reporter: nimo stephan Jboss AS 7 includes the following HTTP-Header for every response: Server:Apache-Coyote/1.1 For security issues, it is good to hide this header so attackers cannot easily derivate its underlying technology (which, in this case, indicates that Java-Technology/Tomcat is used). Possible solutions is: Invent a new system-property "org.jboss.as.sendServerHeader" which can be set, for example, in standalone.xml: <system-properties> <property name="org.apache.coyote.http11.Http11Protocol.SERVER" value=""/> <property name="org.jboss.as.sendServerHeader" value="false"/> </system-properties> Note: - leaving the value of "org.apache.coyote.http11.Http11Protocol.SERVER" results in printing the Server-Header also, instead of to go away. However, with that value I can rename the Server-Header, but not deleting it. - At first, I have thought this is a JSF-Rendering-Issue, so I created that issue here http://java.net/jira/browse/JAVASERVERFACES-2445, but it stated out that printing the Server-Header is a "application server level concern". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] (AS7-4673) Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property

by Roger S (JIRA)

Roger S created AS7-4673: ---------------------------- Summary: Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property Key: AS7-4673 URL: https://issues.jboss.org/browse/AS7-4673 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Environment: Red Hat Enterprise Linux Server release 5.7, JDK 7 Reporter: Roger S I found that when the following is set in the standalone.xml of JBoss-7.1.1.Final, it will have a fatal error: <xa-datasource....> .... <xa-datasource-property name="ConnectionProperties">SetBigStringTryClob=true</xa-datasource-property> .... </xa-datasource> The error is: Caused by: javax.resource.ResourceException: No property editor found for type: class java.util.Properties at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:601) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:430) When I don't define the SetBigStringTryClob setting, all is fine. However, the SetBigStringTryClob is really important for the application to work correctly. Hope there's at least a workaround. This worked without problems in JBoss 4.2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
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 June 2012