July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-446) Start the QA process in concert with QA team

by Ovidiu Feodorov (JIRA)

Start the QA process in concert with QA team -------------------------------------------- Key: JBMESSAGING-446 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-446 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-708) Version control of the process definition

by Aravind Kumar (JIRA)

Version control of the process definition ----------------------------------------- Key: JBPM-708 URL: http://jira.jboss.com/jira/browse/JBPM-708 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.1 Reporter: Aravind Kumar Assigned To: Tom Baeyens When working with jBPM in developement environment, there is no control over the version of the process-definition. Each time the server is restarted, a new version is deployed. The work around that I did: <boolean name="update-definition" value="false"/> this tag is included in the jbpm.cfg.xml & a check at JbpmContext.java: public void deployProcessDefinition(ProcessDefinition processDefinition) { if(JbpmConfiguration.Configs.getBoolean("update-definition")) { getGraphSession().deployProcessDefinition(processDefinition); } } This works fine for a single process defifnition. In case, there are multiple process definitions and some needs to be updates and some need not be. -- 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, 8 months

4
3
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

18 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBSER-84) Improve serialization of immutable objects

by Michael Santos (JIRA)

Improve serialization of immutable objects ------------------------------------------ Key: JBSER-84 URL: http://jira.jboss.com/jira/browse/JBSER-84 Project: JBoss Serialization Issue Type: Feature Request Reporter: Michael Santos Assigned To: Clebert Suconic It is common for objects to contain references to hundreds or thousands of equal immutable object instances, especially java.lang.Number subclasses. Some immutable objects produce a considerable serialized amount of information, such as java.math.BigDecimal. However, there's usually no reason for different instances being used to represent the same value; they only exist due to the way they were produced (parsing &, conversion APIs and JDBC are definitely fine examples of that). Experiments on a particular project have shown replacing all these equal instances by one of them can reduce the serialized size of some objects by half. Therefore, JBoss Serialization should provide way to allow users to tell it's ok to use the same reference for all these immutable instances and which classes are to be considered immutable and replace them during the writing phase. This would be much more efficient and wouldn't require developers to rewrite their code in order to optimize serialization of some objects. A global way, such as system property, of telling the API to do this by default with the most commonly used Java SE classes would be desirable as well. -- 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, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-692) Task name in forms.xml refering to non-existent task leads to stackoverflow

by Ronald van Kuijk (JIRA)

Task name in forms.xml refering to non-existent task leads to stackoverflow --------------------------------------------------------------------------- Key: JBPM-692 URL: http://jira.jboss.com/jira/browse/JBPM-692 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM 3.2 alpha 2 Environment: jdk1.5.0_06, cvs-head of 12-6, jboss 4.03sp1 on linux Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Minor Fix For: jBPM 3.2 A <form task="......" in forms.xml refering to a non existent task (case sensitivity problem) leads to a stacktoverflow without any meaningful error.... Either it should be case-insensitive or checked on deploytime. Frustrating, cost me 4 hours :-( -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3437) Get the 3.2-compatibility tests passing for 4.0.5.CR1

by Dimitris Andreadis (JIRA)

Get the 3.2-compatibility tests passing for 4.0.5.CR1 ----------------------------------------------------- Key: JBAS-3437 URL: http://jira.jboss.com/jira/browse/JBAS-3437 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.5.CR1 Task to hold compatibility test issues -- 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, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-666) Throw javax.ejb.ConcurrentAccessException when two threads access the same SFSB instance

by Gavin King (JIRA)

Throw javax.ejb.ConcurrentAccessException when two threads access the same SFSB instance ---------------------------------------------------------------------------------------- Key: EJBTHREE-666 URL: http://jira.jboss.com/jira/browse/EJBTHREE-666 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Gavin King Priority: Critical Fix For: EJB 3.0 RC9 - FD See section 4.13.3 of the EJB Core Contracts specification. I need this for Seam. -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-667) IIOP binding

by Carlo de Wolf (JIRA)

IIOP binding ------------ Key: EJBTHREE-667 URL: http://jira.jboss.com/jira/browse/EJBTHREE-667 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Fix For: EJB 3.0 RC9 - FD Make IIOP binding work in the EJB3 stack. To use IIOP on an EJB bean, the following code is used: @RemoteBinding(factory=org.jboss.ejb3.iiop.IORFactory.class) -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-660) Nested sfsb passivation notification is incorrect

by Ben Wang (JIRA)

Nested sfsb passivation notification is incorrect ------------------------------------------------- Key: EJBTHREE-660 URL: http://jira.jboss.com/jira/browse/EJBTHREE-660 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Ben Wang Assigned To: Ben Wang Fix For: EJB 3.0 RC9 - FD Current sfsb activation/passivation notification relies on read/writeExternal. This is semnatically not correct since replication also relies on serialization. So each replication would trigger a activation/passivation pair. I don't believe ejb3 specifies specifically activation/passivation to serialization (there is no word on how to perform passivation actually). So a better way is to decouple this. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-662) sfsb bean remove is not properly done

by Ben Wang (JIRA)

sfsb bean remove is not properly done -------------------------------------- Key: EJBTHREE-662 URL: http://jira.jboss.com/jira/browse/EJBTHREE-662 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Ben Wang Assigned To: Ben Wang Fix For: EJB 3.0 RC9 - FD Currently in StatefulRemoveInterceptor, when user calls @Remove, it removes directly the bean instance in the cache. However, this is incorrect when there is nested bean involved. Correct procedure is to do StatefulBeanContext.remove() that will remove it recursively. -- 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, 9 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2006