April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-892) Forgotten e.printStackTrace()

by Johan Parent (JIRA)

Forgotten e.printStackTrace() ----------------------------- Key: JBPM-892 URL: http://jira.jboss.com/jira/browse/JBPM-892 Project: JBoss jBPM Issue Type: Patch Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: XP, jbpm-3.1.4 Reporter: Johan Parent Assigned To: Tom Baeyens Priority: Trivial A forgotten stack trace in a catch block exposes an otherwise cought exception. Prevent elegant implementation of optimistic locking strategy. Patch is simple, remove line 213 in the close() methode in org.jbpm.svc.Service (for 3.1.4) -- 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

19 years, 3 months

2
5
0 / 0

[JBoss JIRA] Closed: (JBPM-392) cancel taskInstances, messages and timers when process instance ends

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-392?page=all ] Tom Baeyens closed JBPM-392. ---------------------------- Fix Version/s: (was: jBPM jPDL 3.2.1) Resolution: Won't Fix this issue won't be fixed as a jbpm API. the problem is that the logs refer to the task instance data, even when the process is ended. so the historic information would have to be removed in order for the task data to be removed. in the next generation version of jbpm, we'll be starting with a real business intelligence solution that duplicates all the information in the historic archive. instead, users will have the following workaround: they can do for now: use hibernate bulk delete to remove the logs that have references to the task instances (similar for any other type of runtime data). then, use the bulk delete to remove the task instances themselves. > cancel taskInstances, messages and timers when process instance ends > -------------------------------------------------------------------- > > Key: JBPM-392 > URL: http://jira.jboss.com/jira/browse/JBPM-392 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > when a process instance ends, we should have an option to remove or cancel all open taskInstance, messages and timers. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4349) Have -b option in the run.bat/run.sh with Comma Separated List of IPs as Parameter .

by Vicky Kak (JIRA)

Have -b option in the run.bat/run.sh with Comma Separated List of IPs as Parameter . ------------------------------------------------------------------------------------ Key: JBAS-4349 URL: http://jira.jboss.com/jira/browse/JBAS-4349 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: System service Reporter: Vicky Kak Assigned To: Dimitris Andreadis Priority: Optional The -b option of the run.bat/run.sh which binds address for all JBoss service should take the comma separated list of IP -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBRULES-151) DSL mapping editor pop up to use a text area instead of a one line

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-151?page=all ] Michael Neale resolved JBRULES-151. ----------------------------------- Resolution: Won't Fix > DSL mapping editor pop up to use a text area instead of a one line > ------------------------------------------------------------------ > > Key: JBRULES-151 > URL: http://jira.jboss.com/jira/browse/JBRULES-151 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Eclipse IDE > Reporter: Michael Neale > Assigned To: Michael Neale > Fix For: 3.1-m3 > > > The editor at the moment is a one line field. Would be nice to have a larger area. Where newlines can be stored. When applying the mapping, the newlines can be removed (they are not really needed). > This is a precursor to syntax colouring and code completion in the language mapping editor. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBRULES-208) Improved DSL Organization

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-208?page=all ] Michael Neale resolved JBRULES-208. ----------------------------------- Resolution: Out of Date This has been partially incorporated, and partially superseeded by the new package configuration concepts (in the BRMS etc) - where the package config is kept outside of the DRL or DSL file (the DSL file is just a specific asset that contributes to the configuration). > Improved DSL Organization > ------------------------- > > Key: JBRULES-208 > URL: http://jira.jboss.com/jira/browse/JBRULES-208 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Affects Versions: 3.0-beta1 > Reporter: Jeff Brown > Assigned To: Michael Neale > Fix For: 3.1-m3 > > Attachments: DSL-contribs-mahen.zip > > > When using DSL, right now import statements are added to the DRL file. The statements that those import statements affect are in the DSL file. It may make more sense to get the import statements into the file that explicitely uses the classes being imported. As it is right now, if the DSL implementation changes in a way that doesn't change the DSL syntax, the DRL file may still have to be updated just to include new imports. That is an implementation detail that should be transparent to the DRL author. > To take that a bit further, it may make sense to move the function definitions so the DRL file includes just the expander and the rules. This separation would be cleaner and would probably make more sense from the perspective of the DRL author. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-375) "?" doesn't seem to be recognized in the excel spreadsheet.

