July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1435) Modify cobertura maven plugin definition to use version 2.5

by Rostislav Svoboda (JIRA)

Modify cobertura maven plugin definition to use version 2.5 ----------------------------------------------------------- Key: AS7-1435 URL: https://issues.jboss.org/browse/AS7-1435 Project: Application Server 7 Issue Type: Task Reporter: Rostislav Svoboda Upgrade jboss-parent to use version 2.5 for cobertura maven plugin. Version 2.5 contains functionality for agregated report - http://jira.codehaus.org/browse/MCOBERTURA-65 Don't use version 2.5.1 because there is NPE bug - see http://jira.codehaus.org/browse/MCOBERTURA-151 Workaround: specify cobertura plugin version from command line mvn -Pcode-coverage -Dcobertura.aggregate=true -Dversion.cobertura.plugin=2.5 clean cobertura:clean cobertura:cobertura -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
6
0 / 0

[JBoss JIRA] Created: (AS7-815) Fix or remove ignored tests in WSTestCase

by Thomas Diesler (JIRA)

Fix or remove ignored tests in WSTestCase ----------------------------------------- Key: AS7-815 URL: https://issues.jboss.org/browse/AS7-815 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Alessio Soldano We are in the process of a major test infrastructure update. For this I migrated all smoke tests the the managed container. The arquillian subsystem has been replaced by a on-demand deployment. Your test might be @Ignored because I could not fix it easily or it has already been ignored for some time. Please have a look if you can fix it, otherwise I'd like to know why it should be ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

7
7
0 / 0

[JBoss JIRA] Created: (AS7-1080) XA Datasource w/o xa-properties swllows an exception

by Heiko Braun (JIRA)

XA Datasource w/o xa-properties swllows an exception ---------------------------------------------------- Key: AS7-1080 URL: https://issues.jboss.org/browse/AS7-1080 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Braun Fix For: 7.1.0.Alpha1 ry to add an XA Datasource but don't add any XA properties. You will get the error below on the server. The problem is that the user doesn't see any error message at all. I assume that this is a known class of problem, but I mention here for bookkeeping purposes. 12:45:43,109 WARN [org.jboss.as.controller] (HttpManagementService-threads - 4) Operation ("add") failed - address: ([ ("subsystem" => "datasources"), ("xa-data-source" => "foo") ]): org.jboss.as.controller.OperationFailedException: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element xa-datasource-property in o rg.jboss.jca.common.metadata.ds.XADataSourceImpl [ "Failed to create XaDataSource instance for [{ \"operation\" => \"add\", \"address\" => [ (\"subsystem\" => \"datasources\"), (\"xa-data-source\" => \"foo\") ], \"name\" => \"foo\", \"jndi-name\" => \"bar\", \"enabled\" => true, \"driver-name\" => \"h2\", \"driver-class-name\" => \"org.h2.Driver\", \"driver-major-version\" => 1, \"driver-minor-version\" => 2, \"pool-name\" => \"foo_Pool\", \"user-name\" => \"asdf\", \"password\" => \"asdf\", \"xa-data-source-properties\" => {} }] reason:IJ010069: Missing required element xa-datasource-property in org.jboss.jca.common.metadata.ds.XADataSourceImpl" ] at org.jboss.as.connector.subsystems.datasources.XaDataSourceAdd.startConfigAndAddDependency(XaDataSourceAdd.java:64) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceAdd.performRuntime(AbstractDataSourceAdd.java:93) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1310) Manage resource adapters through web console

by Heiko Braun (JIRA)

Manage resource adapters through web console -------------------------------------------- Key: AS7-1310 URL: https://issues.jboss.org/browse/AS7-1310 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-1100) ENCRYPT debug log prints "hex" output in ambiguous format

by Dennis Reed (JIRA)

ENCRYPT debug log prints "hex" output in ambiguous format --------------------------------------------------------- Key: JGRP-1100 URL: https://jira.jboss.org/jira/browse/JGRP-1100 Project: JGroups Issue Type: Bug Affects Versions: 2.4.7 Reporter: Dennis Reed Assignee: Dennis Reed ENCRYPT.formatArray doesn't convert a byte array straight to hex. It leaves off any leading 0 in a byte and appends ffffff in front of any negative byte. This prevents the original data from easily being reconstructed from the log for debugging purposes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
12
0 / 0

