May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-808) Need to set Infinispan transport class explicitly

by Paul Ferraro (JIRA)

Need to set Infinispan transport class explicitly ------------------------------------------------- Key: AS7-808 URL: https://issues.jboss.org/browse/AS7-808 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.Beta3 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.0.0.CR1 Since the Infinispan 5 upgrade, calls new GlobalConfiguration() no longer have a transport class set. This needs to be set explicitly when a transport is used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-680) fop-1.0.pom is different on JBoss Nexus compared to Maven central

by Stevo Slavic (JIRA)

fop-1.0.pom is different on JBoss Nexus compared to Maven central ----------------------------------------------------------------- Key: JBBUILD-680 URL: https://issues.jboss.org/browse/JBBUILD-680 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Reporter: Stevo Slavic Priority: Minor [fop-1.0.pom on central|http://repo1.maven.org/maven2/org/apache/xmlgraphics/fop/1.0/fop-...] has dependency on xmlgraphics-commons 1.4, while same pom on [JBoss Nexus public repo|https://repository.jboss.org/nexus/content/groups/public/org/apache/...] has dependency on xmlgraphics-commons 1.3. One on central is ok. This difference causes build instability. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-805) relative-to on Logging file handlers defined with default which is not honoured.

by Darran Lofthouse (JIRA)

relative-to on Logging file handlers defined with default which is not honoured. -------------------------------------------------------------------------------- Key: AS7-805 URL: https://issues.jboss.org/browse/AS7-805 Project: Application Server 7 Issue Type: Bug Reporter: Darran Lofthouse Assignee: Darran Lofthouse The paths for the logging subsystem are defined as: - <xs:complexType name="pathType"> <xs:attribute name="relative-to" use="optional" default="jboss.server.log.dir" type="xs:string"/> <xs:attribute name="path" use="required" type="xs:string"/> </xs:complexType> However the default of jboss.server.log.dir is not used if the relative-to attribute is omitted and instead the path is either absolute or relative to the folder JBoss is started from. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3038) Improve DRLDumper to not show the "value=" key on annotations when it is the only key/value pair

by Edson Tirelli (JIRA)

Improve DRLDumper to not show the "value=" key on annotations when it is the only key/value pair ------------------------------------------------------------------------------------------------ Key: JBRULES-3038 URL: https://issues.jboss.org/browse/JBRULES-3038 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.M2 Reporter: Edson Tirelli Assignee: Edson Tirelli Priority: Minor Fix For: 5.2.0.CR1 Improve DRLDumper to not show the "value=" key on annotations when it is the only key/value pair. Examples of desired dumps: @role( event ) @author( name = "Bob" ) @copyright( year = "2011", license="ASL" ) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-797) TCCL issue due to Hibernate 4.0 upgrade

by Scott Marlow (JIRA)

TCCL issue due to Hibernate 4.0 upgrade --------------------------------------- Key: AS7-797 URL: https://issues.jboss.org/browse/AS7-797 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Jason Greene Fix For: 7.0.0.CR1 This will be addressed when Hibernate 4.0 replaces the annotations-commons dependent code with jandex. In the mean time, we need a AS7 JPA integration solution. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-724) XA Datasource get removed from XML when booted in domain mode

by Heiko Braun (JIRA)

XA Datasource get removed from XML when booted in domain mode ------------------------------------------------------------- Key: AS7-724 URL: https://issues.jboss.org/browse/AS7-724 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.CR1 I am adding an XA declaration to domain.xml: <xa-datasource jndi-name="java:/H2XADS" pool-name="H2XADS"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> <xa-datasource-property name="URL">jdbc:h2:mem:test</xa-datasource-property> <security>  <user-name>sa</user-name>  <password>sa</password> </security> </xa-datasource> After the server has booted it's gone. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-723) Creating XA datasource requires driver name and version

by Heiko Braun (JIRA)