by wen Lin (JIRA)

"?" doesn't seem to be recognized in the excel spreadsheet. ------------------------------------------------------------- Key: JBRULES-375 URL: http://jira.jboss.com/jira/browse/JBRULES-375 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 3.0.1 Environment: window xp, eclipses-3.1.2 Reporter: wen Lin Assigned To: Mark Proctor In the action cell, I have int score = (i.getMyScore()< $param)? i.getMyScore(): $param; c.setAdjustScore(score); c.setFlag(false); modify( c ); and got the following errors: [mTokens]: line 25:39 state 0 (decisionfiltered=16) no viable alt line 25:39; char='?' [mTokens]: line 37:39 state 0 (decisionfiltered=16) no viable alt line 37:39; char='?' [mTokens]: line 49:39 state 0 (decisionfiltered=16) no viable alt line 49:39; char='?' [mTokens]: line 61:39 state 0 (decisionfiltered=16) no viable alt line 61:39; char='?' [mTokens]: line 73:39 state 0 (decisionfiltered=16) no viable alt line 73:39; char='?' [mTokens]: line 85:39 state 0 (decisionfiltered=16) no viable alt line 85:39; char='?' [mTokens]: line 97:39 state 0 (decisionfiltered=16) no viable alt line 97:39; char='?' Rule Compilation error Syntax error on token ")", ? expected after this token Rule Compilation error Syntax error on token ")", ? expected after this token Rule Compilation error Syntax error on token ")", ? expected after this token Rule Compilation error Syntax error on token ")", ? expected after this token Rule Compilation error Syntax error on token ")", ? expected after this token Rule Compilation error Syntax error on token ")", ? expected after this token Rule Compilation error Syntax error on token ")", ? expected after this token ------------------------------------------------------------------ but the problem disappears while I use the following instead: c.setAdjustScore(Math.min(i.getMyScore (), $param)); --------------------------------------------------------------------------------------- It seems to me that either "?" is not recognized or "(a>b)? a:b" doesn't 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

19 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-945) Resource injection not working for embedded

by William DeCoste (JIRA)

Resource injection not working for embedded ------------------------------------------- Key: EJBTHREE-945 URL: http://jira.jboss.com/jira/browse/EJBTHREE-945 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: William DeCoste Assigned To: William DeCoste @Resource(mappedName = "java:/GP3DS") public DataSource dataSource; -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-940) Provide slimmed down client jar

by Tim Fox (JIRA)

Provide slimmed down client jar ------------------------------- Key: JBMESSAGING-940 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-940 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.SP2 We will provide a slimmed down jboss-messaging-client.jar that only includes jboss messaging classes (and maybe some others that are very unlikely to change). This wil help resolve several issues customers have had with conflicts with versions of classes in the fat jar with other versions required for other products like EJB3 which required a different version of remoting. -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-259) Activate compression in marshaller

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-259?page=all ] Tim Fox updated JBMESSAGING-259: -------------------------------- Priority: Minor (was: Major) > Activate compression in marshaller > ---------------------------------- > > Key: JBMESSAGING-259 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-259 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Activate compression in marshaller for messages > x bytes. Make it configurable -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-607) Update the Messaging Lab page

by Ovidiu Feodorov (JIRA)

Update the Messaging Lab page ----------------------------- Key: JBMESSAGING-607 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-607 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Tim Fox Priority: Critical Fix For: 1.2.0.Alpha2 Update the content of the main lab page (http://labs.jboss.com/portal/jbossmessaging/) so it is consistent with the latest advances in the architecture. Damon offered to help with this. He will provide formatting and "look-and-feel" support. Tim will generate the content. -- 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

19 years, 3 months

7
10
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 April 2007