December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4293) Support property expansion in redirect-port attribute of the web system's connector

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-4293?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned AS7-4293: -------------------------------- Assignee: Tomaz Cerar (was: Remy Maucherat) > Support property expansion in redirect-port attribute of the web system's connector > ----------------------------------------------------------------------------------- > > Key: AS7-4293 > URL: https://issues.jboss.org/browse/AS7-4293 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.1.Final > Environment: Standalone JBoss AS 7 on RHEL Linux and Windows 7 Enterprise x64 > Reporter: Sven-Jørgen Karlsen > Assignee: Tomaz Cerar > Priority: Optional > Attachments: 04_fix_as_4293.patch > > > The connector element of the web subsystem doesn't support property expansion, forcing you to hardwire the port > number. E.g., writing: > ... > <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host"> > <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" > redirect-port="${jboss.web.https.port}"/> > ... > causes a NumberFormatException. Runtime properties for this attribute was supported in previous versions. > Another problem is that there is no predefined property with the above name. > An alternative solution is to allow a reference to a socket binding groups in the attribute value, as discussed in > http://community.jboss.org/thread/176339 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-941) NPE in ResourceAdapter1516Impl for invalid RAR

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/JBJCA-941?page=com.atlassian.jira.plugin.... ] Philippe Marschall updated JBJCA-941: ------------------------------------- Attachment: JBJCA-941.patch Patch that fixes the issues > NPE in ResourceAdapter1516Impl for invalid RAR > ---------------------------------------------- > > Key: JBJCA-941 > URL: https://issues.jboss.org/browse/JBJCA-941 > Project: IronJacamar > Issue Type: Bug > Components: Common > Affects Versions: 1.0.13.Final > Reporter: Philippe Marschall > Assignee: Jesper Pedersen > Labels: patch > Attachments: JBJCA-941.patch > > > In case of an invalid RAR (JCA 1.6 but not adapter class) you get the following deployment error in JBoss AS. > {code} > 15:38:22,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."sample-application-1.0.0-SNAPSHOT.ear"."sample-adapter-1.0.0-SNAPSHOT.rar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."sample-application-1.0.0-SNAPSHOT.ear"."sample-adapter-1.0.0-SNAPSHOT.rar".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "sample-adapter-1.0.0-SNAPSHOT.rar" of deployment "sample-application-1.0.0-SNAPSHOT.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.8.0-ea] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.8.0-ea] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.8.0-ea] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:185) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.jca.common.metadata.ra.common.ResourceAdapter1516Impl.validate(ResourceAdapter1516Impl.java:351) > at org.jboss.jca.common.metadata.ra.common.ConnectorAbstractmpl.validate(ConnectorAbstractmpl.java:332) > at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:142) > ... 6 more > {code} > It should be a {code}org.jboss.jca.common.api.validator.ValidateException{code} but ends up being a {code}java.lang.NullPointerException{code}. The problem is that {code}ResourceAdapter1516Impl#validate(){code} uses > {code} > this.resourceadapterClass == null > {code} > instead of > {code} > XsdString.isNull(this.resourceadapterClass) > {code} > like {code}#getResourceadapterClass(){code} or the constructor. > {code} > this.resourceadapterClass.getValue() > {code} > then returns {code}null{code} so > {code} > this.resourceadapterClass.getValue().trim() > {code} > throws a {code}NullPointerException{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-941) NPE in ResourceAdapter1516Impl for invalid RAR

by Philippe Marschall (JIRA)

Philippe Marschall created JBJCA-941: ---------------------------------------- Summary: NPE in ResourceAdapter1516Impl for invalid RAR Key: JBJCA-941 URL: https://issues.jboss.org/browse/JBJCA-941 Project: IronJacamar Issue Type: Bug Components: Common Affects Versions: 1.0.13.Final Reporter: Philippe Marschall Assignee: Jesper Pedersen In case of an invalid RAR (JCA 1.6 but not adapter class) you get the following deployment error in JBoss AS. {code} 15:38:22,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."sample-application-1.0.0-SNAPSHOT.ear"."sample-adapter-1.0.0-SNAPSHOT.rar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."sample-application-1.0.0-SNAPSHOT.ear"."sample-adapter-1.0.0-SNAPSHOT.rar".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "sample-adapter-1.0.0-SNAPSHOT.rar" of deployment "sample-application-1.0.0-SNAPSHOT.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.8.0-ea] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.8.0-ea] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.8.0-ea] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:185) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 5 more Caused by: java.lang.NullPointerException at org.jboss.jca.common.metadata.ra.common.ResourceAdapter1516Impl.validate(ResourceAdapter1516Impl.java:351) at org.jboss.jca.common.metadata.ra.common.ConnectorAbstractmpl.validate(ConnectorAbstractmpl.java:332) at org.jboss.as.connector.deployers.ra.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:142) ... 6 more {code} It should be a {code}org.jboss.jca.common.api.validator.ValidateException{code} but ends up being a {code}java.lang.NullPointerException{code}. The problem is that {code}ResourceAdapter1516Impl#validate(){code} uses {code} this.resourceadapterClass == null {code} instead of {code} XsdString.isNull(this.resourceadapterClass) {code} like {code}#getResourceadapterClass(){code} or the constructor. {code} this.resourceadapterClass.getValue() {code} then returns {code}null{code} so {code} this.resourceadapterClass.getValue().trim() {code} throws a {code}NullPointerException{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6100) Support expression for boolean attributes

