October 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMDR-44) Release JBoss MDR 2.0.0.CR2

by Ales Justin (JIRA)

Release JBoss MDR 2.0.0.CR2 --------------------------- Key: JBMDR-44 URL: https://jira.jboss.org/jira/browse/JBMDR-44 Project: JBoss MetaData Repository Issue Type: Release Components: Release Affects Versions: JBossMDR-2.0.0.CR1 Reporter: Ales Justin Assignee: Ales Justin Priority: Minor Fix For: JBossMDR-2.0.0.CR2 -- 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

16 years, 3 months

1
2
0 / 0

[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

16 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1641) ForEach node

by Kris Verlaenen (JIRA)

ForEach node ------------ Key: JBRULES-1641 URL: http://jira.jboss.com/jira/browse/JBRULES-1641 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assigned To: Mark Proctor A ForEach node is a composite node that executes the contained subflow for each of the elements in a collection -- 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

16 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2189) New JBPM process definitions in portal-identity.sar are not picked up

by Stephen Houston (JIRA)

New JBPM process definitions in portal-identity.sar are not picked up --------------------------------------------------------------------- Key: JBPORTAL-2189 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2189 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.6 Final Environment: JDK 1.6.07, JBoss AS 4.2.3.GA (using the all server config), JBoss Portal 2.6.6 HA, CentOs 5.1 Reporter: Stephen Houston New process definitions copied to the server/all/deploy/jboss-portal-ha.sar/portal-identity.sar/conf directory are not picked up. The original definition is used. Steps to reproduce * Stop the portal if its running * Copy the attached com.test-0.0.1-SNAPSHOT.jar to jboss-portal-ha.sar/lib. This contains two handler definitions, Handler1 prints out 1s and Handler2 prints out 2s * Extract def1.zip to portal-identity.sar/conf/processes. This creates a new process definition testprocess.xml * Modify portal-identity.sar/conf/identity-ui-configuration.xml , adding the line <admin-subscription-mode>testprocess</admin-subscription-mode> * Start the portal. Login as admin, create a new user account. When submitted to the process you will see 10 lines of 1's written to the console * Stop the portal * Extract def2.zip to portal-identity.sar/conf/processes. This will overwrite testprocess.xml with one that uses Handler2 instead of handler 1. * Start the portal. Login as admin, create a new user account. When submitted to the process you will see 10 lines of 1's written to the console indicating that the old process version was used instead of the updated on. To work around the problem you need to change the process name, rename the file, and update identity-ui-configuration.xml. It would be more desirable if the portal could determine that the process has changed and that it needs to be picked up and redeployed. -- 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

16 years, 3 months

1
5
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-375) Grouping of messages

by Andy Taylor (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-375?page=com.atlassian.jir... ] Andy Taylor commented on JBMESSAGING-375: ----------------------------------------- Ive changed the API to make this simpler, revision 5073. > Grouping of messages > -------------------- > > Key: JBMESSAGING-375 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assignee: Andy Taylor > Fix For: 2.0.0 Beta > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by a group id so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of group id. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-1) Move existing prototype to a branch

by Jesper Pedersen (JIRA)

Move existing prototype to a branch ----------------------------------- Key: JBJCA-1 URL: https://jira.jboss.org/jira/browse/JBJCA-1 Project: JBoss JCA Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Minor Fix For: 1.0 Alpha1 Move the existing prototype done by Adrian and Vicky to a branch -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1783) Spelling Error in Remove DSL Dialog Box

by Steve Nunez (Illation) (JIRA)

Spelling Error in Remove DSL Dialog Box --------------------------------------- Key: JBRULES-1783 URL: https://jira.jboss.org/jira/browse/JBRULES-1783 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 5.0.0.M1 Reporter: Steve Nunez (Illation) Assignee: Mark Proctor "Sentense" should read "Sentence" -- 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

16 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1454) Unit tests for date ranges are not working

by Toni Rikkola (JIRA)

Unit tests for date ranges are not working ------------------------------------------ Key: JBRULES-1454 URL: http://jira.jboss.com/jira/browse/JBRULES-1454 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Toni Rikkola I made the tests earlier. They worked when I ran them on my computer, but failed when I took a look at them in hudson. So they were disabled for a while. Today I got an error from the drl-file that these unit tests use. -- 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

16 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1486) Rules for incompatible restrictions

by Toni Rikkola (JIRA)

Rules for incompatible restrictions ----------------------------------- Key: JBRULES-1486 URL: http://jira.jboss.com/jira/browse/JBRULES-1486 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Toni Rikkola Assigned To: Mark Proctor Rules that look for incompatible restrictions. Example: Pattern( a != 1, a == 1 ) This information will be used for Rule incompatibility, Rule conflict and Rule incoherence. -- 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

16 years, 3 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBRULES-1733) Set execution environment in project's build path.

by Mark Proctor (JIRA)

[ https://jira.jboss.org/jira/browse/JBRULES-1733?page=com.atlassian.jira.p... ] Mark Proctor updated JBRULES-1733: ---------------------------------- Assignee: Kris Verlaenen (was: Mark Proctor) kris, I'm assigning this to you, but I don't think this makes sense. We can and do set the classpath, but I don't think we can set the JRE, because every system is different. > Set execution environment in project's build path. > -------------------------------------------------- > > Key: JBRULES-1733 > URL: https://jira.jboss.org/jira/browse/JBRULES-1733 > Project: JBoss Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: All > Affects Versions: FUTURE > Environment: Eclipse IDE > Reporter: Faron Dutton > Assignee: Kris Verlaenen > Priority: Minor > > Currently, each Drools project relies on the default Eclipse JRE container, which varies from one developer to another. Configuring the execution environment in a project's classpath will remove the need for a developer to alter the classpath on checkout. -- 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

16 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2008