October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3607) Drools Grid-Node issue

by Sunny Osaje (JIRA)

Sunny Osaje created JBRULES-3607: ------------------------------------ Summary: Drools Grid-Node issue Key: JBRULES-3607 URL: https://issues.jboss.org/browse/JBRULES-3607 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Sunny Osaje Assignee: Mark Proctor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] (JBRULES-3578) Normalize tuple interfaces eliminating the separate interface for RightTuples

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3578: -------------------------------------- Summary: Normalize tuple interfaces eliminating the separate interface for RightTuples Key: JBRULES-3578 URL: https://issues.jboss.org/browse/JBRULES-3578 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.4.0.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.5.0.Beta1 The current split of tuples into LeftTuples and RightTuples adds complexity to the system and makes impossible for the system to join (concatenate) 2 left tuples. The goal of this task is to normalize all tuple interfaces into a single interface, allowing two-input nodes like joins to join 2 tuples, independently of the number of elements in each. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (JBRULES-3448) XLS Decision tables: Add support for Condition column DRL fragments

by Michael Anstis (JIRA)

Michael Anstis created JBRULES-3448: --------------------------------------- Summary: XLS Decision tables: Add support for Condition column DRL fragments Key: JBRULES-3448 URL: https://issues.jboss.org/browse/JBRULES-3448 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Michael Anstis Assignee: Michael Anstis Fix For: 5.5.0.Beta1 Condition columns in XLS Decision Tables have a row for Object type and a row for code "snippet". The code snippet is taken as predicates within the Object type; for example:- {code} CONDITION | CONDITION ---------------------------- MyFact ---------------------------- field1 == | field2 == ---------------------------- a | b {code} This is rather limiting (and certainly not conducive to decision table round-tripping). Ideally we need to support:- {code} CONDITION ---------------------------------------------- MyFact( field1 == $param1, field2 == $param2 ) ---------------------------------------------- ---------------------------------------------- a,b {code} Even more ideally it'd be good to be able to register "column handlers" so this can be extended easily. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] (JBRULES-3514) Add support to event sequencing

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3514: -------------------------------------- Summary: Add support to event sequencing Key: JBRULES-3514 URL: https://issues.jboss.org/browse/JBRULES-3514 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-compiler, drools-core Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.5.0.Beta1 The purpose of this ticket is to centralize the discussions regarding the implementation of event sequencing as detailed in the wiki page at: https://community.jboss.org/wiki/EventSequencing The highlevel discussions can be added to this ticket while individual sub-tickets will be created for the implementation of each sub-feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
28
0 / 0

[JBoss JIRA] (JBRULES-3637) The "from" CE does not manage @events correctly

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3637: --------------------------------------- Summary: The "from" CE does not manage @events correctly Key: JBRULES-3637 URL: https://issues.jboss.org/browse/JBRULES-3637 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.4.0.Final Reporter: Davide Sottara Assignee: Edson Tirelli Priority: Critical Fix For: 5.5.0.Beta1 If an event type (i.e. an instance of a class marked with @role(event)) is returned by a "from" node, it is not wrapped by an EventFactHandle as expected, so e.g. any attempt to use temporal operators will fail. See the test case below for an example The problem is in FromNode.java around line 200, where the new handles are created without passing an ObjectTypeConfiguration, leading to the default creation of a DefaultFactHandle. I wonder if it's possible to simply retrieve the ObjectTypeConf: workingMemory.getObjectTypeConfigurationRegistry().getObjectTypeConf( context.getEntryPoint(), object ) and pass it to the handle factory method. I tested it and it works for the test case below, but there may be other side-effects I'm not seeing. --------------------------------------------------------------------------- May be related (but not the same as) #JBRULES-2423 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
0 / 0

[JBoss JIRA] (AS7-5718) Client deserialising objects using wrong classloader

by James Livingston (JIRA)

James Livingston created AS7-5718: ------------------------------------- Summary: Client deserialising objects using wrong classloader Key: AS7-5718 URL: https://issues.jboss.org/browse/AS7-5718 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.3.Final (EAP) Reporter: James Livingston Assignee: Eduardo Martins The commands in org.jboss.naming.remote.protocol.v1.Protocol deserialize objects using the Unmarshaller from ReadUtil. That does not explicitly set a ClassResolver, so it defaults to using the TCCL. Since the handle*Message methods are run in a thread pool, the TCCL could be set to anything, so the commands need to ensure that the correct classloader (presumably the one calling the Context methods) is used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] (AS7-5821) Revisit AS7-1313: lower "Clustering not supported" to INFO level

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-5821: ----------------------------------- Summary: Revisit AS7-1313: lower "Clustering not supported" to INFO level Key: AS7-5821 URL: https://issues.jboss.org/browse/AS7-5821 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) https://issues.jboss.org/browse/AS7-1313?focusedCommentId=12725635&page=c... <distributable/> marks that the app is capable of running in distributable mode, but does not have to be. INFO seems more appropriate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] (JBASMP-25) Don't kill maven process after run goal cancellation

by James Perkins (JIRA)

James Perkins created JBASMP-25: ----------------------------------- Summary: Don't kill maven process after run goal cancellation Key: JBASMP-25 URL: https://issues.jboss.org/browse/JBASMP-25 Project: JBoss AS Maven Plugins Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins Is it possible to reopen this issue? The {{jboss-as:run}} goal does not help when the deployment is to be used in the same Maven build, since the goal tends to block subsequent goals. For example, using this goal in the {{pre-integration-test}} phase, prevents the maven-failsafe-plugin from executing integration tests. Is it possible to introduce goals atleast to start and stop standalone JBoss 7 instances, so that a Maven CI build could manage the lifecyle of the instance ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (AS7-5825) Custom JAAS Security Realm for Remoting

by Pedro Igor (JIRA)

Pedro Igor created AS7-5825: ------------------------------- Summary: Custom JAAS Security Realm for Remoting Key: AS7-5825 URL: https://issues.jboss.org/browse/AS7-5825 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Environment: JBoss Application Server 7.1.1.Final Reporter: Pedro Igor Tried to configure a custom JAAS Security Realm for the Remoting Connector using JBoss Application Server 7.1.1.Final. These same steps work with JBoss AS 7.2.0 and 7.1.3. When debbuging the client (in my case a EJB standalone client using org.jboss.ejb.client.naming) I noticed that the PLAIN mech is not returned by the server. My client expects the PLAIN mech to authenticate users using the provided username / password when creating the InitialContext. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
6
0 / 0

[JBoss JIRA] (AS7-5824) Build a workbench for REPL like features

by Harald Pehl (JIRA)

Harald Pehl created AS7-5824: -------------------------------- Summary: Build a workbench for REPL like features Key: AS7-5824 URL: https://issues.jboss.org/browse/AS7-5824 Project: Application Server 7 Issue Type: Sub-task Reporter: Harald Pehl Assignee: Harald Pehl The workbench is an own GWT entry point. Using the workbench one can edit the abstract UI model and generate a concrete UI on the fly. Thus the workbench can be used to have something like a *R*ead-*e*val-*p*rint-*l*oop. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
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 October 2012