November 2008 - jboss-jira - Jboss List Archives

[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, 8 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, 8 months

3
3
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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-799) RpcDispatcher: merge Marshaller and Marshaller2 into one interface

by Bela Ban (JIRA)

RpcDispatcher: merge Marshaller and Marshaller2 into one interface ------------------------------------------------------------------ Key: JGRP-799 URL: https://jira.jboss.org/jira/browse/JGRP-799 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0 -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-848) Streamable: use interface rather than class as parameter

by Bela Ban (JIRA)

Streamable: use interface rather than class as parameter -------------------------------------------------------- Key: JGRP-848 URL: https://jira.jboss.org/jira/browse/JGRP-848 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 DataOutput instead of DataOutputStream, and the same for input -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-396) Replace all uses of Vector, ArrayList etc with interfaces

by Bela Ban (JIRA)

Replace all uses of Vector, ArrayList etc with interfaces --------------------------------------------------------- Key: JGRP-396 URL: http://jira.jboss.com/jira/browse/JGRP-396 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 - E.g. - Vector --> Collection - ArrayList --> List -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-835) RpcDispatcher/MessageDispatcher: remove deadlock_detection parameters

by Bela Ban (JIRA)

RpcDispatcher/MessageDispatcher: remove deadlock_detection parameters --------------------------------------------------------------------- Key: JGRP-835 URL: https://jira.jboss.org/jira/browse/JGRP-835 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 related to https://jira.jboss.org/jira/browse/JGRP-828 -- 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
1
0 / 0

[JBoss JIRA] Created: (JGRP-412) Replace all uses of Channel.receive() with Receiver.receive() callbacks

by Bela Ban (JIRA)

Replace all uses of Channel.receive() with Receiver.receive() callbacks ----------------------------------------------------------------------- Key: JGRP-412 URL: http://jira.jboss.com/jira/browse/JGRP-412 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 This includes removing PullPushAdapters and converting MessageDispatcher/RpcDispatcher to use Receiver instead of PullPushAdapter -- 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
2
0 / 0

[JBoss JIRA] Created: (JGRP-453) Change signature of Channel.down() to return Object, rename downcall() to down()

by Bela Ban (JIRA)

Change signature of Channel.down() to return Object, rename downcall() to down() -------------------------------------------------------------------------------- Key: JGRP-453 URL: http://jira.jboss.com/jira/browse/JGRP-453 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 We had to make Channel.down() return void, otherwise JGroups would not have been backwards compatible with JBoss 4.0.5 -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-612) ChannelFactory should have only channel create methods

by Vladimir Blagojevic (JIRA)

ChannelFactory should have only channel create methods ------------------------------------------------------ Key: JGRP-612 URL: http://jira.jboss.com/jira/browse/JGRP-612 Project: JGroups Issue Type: Task Affects Versions: 2.5, 2.6, 2.7, 2.x Reporter: Vladimir Blagojevic Assigned To: Bela Ban Fix For: 3.0 ChannelFactory should not have setMultiplexerConfig methods but rather only create channel methods. Multiplexer configuration can be initialized through implementors constructor. -- 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
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008