October 2007 - 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

2
21
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

2
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

2
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

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

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

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-513) Remove deprecated system properties (non 'jboss' namespace)

by Brian Stansberry (JIRA)

Remove deprecated system properties (non 'jboss' namespace) ----------------------------------------------------------- Key: JGRP-513 URL: http://jira.jboss.com/jira/browse/JGRP-513 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assigned To: Bela Ban Priority: Minor As discussed on http://wiki.jboss.org/wiki/Wiki.jsp?page=SystemProps there are a number of deprecated, 'legacy' system properties. This is just a JIRA entry to track remembering to clean them up. This JIRA is for the non-'jboss' namespaced properties, which perhaps we would keep around longer than the 'jboss' ones. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-512) Remove support for deprecated 'jboss' namespaced system properties

by Brian Stansberry (JIRA)

Remove support for deprecated 'jboss' namespaced system properties ------------------------------------------------------------------ Key: JGRP-512 URL: http://jira.jboss.com/jira/browse/JGRP-512 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assigned To: Bela Ban Priority: Minor As discussed on http://wiki.jboss.org/wiki/Wiki.jsp?page=SystemProps there are a number of deprecated, 'legacy' system properties. This is just a JIRA entry to track remembering to clean them up. I'm creating a separate JIRA for the non-'jboss' namespaced properties. Use of the 'jboss' namespace isn't too good, so it might be justified removing those earlier, e.g. 2.5, so users won't use them in AS 5.x and expect them to work. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-563) Consolidate state transfer API to use streams

by Vladimir Blagojevic (JIRA)

Consolidate state transfer API to use streams --------------------------------------------- Key: JGRP-563 URL: http://jira.jboss.com/jira/browse/JGRP-563 Project: JGroups Issue Type: Task Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 3.0 Although streaming state transfer has its advantages over byte based state transfer, byte based state transfer is absolutely necessary since streaming based transfer relies on plain sockets that are not firewall friendly. However, that does not mean that we cannot consolidate state transfer API at application level and mask byte based transfer with streams. We have already done this in JBC 2.0 so there is no reason not to do it on JGroups level as well. Advantages: - simpler state transfer API - interchangeable state transfer mechanism without affect on application - simplification of client application Disadvantages: - we break current API by eliminating getState(byte[]) and setState(byte []) -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-567) Add one shot state transfer for multiple substates

by Vladimir Blagojevic (JIRA)

Add one shot state transfer for multiple substates -------------------------------------------------- Key: JGRP-567 URL: http://jira.jboss.com/jira/browse/JGRP-567 Project: JGroups Issue Type: Feature Request Affects Versions: 2.x Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Currently (2.5) each sub state transfer requires separate state transfer invocation for each sub state. It would be very convenient if we could transfer a list of substates all in one underlying state transfer. This would require introduction of a new method in JChannel API, however we should avoid additional callbacks on application level. Proposed API for additional JChannel method is: public boolean getState(Address target, List<String> state_ids, long timeout) throws ChannelNotConnectedException, ChannelClosedException; -- 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

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007