by Heiko Braun (JIRA)

Heiko Braun created AS7-6100: -------------------------------- Summary: Support expression for boolean attributes Key: AS7-6100 URL: https://issues.jboss.org/browse/AS7-6100 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 it currently uses checkbox inout types -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6099) Include registered attributes with no model representation in read-resource results

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6099?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6099: ---------------------------------- Assignee: (was: Brian Stansberry) > Include registered attributes with no model representation in read-resource results > ----------------------------------------------------------------------------------- > > Key: AS7-6099 > URL: https://issues.jboss.org/browse/AS7-6099 > Project: Application Server 7 > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Brian Stansberry > Priority: Minor > > Following situation: > 1) resource includes attribute xyz > 2) No read-handler is registered for xyz (i.e. default read semantic Resource.getModel().get("xyz") is to be used) > 3) Poorly coded "add" handler for the resource doesn't call model.get("xyz") for some reason. > The effect of this is the read-resource result will not include "xyz" => undefined in the output. Nothing for xyz will appear at all, hiding the existence of the attribute from the caller. > The read-resource handler can deal with a check in its loop through the AttributeAccess registration for the "no read-handler" case. (This check is already there; an 'else' clause is needed.) If no read-handler, see if there is an entry in the directAttributes map for the attribute; if not, add one with a value of new ModelNode(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6099) Include registered attributes with no model representation in read-resource results

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6099: ------------------------------------- Summary: Include registered attributes with no model representation in read-resource results Key: AS7-6099 URL: https://issues.jboss.org/browse/AS7-6099 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management Affects Versions: 7.1.3.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Following situation: 1) resource includes attribute xyz 2) No read-handler is registered for xyz (i.e. default read semantic Resource.getModel().get("xyz") is to be used) 3) Poorly coded "add" handler for the resource doesn't call model.get("xyz") for some reason. The effect of this is the read-resource result will not include "xyz" => undefined in the output. Nothing for xyz will appear at all, hiding the existence of the attribute from the caller. The read-resource handler can deal with a check in its loop through the AttributeAccess registration for the "no read-handler" case. (This check is already there; an 'else' clause is needed.) If no read-handler, see if there is an entry in the directAttributes map for the attribute; if not, add one with a value of new ModelNode(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5798) Third level navigation back link

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/AS7-5798?page=com.atlassian.jira.plugin.s... ] Catherine Robson commented on AS7-5798: --------------------------------------- Thanks Heiko, this looks better. I'll resolve. > Third level navigation back link > -------------------------------- > > Key: AS7-5798 > URL: https://issues.jboss.org/browse/AS7-5798 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Catherine Robson > Labels: uxp > Fix For: 7.2.0.CR1 > > Attachments: Screen Shot 2012-12-06 at 10.10.07 AM.png, Screen Shot 2012-12-06 at 10.10.15 AM.png > > > Third level navigation shows up under the tabbed second level nav- igation with a back link. The back link should be visually different than the tertiary navigation links to help distinguish the different types of action. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5798) Third level navigation back link

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/AS7-5798?page=com.atlassian.jira.plugin.s... ] Catherine Robson resolved AS7-5798. ----------------------------------- Resolution: Done > Third level navigation back link > -------------------------------- > > Key: AS7-5798 > URL: https://issues.jboss.org/browse/AS7-5798 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Catherine Robson > Labels: uxp > Fix For: 7.2.0.CR1 > > Attachments: Screen Shot 2012-12-06 at 10.10.07 AM.png, Screen Shot 2012-12-06 at 10.10.15 AM.png > > > Third level navigation shows up under the tabbed second level nav- igation with a back link. The back link should be visually different than the tertiary navigation links to help distinguish the different types of action. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-2002) Simplify runtime resource registration

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/AS7-2002?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber resolved AS7-2002. -------------------------------------- Fix Version/s: (was: 7.2.0.Alpha1) Resolution: Won't Fix > Simplify runtime resource registration > -------------------------------------- > > Key: AS7-2002 > URL: https://issues.jboss.org/browse/AS7-2002 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Affects Versions: 7.0.0.Final > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > > We need to review and simplify the process of creating and registering runtime resources - to avoid having something like: > https://github.com/jbossas/jboss-as/blob/master/messaging/src/main/java/o... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6095) Expose tatletale management operations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6095?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6095: ---------------------------------- Assignee: (was: Brian Stansberry) > Expose tatletale management operations > -------------------------------------- > > Key: AS7-6095 > URL: https://issues.jboss.org/browse/AS7-6095 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Fix For: Open To Community > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2012