[JBoss JIRA] Created: (AS7-1301) Update OSGi to be compatible with JBoss Modules 1.1 series

by David Lloyd (JIRA)

Update OSGi to be compatible with JBoss Modules 1.1 series ---------------------------------------------------------- Key: AS7-1301 URL: https://issues.jboss.org/browse/AS7-1301 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: David Lloyd Assignee: Thomas Diesler Fix For: 7.1.0.Alpha1 JBoss Modules 1.1 has two significant changes. First, jaxpmodule is eliminated. Second, the system module is no more - instead there's a dependency type for the system class loader. I currently have an updated AS in my http://github.com/dmlloyd/jboss-as/tree/upgrades branch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
19
0 / 0

[JBoss JIRA] Created: (AS7-1376) Implement EE.10 Application Clients

by Carlo de Wolf (JIRA)

Implement EE.10 Application Clients ----------------------------------- Key: AS7-1376 URL: https://issues.jboss.org/browse/AS7-1376 Project: Application Server 7 Issue Type: Task Components: EE Reporter: Carlo de Wolf Assignee: David Lloyd Priority: Critical Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBLOGGING-52) Use of system property for proxy generation setting is too inflexible

by Dan Allen (JIRA)

Use of system property for proxy generation setting is too inflexible --------------------------------------------------------------------- Key: JBLOGGING-52 URL: https://issues.jboss.org/browse/JBLOGGING-52 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-spi Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd Fix For: 3.0.0.Beta5-jboss-logging JBoss Logging uses a system property to configure whether or not proxies are generated for type-safe loggers. This approach is very inflexible. The main issue is that the value of this system property is being cached too aggressively. In CDI extensions, we are forced to use a static code block to set the property so it is assigned early enough that JBoss Logging caches the correct value. However, with multiple extensions loading in a non-deterministic order, we end up having to put this static block in multiple places. [1] We need a better way to apply this setting. Perhaps a static method on a configuration API to assign the value before any logging takes place. [1] https://github.com/seam/solder/blob/master/impl/src/main/java/org/jboss/s... https://github.com/seam/servlet/blob/master/impl/src/main/java/org/jboss/... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
12
0 / 0

[JBoss JIRA] Created: (JBAS-9316) Indentation of multiline text content in standalone.xml keeps increasing on rewrites

by David Bosschaert (JIRA)

Indentation of multiline text content in standalone.xml keeps increasing on rewrites ------------------------------------------------------------------------------------ Key: JBAS-9316 URL: https://issues.jboss.org/browse/JBAS-9316 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: XML Services/Frameworks Affects Versions: 7.0.0.Beta3 Reporter: David Bosschaert Assignee: Jason Greene Priority: Minor The standalone.xml file contains some XML tags that contain multi-line XML text, e.g.: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} The problem is that every automatic rewrite of the standalone.xml (e.g. when you deploy a new thing) the indentation increases from the 2nd line of the text, so after the first rewrite it looks like this: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} after a few deploys it ends up looking like this: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} Pretty ugly :( Would be nice if the indentation could be left untouched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3072) CCE due to non-boolean constraint expression

by Wolfgang Laun (JIRA)

CCE due to non-boolean constraint expression -------------------------------------------- Key: JBRULES-3072 URL: https://issues.jboss.org/browse/JBRULES-3072 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.CR1 Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0 (Possibly related to JBRULES-3011) class Person { String name; } when $p1: Person( name + name ) This is compiled, and execution fails with: Caused by: org.drools.RuntimeDroolsException: Exception executing predicate name + name at org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:298) at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:130) at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:59) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:193) at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:143) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:332) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:293) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:905) at org.drools.base.DefaultKnowledgeHelper.insert(DefaultKnowledgeHelper.java:119) at org.drools.base.DefaultKnowledgeHelper.insert(DefaultKnowledgeHelper.java:113) at freeform.Rule_ins_0.defaultConsequence(Rule_ins_0.java:9) at freeform.Rule_ins_0DefaultConsequenceInvoker.evaluate(Rule_ins_0DefaultConsequenceInvoker.java:23) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:905) ... 7 more Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean at org.drools.base.mvel.MVELPredicateExpression.evaluate(MVELPredicateExpression.java:101) at org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:291) ... 19 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
7
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 July 2011