December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6089) CLI module command should not require --resources if --module-xml is specified.

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/AS7-6089?page=com.atlassian.jira.plugin.s... ] Stan Silvert updated AS7-6089: ------------------------------ Fix Version/s: 7.1.4.Final (EAP) Git Pull Request: https://github.com/jbossas/jboss-as/pull/3586, https://github.com/jbossas/jboss-as/pull/3601 (was: https://github.com/jbossas/jboss-as/pull/3586) > CLI module command should not require --resources if --module-xml is specified. > ------------------------------------------------------------------------------- > > Key: AS7-6089 > URL: https://issues.jboss.org/browse/AS7-6089 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI > Affects Versions: 7.1.3.Final (EAP) > Reporter: Stan Silvert > Assignee: Stan Silvert > Labels: cli > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) > > > It is perfectly legitimate to have a module without resources. The module.xml can specify no resources or even specify resources in another module. > So, if creating a module with a custom module.xml, --resources should not be a required field. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6117) CLI module command leaves out slot in generated module.xml

by Stan Silvert (JIRA)

Stan Silvert created AS7-6117: --------------------------------- Summary: CLI module command leaves out slot in generated module.xml Key: AS7-6117 URL: https://issues.jboss.org/browse/AS7-6117 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.3.Final (EAP) Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) If you execute a CLI module command with the --slot option and you allow CLI to auto-generate the module.xml file, it leaves the "slot" attribute out of the generated XML. module add --name=foo --slot=bar --resources=my.jar Currently generates: {code:xml} <?xml version="1.0" ?> <module xmlns="urn:jboss:module:1.1" name="foo"> <resources> <resource-root path="my.jar"/> </resources> </module> {code} Should be {code:xml} <?xml version="1.0" ?> <module xmlns="urn:jboss:module:1.1" name="foo" slot="bar"> <resources> <resource-root path="my.jar"/> </resources> </module> {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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-55) Encoding is not written out to the logging.properties file

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-55?page=com.atlassian.jira.plugin.... ] James Perkins commented on LOGMGR-55: ------------------------------------- Pull request sent https://github.com/jboss-logging/jboss-logmanager/pull/6 for master and https://github.com/jboss-logging/jboss-logmanager/pull/10 for 3.1 > Encoding is not written out to the logging.properties file > ---------------------------------------------------------- > > Key: LOGMGR-55 > URL: https://issues.jboss.org/browse/LOGMGR-55 > Project: JBoss Log Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.3.3.Final, 1.4.0.Beta1 > > > When a handler defines an encoding and the logging.properties is written out via the PropertyConfigurator the encoding attribute is not written out. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-55) Encoding is not written out to the logging.properties file

by James Perkins (JIRA)

James Perkins created LOGMGR-55: ----------------------------------- Summary: Encoding is not written out to the logging.properties file Key: LOGMGR-55 URL: https://issues.jboss.org/browse/LOGMGR-55 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.3.3.Final, 1.4.0.Beta1 When a handler defines an encoding and the logging.properties is written out via the PropertyConfigurator the encoding attribute is not written out. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4065) TS: Migrate from Surefire to Failsafe maven plugin.

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-4065?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-4065: ----------------------------------- This will not be merged to master until EAP 6.1 is tagged, so please keep this in sync with master (rebase now and then). > TS: Migrate from Surefire to Failsafe maven plugin. > --------------------------------------------------- > > Key: AS7-4065 > URL: https://issues.jboss.org/browse/AS7-4065 > Project: Application Server 7 > Issue Type: Enhancement > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Jakub Senko > Fix For: 7.2.0.Alpha1 > > > Surefire aims at unit testing. > Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify. > That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae). > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4065) TS: Migrate from Surefire to Failsafe maven plugin.

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-4065?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-4065: ----------------------------------- To have a new jboss parent released and used in AS, ask Paul Gier. > TS: Migrate from Surefire to Failsafe maven plugin. > --------------------------------------------------- > > Key: AS7-4065 > URL: https://issues.jboss.org/browse/AS7-4065 > Project: Application Server 7 > Issue Type: Enhancement > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Jakub Senko > Fix For: 7.2.0.Alpha1 > > > Surefire aims at unit testing. > Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify. > That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae). > -- 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

13 years, 7 months

1
0
0 / 0

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

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-941?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated JBJCA-941: ---------------------------------- Fix Version/s: 1.0.14.Final 1.1.0.Beta4 Affects Version/s: 1.1.0.Beta3 > 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, 1.1.0.Beta3 > Reporter: Philippe Marschall > Assignee: Jesper Pedersen > Labels: patch > Fix For: 1.0.14.Final, 1.1.0.Beta4 > > 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6116) Removing an entity from table confuses default selection

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6116?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-6116: ---------------------------------- seems to be affecting tables with two entities only > Removing an entity from table confuses default selection > -------------------------------------------------------- > > Key: AS7-6116 > URL: https://issues.jboss.org/browse/AS7-6116 > Project: Application Server 7 > Issue Type: Bug > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > > the default selection gets messed up. somehow the order of the deleted entity matters. requires some investigation -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-942) Unlock thread in case of a SQLException

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-942?page=com.atlassian.jira.plugin.... ] Jesper Pedersen resolved JBJCA-942. ----------------------------------- Resolution: Done > Unlock thread in case of a SQLException > --------------------------------------- > > Key: JBJCA-942 > URL: https://issues.jboss.org/browse/JBJCA-942 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.13.Final, 1.1.0.Beta3 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.14.Final, 1.1.0.Beta4 > > -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6116) Removing an entity from table confuses default selection

by Heiko Braun (JIRA)

Heiko Braun created AS7-6116: -------------------------------- Summary: Removing an entity from table confuses default selection Key: AS7-6116 URL: https://issues.jboss.org/browse/AS7-6116 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 the default selection gets messed up. somehow the order of the deleted entity matters. requires some investigation -- 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

13 years, 7 months

1
0
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 December 2012