September 2006 - jboss-jira - Jboss List Archives

[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: (JBBUILD-323) JBossBuild needs to be able to calculate component version using highest common denominator algorithm

by Alex Pinkin (JIRA)

JBossBuild needs to be able to calculate component version using highest common denominator algorithm ----------------------------------------------------------------------------------------------------- Key: JBBUILD-323 URL: http://jira.jboss.com/jira/browse/JBBUILD-323 Project: JBoss Build System Issue Type: Feature Request Affects Versions: JBossBuild-1.1 DR2 Reporter: Alex Pinkin We've already had this discussion, and thought that it's not easy to implement. However, I do think we need this done since I don't want all projects to enumerate all their 3rd party dependencies in build-thirdparty.xml. Example: these products include the following javassist versions 1. aop 1.5.0.GA: javassist 3.2.0.CR1, 3.2.0.CR2, 3.3.0.GA 2. ws 1.0.0.GA: javassist 3.2.0.CR1, 3.2.0.CR2, 3.3.0.GA 3. ejb3 1.0.0.CR8: javassist 3.2.0.CR1, 3.2.0.CR2, 3.2.0.GA JBossBuild needs to be able to determine that javassist 3.2.0.CR2 is the highest common denominator. Current behaviour is that JBossBuild takes the highest version of the component whenever it runs into it for the first time during the dependency graph traversal. Does Maven already support this? It seems like this should be one of the core maven features. Could you please look more info feasibility of implementing this in JBossBuild? -- 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] Created: (JBPM-734) org.jbpm.util.XmlException: couldn't parse xml

by Ivan Garcia (JIRA)

org.jbpm.util.XmlException: couldn't parse xml ---------------------------------------------- Key: JBPM-734 URL: http://jira.jboss.com/jira/browse/JBPM-734 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: Ivan Garcia Assigned To: Tom Baeyens This code try{ String cfg = "<jbpm-configuration>"; cfg += "</jbpm-configuration>"; jbpmConfiguration = JbpmConfiguration.parseXmlString(cfg); }catch(Exception e){ e.printStackTrace(); } launch this exception, org.jbpm.util.XmlException: couldn't parse xml at org.jbpm.util.XmlUtil.parseXmlInputSource(XmlUtil.java:78) at org.jbpm.util.XmlUtil.parseXmlResource(XmlUtil.java:60) at org.jbpm.configuration.ObjectFactoryParser.parseElementsFromResource(ObjectFactoryParser.java:104) at org.jbpm.JbpmConfiguration.parseObjectFactory(JbpmConfiguration.java:299) at org.jbpm.JbpmConfiguration.parseXmlString(JbpmConfiguration.java:318) Caused by: java.net.MalformedURLException at java.net.URL.<init>(URL.java:601) at java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.jbpm.util.XmlUtil.parseXmlInputSource(XmlUtil.java:76) ... 6 more and i dont know why :-( Thanks -- 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
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-764) Update docs, examples and tutorial to reflect 2.0.0 API

by Manik Surtani (JIRA)

Update docs, examples and tutorial to reflect 2.0.0 API ------------------------------------------------------- Key: JBCACHE-764 URL: http://jira.jboss.com/jira/browse/JBCACHE-764 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 -- 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] Created: (JGRP-328) MultiplexerTest.testStateTransferWithReconnect() has leftover threads if run with -Dstack=tcp

by Bela Ban (JIRA)

MultiplexerTest.testStateTransferWithReconnect() has leftover threads if run with -Dstack=tcp --------------------------------------------------------------------------------------------- Key: JGRP-328 URL: http://jira.jboss.com/jira/browse/JGRP-328 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.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

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-460) Please allow ftp downloads to "resume"

by hoogenbj (JIRA)

Please allow ftp downloads to "resume" -------------------------------------- Key: JBRULES-460 URL: http://jira.jboss.com/jira/browse/JBRULES-460 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Any Reporter: hoogenbj Assigned To: Mark Proctor Priority: Minor Hi Guys In my part of the world (South Africa) we still get dropped connections and here a 128kbps connection counts as broadband. It is extremely &*^&^$%#$ annoying if I lose a connection while trying to download a 23MB file (JBoss Rules 3.0.4 binary with deps) and I have to start from the beginning because your ftp server does not allow "resume". (I've already made 3 attempts today) PLEASE PLEASE PLEASE change it. Other parts of JBoss do allow it so why not you? I'm not sure why you disallow it. Maybe you think that people multiplexing a download over multiple connections (with DAP) put too much load on the server? Think about it: you are actually increasing the load by not allowing it, because someone like me have to make multiple attempts at downloading something before succeeding. If I have to try 3 times and come close to succeeding the first two times, it is effectively the same as three people downloading the same software. Allow resume and I'll succeed sooner and go away sooner. Again, PUHHLEASSEEE! Regards Johan Hoogenboezem -- 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] Created: (JBRULES-469) function name overloading

by Mark Proctor (JIRA)

function name overloading ------------------------- Key: JBRULES-469 URL: http://jira.jboss.com/jira/browse/JBRULES-469 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Reporter: Mark Proctor Assigned To: Mark Proctor Currently the function resolver is limited with regards to overloading and you can only use the same function name once in a package. We need to have more correct overloading and ofcourse handle multiple versions of the same function name in a package. -- 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
1
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

19 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-3724) NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port

by Grant Quimby (JIRA)

NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port -------------------------------------------------------------------------------------------------------- Key: JBAS-3724 URL: http://jira.jboss.com/jira/browse/JBAS-3724 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB3, Remoting Affects Versions: JBossAS-4.0.4.GA Environment: One JBoss 4.0.4.GA install with two instances, one on the default ports and one on ports with an increase of 1000 on all port numbers. Reporter: Grant Quimby Assigned To: Dimitris Andreadis Priority: Blocker When trying to access a remote application that is running in a server instance that does not have the default InvokerLocator port (3873) the remote caller recieves a NotFoundInDispatcherException when trying to call a method in the EJB3 Stateless Session Bean as the EJB3 Session Bean's InvokerLocator is at port 4873 and not port 3873 where the Remote Proxy looks. Similar issue for Service Beans at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89537 This is okay presently but in approximately two weeks we need to be running four instances with Session beans in two of them, which is currently not possible in a production version. -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3726) Introduce basic twiddle tests in the testsuite

by Dimitris Andreadis (JIRA)

Introduce basic twiddle tests in the testsuite ---------------------------------------------- Key: JBAS-3726 URL: http://jira.jboss.com/jira/browse/JBAS-3726 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.6.CR1 We currently have no automated tests for twidde. -- 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
11
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 September 2006