June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBRULES-50) DRL text editor to support query construct

by Mark Proctor (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-50?page=all ] Mark Proctor closed JBRULES-50. ------------------------------- > DRL text editor to support query construct > ------------------------------------------ > > Key: JBRULES-50 > URL: http://jira.jboss.com/jira/browse/JBRULES-50 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Eclipse IDE > Affects Versions: 3.0-beta1 > Reporter: Michael Neale > Assigned To: Michael Neale > Fix For: 3.0-beta1 > > > Should have sytax highlighted, code completion similar to a rule condition section, and have a simple template for creating a new query -- 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-372) QueryResult.get fires ClassCastException when using the string argument

by Giovanni Cuccu (JIRA)

QueryResult.get fires ClassCastException when using the string argument ----------------------------------------------------------------------- Key: JBRULES-372 URL: http://jira.jboss.com/jira/browse/JBRULES-372 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss Rules 3.0.1 and JBoss Rules as downloaded from svn trunk as of 12/07/06 Reporter: Giovanni Cuccu Assigned To: Mark Proctor here is the simple test case: package simpletest; public class AssertedObject { private String value; public String getValue() { return value; } public void setValue(String value) { this.value = value; } public AssertedObject(String value) { // TODO Auto-generated constructor stub this.value = value; } } package simpletest; import simpletest.AssertedObject; rule rule1 when then assert( new AssertedObject( "value1") ); assert( new AssertedObject( "value2") ); end query "assertedobjquery" assertedobj : AssertedObject( value=="value1" ) end package simpletest; import java.io.InputStreamReader; import java.util.HashMap; import java.util.Iterator; import java.util.Map; import mit.rules.test.Prestazione; import mit.rules.test.StrutturaErogante; import mit.rules.test.TempiAttesa; import mit.rules.test.TestRules; import org.drools.QueryResult; import org.drools.QueryResults; import org.drools.RuleBase; import org.drools.RuleBaseFactory; import org.drools.WorkingMemory; import org.drools.audit.WorkingMemoryFileLogger; import org.drools.compiler.PackageBuilder; public class TestQuery { public static void main(String[] args) throws Exception { // TODO Auto-generated method stub final PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl( new InputStreamReader( TestQuery.class.getResourceAsStream( "testquery.drl" ) ) ); final RuleBase ruleBase = RuleBaseFactory.newRuleBase(); ruleBase.addPackage( builder.getPackage() ); final WorkingMemory workingMemory = ruleBase.newWorkingMemory(); fireRules(workingMemory); } public static void fireRules(WorkingMemory workingMemory) { final WorkingMemoryFileLogger logger = new WorkingMemoryFileLogger( workingMemory ); logger.setFileName( "log/testquery" ); workingMemory.fireAllRules(); QueryResults results = workingMemory.getQueryResults( "assertedobjquery" ); if (results==null || !results.iterator().hasNext()) { System.err.println("Empty list"); } else { for ( Iterator it = results.iterator(); it.hasNext(); ) { QueryResult result = ( QueryResult )it.next();; AssertedObject assertedObject=(AssertedObject)result.get( "assertedobj" ); System.out.println("AssertedObject with value " + assertedObject.getValue()); } } logger.writeToDisk(); } } -- 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

18 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-844) Create bridge smoke test

by Tim Fox (JIRA)

Create bridge smoke test ------------------------ Key: JBMESSAGING-844 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-844 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA We should create a smoke test that starts 3 nodes, and deploys a bridge on one of them, then bridges messages from one node to another. -- 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

18 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1013) Document configuration for the microcontainer

by Brian Stansberry (JIRA)

Document configuration for the microcontainer --------------------------------------------- Key: JBCACHE-1013 URL: http://jira.jboss.com/jira/browse/JBCACHE-1013 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.CR1 -- 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

18 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-809) Pojo-style configuration for use by Microcontainer

by Brian Stansberry (JIRA)

