November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1276) Drools toolbar should not appear in all perspectives and should reuse the standard "new" dropdown

by Willian Mitsuda (JIRA)

Drools toolbar should not appear in all perspectives and should reuse the standard "new" dropdown ------------------------------------------------------------------------------------------------- Key: JBRULES-1276 URL: http://jira.jboss.com/jira/browse/JBRULES-1276 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.2 Reporter: Willian Mitsuda Assigned To: Mark Proctor I just installed the drools plugin and noted that it automatically enables a drools toolbar in every perspective. This is not a good UI policy because it looks like the plugin is trying to appear more important than the others. I have other plugins installed, and I don't like the drools button appearing by default in the C++ or the Profilling perspective, for example. It could be enabled by default just in the Drools perspective, since it exists, and the user could enable it on the others, if he desires. Also, since your actions are all about resource creation, you could hook them into the standard "new" dropdown, instead of creating your own actionset. This should make your plugin to appear more integrated to Eclipse. -- 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

17 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1230) Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath

by Krishnan Sivaramakrishna Iyer (JIRA)

Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath ------------------------------------------------------------------------------------- Key: JBRULES-1230 URL: http://jira.jboss.com/jira/browse/JBRULES-1230 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 4.0.0.GA Environment: Windows XP, Dell Optiplex GX 270 Reporter: Krishnan Sivaramakrishna Iyer Assigned To: Mark Proctor Priority: Blocker hi all, In my application, I use simple drl file based rules and it is not a J2EE application. Based on the dependencies documentation http://anonsvn.labs.jboss.com/labs/jbossrules/tags/4.0.1.14754GA/README_D... , it seems I am in the compiler option The only jars I am including are as follows :- drools-compiler-4.0.0.jar drools-core-4.0.0.jar drools-decisiontables-4.0.0.jar drools-jsr94-4.0.0.jar antlr-runtime-3.0.jar mvel14-1.2rc1.jar core-3.2.3.v_686_R32x.jar [Can anyone explain why I need this, the documentation seems like this is optional, but when I don't specify this, it does not work ?.] I also tried not including the core but including the janino library and specifying the janino compiler at run time and that also expects the core to be included. Any help is appreciated. TIA, Krishnan. Comments from Edson Tirelli Krishnan, You should not need decision tables and jsr94 jars if you are not using such feature. Regarding the compiler, you must use either core (jdt) jar or Janino jar... I'm not aware of any hard dependency on core itself... if it exists, please open a jira for us to fix. []s Edson -- 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

17 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1141) QueueBrowser sees expired messages

by Carlo de Wolf (JIRA)

QueueBrowser sees expired messages ---------------------------------- Key: JBMESSAGING-1141 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1141 Project: JBoss Messaging Issue Type: Bug Components: JMS Client Manager Affects Versions: 1.4.0.SP1 Reporter: Carlo de Wolf Assigned To: Tim Fox When I send a message which almost immediately expires, a queue browser will still show the message. sender.send(message, DeliveryMode.NON_PERSISTENT, 4, 1); Thread.sleep(2000); QueueBrowser browser = session.createBrowser(queue); Enumeration e = browser.getEnumeration(); List messages = CollectionsUtil.list(e); browser.close(); if(messages.size() == 1) { QueueReceiver receiver = session.createReceiver(dlq); message = (TextMessage) receiver.receive(2000); assertNull(message); } else { assertEquals(0, messages.size()); } -- 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

17 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1163) Set MessagingTimeoutFactory thread pool configurable

by Abel Munoz Alcaraz (JIRA)

Set MessagingTimeoutFactory thread pool configurable ---------------------------------------------------- Key: JBMESSAGING-1163 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1163 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.4.0.SP1 Environment: All environments Reporter: Abel Munoz Alcaraz Assigned To: Tim Fox It is desirable to do the limits of MessagingTimeoutFactory's thread pool configurables: MaximumQueueSize, MaximumPoolSize, etc. -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1015) Refactor cluster message notification

by Tim Fox (JIRA)

Refactor cluster message notification ------------------------------------- Key: JBMESSAGING-1015 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1015 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 We need an abstract cluster message notification system in place. This should decouple the post office from having to handle all messages via groupMember. The groupMember should be moved out of post office. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1148) Remove node id address mapping

by Tim Fox (JIRA)

Remove node id address mapping ------------------------------ Key: JBMESSAGING-1148 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1148 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta We can dramatically simplify the way we currently deal with node id- address mappings. We can pass in node id as additional data before call to connect so each address in the view has the extra data - this makes node id - address mapping redundant, and we can remove the join and leave messages. :) We can also remove the failovermap altogether - and generate it on the fly from the view (now it becomes trivial!!) This should vastly simplify things and remove the scope for race conditions. You can associate arbitrary data with an IpAddress, see below: | JChannel c=new JChannel(properties); Map<String,Object> m=new HashMap<String,Object>(); m.put("additional_data", new byte[]{'b', 'e', 'l', 'a'}); c.down(new Event(Event.CONFIG, m)); c.connect("bla"); IpAddress addr=(IpAddress)c.getLocalAddress(); System.out.println("address is " + addr); assertNotNull(addr.getAdditionalData()); assertEquals('b', addr.getAdditionalData()[0]); c.close();| -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-877) Optimise browsing

by Tim Fox (JIRA)

Optimise browsing ----------------- Key: JBMESSAGING-877 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-877 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Currently browsing is inefficient and copies the entire set of message references. Instead we should use the deque iterator + the deliveries iterator. We should also investigate activating the browsing interceptor to batch messages. -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-871) Optimisations

by Tim Fox (JIRA)

Optimisations ------------- Key: JBMESSAGING-871 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-871 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Super task for various performance related optimisations -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-878) Consider using multicast or reliable multicast for message delivery

by Tim Fox (JIRA)

Consider using multicast or reliable multicast for message delivery ------------------------------------------------------------------- Key: JBMESSAGING-878 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-878 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 We could use multicast or jgroups reliable multicast for delivery of messages from server to client when there are many subscribers - currently this is point to point. -- 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

17 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-874) INVM persistent message optimisation

by Tim Fox (JIRA)

INVM persistent message optimisation ------------------------------------ Key: JBMESSAGING-874 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-874 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally. -- 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

17 years, 9 months

2
4
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 November 2007