Creating XA datasource requires driver name and version ------------------------------------------------------- Key: AS7-723 URL: https://issues.jboss.org/browse/AS7-723 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 It's weird, because the XA datasource itself just relies on the DataSource class. The driver and version info is only needed to identify the module/service: Request { "operation" => "add", "address" => [ ("profile" => "default"), ("subsystem" => "datasources"), ("xa-data-source" => "H2XADS") ], "name" => "H2XADS", "jndi-name" => "H2XADS", "enabled" => true, "xa-data-source-class" => "org.h2.jdbcx.JdbcDataSource", "pool-name" => "H2XADS_Pool", "user-name" => "sa", "password" => "sa", "xa-data-source-properties" => [("URL" => "jdbc:h2:mem:test")], "child-type" => undefined } Response Internal Server Error { "outcome" => "failed", "result" => {"server-groups" => {"main-server-group" => { "server-two" => { "host" => "local", "response" => { "outcome" => "failed", "failure-description" => "java.util.NoSuchElementException: No child 'driver' exists" } }, "server-one" => { "host" => "local", "response" => { "outcome" => "failed", "failure-description" => "java.util.NoSuchElementException: No child 'driver' exists" } } }}}, "failure-description" => "Operation was not applied successfully to any servers" } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Moved: (JBBUILD-679) Add JPDFUnit to JBoss Repository

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBBUILD-679?page=com.atlassian.jira.plugi... ] George Gastaldi moved SEAMREPORTS-4 to JBBUILD-679: --------------------------------------------------- Project: JBoss Build System (was: Seam Reports) Key: JBBUILD-679 (was: SEAMREPORTS-4) Issue Type: Feature Request (was: Task) Workflow: jira (was: GIT Pull Request workflow ) > Add JPDFUnit to JBoss Repository > -------------------------------- > > Key: JBBUILD-679 > URL: https://issues.jboss.org/browse/JBBUILD-679 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: George Gastaldi > > Check if it is possible to use http://jpdfunit.sourceforge.net on this project -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2238) Accumulate should be implemented with left-input incremental so they don't start from scratch on every left-input retraction/assertion

by Geoffrey De Smet (JIRA)

Accumulate should be implemented with left-input incremental so they don't start from scratch on every left-input retraction/assertion -------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2238 URL: https://jira.jboss.org/jira/browse/JBRULES-2238 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.0.1.FINAL Reporter: Geoffrey De Smet Assignee: Mark Proctor The current accumulate implementation has a severe performance loss in the drools-solver context. Edson said that this issue could be the culprit. However, for this to be implemented the true modify feature should first be implemented. See the discussion "Why is this DRL twice as slow?" on the dev user list. >From IRC: <ge0ffrey> more and more of my experiments show the poisones nature of accumulate for drools-solver. Probably because they are backwards chained (as I understand it?). Of course accummulate is great for many use cases, just not drools-solver. <ge0ffrey> The problem is, I have no way to workaround them. I need the sum of my logically inserted objects. <etirelli> ge0ffrey: no, accumulate are implemented as forward chain as usual <etirelli> the problem is that a left-input retraction on an accumulate node will throw away any result and a leftinput assert will recalculate everything from scratch <ge0ffrey> What do you mean by "must fully recalculate"? <etirelli> mean from scratch <ge0ffrey> Why does it do that? <etirelli> remember that modify = retract+assert <ge0ffrey> And right-input retractions won't recalculate everything from scratch? <etirelli> no... right input are incremental <ge0ffrey> would making leftinput assert incremental too be possible? <etirelli> ge0ffrey: the only way to do left-input incremental is with a feature called "true modify" -- 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

13 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1466) please bail if user is using an incompatible MVEL

by Godmar Back (JIRA)

please bail if user is using an incompatible MVEL ------------------------------------------------- Key: JBRULES-1466 URL: http://jira.jboss.com/jira/browse/JBRULES-1466 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.4 Reporter: Godmar Back When using MVEL, please check String constants org.mvel.MVEL.VERSION and org.mvel.MVEL.VERSION_SUB to see if it's compatible. Bail if it isn't. Ignoring version mismatches leads to difficult to diagnose problems, see: http://lists.jboss.org/pipermail/rules-users/2008-February/004759.html http://lists.jboss.org/pipermail/rules-users/2008-February/004709.html Thanks. -- 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

13 years, 7 months

6
20
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2011