Pojo-style configuration for use by Microcontainer -------------------------------------------------- Key: JBCACHE-809 URL: http://jira.jboss.com/jira/browse/JBCACHE-809 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Critical Fix For: 2.0.0 Need to be able construct a 2.0 Cache using the MC. We need Pojo configuration classes for all configuration elements except JGroups protocol stack. MC-style configuration should not rely on injecting a DOM element or a Properties object into any config object. Old style configuration still needs to be supported though. -- 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

18 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1469) Portlet window name can not be UTF8

by Dave Chen (JIRA)

Portlet window name can not be UTF8 ----------------------------------- Key: JBPORTAL-1469 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1469 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Environment: JBOSS, IE, MyFaces Reporter: Dave Chen In portal management page, adding a Portlet into a page with a window name in UTF8, the window name was not displayed correctly. -- 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-700) add ability to add descriptions to jmx operations in Service beans

by William DeCoste (JIRA)

add ability to add descriptions to jmx operations in Service beans ------------------------------------------------------------------ Key: EJBTHREE-700 URL: http://jira.jboss.com/jira/browse/EJBTHREE-700 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC8 - FD Reporter: William DeCoste Assigned To: William DeCoste -- 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

18 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-978) NullPointerException within DefaultClusteredPostOffice.handleMessagePullResult()

by Ray Ploski (JIRA)

NullPointerException within DefaultClusteredPostOffice.handleMessagePullResult() -------------------------------------------------------------------------------- Key: JBMESSAGING-978 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-978 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.2.0.SP1 Environment: CentOS 4, JBoss AS 4.0.5, Sun JDK 1.5.07, MySQL 5.x for persistence. Six node cluster. Reporter: Ray Ploski Assigned To: Tim Fox After sending about 10,000 messages through a clustered JMS deployment we received the following error, locking up the topic. I worked around it by adding a null check to the condition within handleMessagePullResult(). Fix is for line 968 of org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice is listed at the end of the description. 2007-05-31 11:41:39,130 ERROR @IncomingMessageHandler (channel=DefaultPostOffice) [DefaultClusteredPostOffice] Caught Exception in Receiver java.lang.NullPointerException at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.handleMessagePullResult(DefaultClusteredPostOffice.java:968) at org.jboss.messaging.core.plugin.postoffice.cluster.PullMessageResultRequest.execute(PullMessageResultRequest.java:105) at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$DataReceiver.receive(DefaultClusteredPostOffice.java:2461) at org.jgroups.JChannel.up(JChannel.java:1102) at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:377) at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:393) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.pbcast.GMS.up(GMS.java:771) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:791) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:154) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.FRAG.up(FRAG.java:168) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:476) at org.jgroups.protocols.UNICAST.up(UNICAST.java:206) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) FIX: if (remoteQueue == null || remoteNodeId != remoteQueue.getNodeId() ) -- 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

18 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-974) concurrent job acquirement fails

by Alexander Schlett (JIRA)

concurrent job acquirement fails -------------------------------- Key: JBPM-974 URL: http://jira.jboss.com/jira/browse/JBPM-974 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Alexander Schlett Assigned To: Tom Baeyens when more than 1 job executor thread is configured and concurrent async nodes are to be executed, it results in hibernate exceptions. reason: job acquirement is not synchronized well, resulting in multiple threads trying to work on the same job. -- 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

18 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-976) The setting "resource.mail.properties" is never used.

by luka kama (JIRA)

The setting "resource.mail.properties" is never used. ----------------------------------------------------- Key: JBPM-976 URL: http://jira.jboss.com/jira/browse/JBPM-976 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2 Reporter: luka kama Assigned To: Tom Baeyens The property "resource.mail.properties" should be used if the property "jbpm.mail.smtp.host" is not defined. The proplem is that "jbpm.mail.smtp.host" is set in the default configuration, so it will be always defined, preventing the "resource.mail.properties" to be used. Maybe the check should be reversed? (check before "resource.mail.properties" and if not set use "jbpm.mail.smtp.host") -- 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

18 years, 6 months

3
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 June 2007