January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2772) Drools Grid Impl2 remoting features (socket)

by Mauricio Salatino (JIRA)

Drools Grid Impl2 remoting features (socket) -------------------------------------------- Key: JBRULES-2772 URL: https://jira.jboss.org/browse/JBRULES-2772 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M1 Reporter: Mauricio Salatino Assignee: Mauricio Salatino Implement the Remoting Clients and Providers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2746) Drools Grid Impl2

by Mauricio Salatino (JIRA)

Drools Grid Impl2 ----------------- Key: JBRULES-2746 URL: https://jira.jboss.org/browse/JBRULES-2746 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M1 Reporter: Mauricio Salatino Assignee: Mauricio Salatino New APIs for Drools Grid -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2775) Drools Grid Impl 2 Spring Support for remote execution nodes

by Mauricio Salatino (JIRA)

Drools Grid Impl 2 Spring Support for remote execution nodes ------------------------------------------------------------ Key: JBRULES-2775 URL: https://jira.jboss.org/browse/JBRULES-2775 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mauricio Salatino We need to add support for the new APIs inside drools-container/drools-spring. To support grid nodes configurations using spring. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2869) Split up the build, the repositories and hudson jobs in seperate projects: at least drools, jBPM, guvnor and eclipse so it's easier to fork, checkout and build one project

by Geoffrey De Smet (JIRA)

Split up the build, the repositories and hudson jobs in seperate projects: at least drools, jBPM, guvnor and eclipse so it's easier to fork, checkout and build one project --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2869 URL: https://issues.jboss.org/browse/JBRULES-2869 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.2.0.M2 still use a parent pom. Learn from seam 3. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-833) Maven2ize drools-examples

by Geoffrey De Smet (JIRA)

Maven2ize drools-examples ------------------------- Key: JBRULES-833 URL: http://jira.jboss.com/jira/browse/JBRULES-833 Project: JBoss Rules Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 3.1-m1 Reporter: Geoffrey De Smet Assigned To: Mark Proctor Priority: Minor - the eclipse files can now be generate and generate the maven builder in it too - it compiles with a mvn install => catch compile errors early -- 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, 9 months

2
21
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1166) jta-data-source / non-jta-data-source

by Jesper Pedersen (JIRA)

jta-data-source / non-jta-data-source ------------------------------------- Key: EJBTHREE-1166 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1166 Project: EJB 3.0 Issue Type: Bug Environment: JBoss AS: SVN / trunk (rev 68402) jboss-ejb3-cache version="0.11.1" jboss/jboss-ejb3-ext-api version="0.1.2.Beta1" jboss/jboss-ejb3-impl version="0.1.2.Beta1" Reporter: Jesper Pedersen I get the following: persistence.units:ear=rasp-sender.ear,unitName=e-akten-test -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named: e-akten-test persistence.units:ear=rasp-sender.ear,unitName=e-akten -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a jta-data-source for a JTA enabled persistence context named: e-akten The EJB3 persistence spec section 6.2.1.5 states: "In Java EE environments, the jta-data-source and non-jta-data-source elements are used to specify the global JNDI name of the JTA and/or non-JTA data source to be used by the persistence provider. If neither is speciﬁed, the deployer must specify a JTA data source at deployment or a JTA data source must be provided by the container, and a JTA EntityManagerFactory will be created to cor- respond to it." I'm counting on the last case -- data source must be provided by container + entity manager. Hope this helps ! -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8680) More robust handling of previous versions of the configuration files

by Brian Stansberry (JIRA)

More robust handling of previous versions of the configuration files -------------------------------------------------------------------- Key: JBAS-8680 URL: https://jira.jboss.org/browse/JBAS-8680 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta1 Currently when an update is made to the configuration, we copy the config file to ".lastknowngood" and write a new version. We need something more sophisticated than that. 1) The original version of present on server start should be saved as .original. 2) We should keep a proper versioned history (standalone.xml.v1, standalone.xml.v2 etc) 3) Keep a standalone.xml.last which is the same as the current standalone.xml. This can be used to detect (via file timestamps) changes to standalone.xml made while the server is offline -- such change results in a new .original. 4) We need to create proper semantics for the ".lastknowngood" notion, or scrap it. Right now it's just the previous version of the file, which may or may not have been "good". -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBRULES-2333) Support <scoreDsl> besides <scoreDrl> for XmlSolverConfigurer in LocalSearchSolverConfig to allow to use DSL's instead of DRL's for score rules

by Geoffrey De Smet (JIRA)

Support <scoreDsl> besides <scoreDrl> for XmlSolverConfigurer in LocalSearchSolverConfig to allow to use DSL's instead of DRL's for score rules ----------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2333 URL: https://jira.jboss.org/jira/browse/JBRULES-2333 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.1.0.M1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.1.0.M2 shouldn't be to hard, simply adjust LocalSearchSolverConfig class as needed -- 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, 9 months

5
12
0 / 0

[JBoss JIRA] Created: (JBAS-4413) Incorrect behaviour in TCLFilter

by Poyan (JIRA)

Incorrect behaviour in TCLFilter -------------------------------- Key: JBAS-4413 URL: http://jira.jboss.com/jira/browse/JBAS-4413 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-4.0.5.GA Reporter: Poyan Assigned To: Scott M Stark Just one TCLFilter can be added to an appender, decide method return either ACCEPT or DENY. Should return NEUTRAL is some case. public int decide(LoggingEvent event) { int ok = Filter.DENY; if( acceptOnMatch == true ) { ok = Filter.DENY; if( isMatchingTCL() ){ ok = Filter.ACCEPT; } } else { ok = Filter.ACCEPT; // CHANGING THIS ROW TO ok = Filter.NEUTRAL; should do that you check the other filters to. if( isMatchingTCL() ) ok = Filter.DENY; } return ok; } Log4j.xml: <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender"> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p [%t] %c - %m%n"/> </layout> <filter class="org.jboss.logging.filter.TCLFilter"> <param name="AcceptOnMatch" value="false"/> <param name="DeployURL" value="jboss-common-client.jarpoyan"/> </filter> <filter class="org.jboss.logging.filter.TCLFilter"> <param name="AcceptOnMatch" value="false"/> <param name="DeployURL" value="dnsns.jarpoyan"/> </filter> </appender> -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-900) Address: remove isMulticastAddress()

by Bela Ban (JIRA)

Address: remove isMulticastAddress() ------------------------------------ Key: JGRP-900 URL: https://jira.jboss.org/jira/browse/JGRP-900 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 With logical addresses, we don't need this anymore: Address dest=msg.getDest(); boolean mcast=dest == null || dest.isMulticastAddress(); should be changed to boolean mcast=msg.isMulticastMessage(); // or isGroupMessage() ? -- 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, 9 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011