November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBRULES-310) Better handling of primitive and object wrapper comparisons

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-310?page=all ] Edson Tirelli resolved JBRULES-310. ----------------------------------- Resolution: Won't Fix Assignee: Edson Tirelli (was: Mark Proctor) Version 3.1-m1 and above handle primitives nativelly and code works fine. Just rewrite the rule using primitives: rule "cov and biz income" when //the coverage amount is >= 15000 WorkItemWrapper(bizVal:bizIncome) //WorkItemWrapper with isAdmitted being true WorkItemWrapper( covAmount == ( bizVal+10000) ) then //Log Fired cov and biz income System.out.println("fired cov and biz income rule"); end > Better handling of primitive and object wrapper comparisons > ----------------------------------------------------------- > > Key: JBRULES-310 > URL: http://jira.jboss.com/jira/browse/JBRULES-310 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Leaps, Reteoo > Reporter: Joe Son > Assigned To: Edson Tirelli > Fix For: 3.1-m1 > > > I have a following rule set up where both bizIncome and covAmount return Integer object. > rule "cov and biz income" > when > //the coverage amount is >= 15000 > WorkItemWrapper(bizVal:bizIncome) //WorkItemWrapper with isAdmitted being true > WorkItemWrapper( covAmount == ( new Integer(bizVal.intValue()+10000) )) > then > //Log Fired cov and biz income > System.out.println("fired cov and biz income rule"); > > end > However, the rule doesn't fire even though they are both say 33000. > My initial set up is that covAmount and bizIncome both are returned as int primitive. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-537) BigDecimalFactory and BigIntegerFactory don't compile with java 1.5 source

by Geoffrey De Smet (JIRA)

BigDecimalFactory and BigIntegerFactory don't compile with java 1.5 source -------------------------------------------------------------------------- Key: JBRULES-537 URL: http://jira.jboss.com/jira/browse/JBRULES-537 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: All Affects Versions: 3.1-m1 Reporter: Geoffrey De Smet Assigned To: Mark Proctor Priority: Minor jbossrules\drools-core\src\main\java\org\drools\base\evaluators\BigIntegerFactory.java and BigIntegerFactory.java won't compile in 1.5 source because BigDecimal isn't a 100% backwards compatible from java 1.5 to 1.4, due to them generifying it. The fix is easy: just add some casts, the JVM does this at runtime anyway. For example: final BigDecimal comp = (BigDecimal) extractor.getValue( object1 ); return comp.compareTo( object2.getValue() ) < 0; This code turns red in java source=1.5 in IntelliJ IDEA (and in Eclipse I would expect the same?) Turn it into: ... return comp.compareTo( (BigDecimal) object2.getValue() ) < 0; I didn't create a patch as it's fast to fix: just copy-paste (BigDecimal) in the 2 classes's use of the compareTo method. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Closed: (JBAS-1342) Message Serialization

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1342?page=all ] Dimitris Andreadis closed JBAS-1342. ------------------------------------ Fix Version/s: (was: JBossAS-4.2.0.CR1) Resolution: Deferred Removing the fix version so it doesn't appear in the release notes. > Message Serialization > --------------------- > > Key: JBAS-1342 > URL: http://jira.jboss.com/jira/browse/JBAS-1342 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Adrian Brock > Attachments: JBAS-1342-SpyTextMessage.zip > > > The message body does not need to be deserialized on the server. > It could just be retained as byte[] > This will avoid unnecessary Object serialiation at the transport and persistent layer > inside the server. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2464) Support JMSX properties

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2464?page=all ] Dimitris Andreadis closed JBAS-2464. ------------------------------------ Fix Version/s: (was: JBossAS-4.2.0.CR1) Resolution: Deferred Removing the fix version so it doesn't appear in the release notes. > Support JMSX properties > ----------------------- > > Key: JBAS-2464 > URL: http://jira.jboss.com/jira/browse/JBAS-2464 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Adrian Brock > > Look at supporting other JMSX properties in JBossMQ -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-1342) Message Serialization

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1342?page=all ] Dimitris Andreadis reopened JBAS-1342: -------------------------------------- > Message Serialization > --------------------- > > Key: JBAS-1342 > URL: http://jira.jboss.com/jira/browse/JBAS-1342 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Adrian Brock > Fix For: JBossAS-4.2.0.CR1 > > Attachments: JBAS-1342-SpyTextMessage.zip > > > The message body does not need to be deserialized on the server. > It could just be retained as byte[] > This will avoid unnecessary Object serialiation at the transport and persistent layer > inside the server. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-2464) Support JMSX properties

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2464?page=all ] Dimitris Andreadis reopened JBAS-2464: -------------------------------------- > Support JMSX properties > ----------------------- > > Key: JBAS-2464 > URL: http://jira.jboss.com/jira/browse/JBAS-2464 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Adrian Brock > Fix For: JBossAS-4.2.0.CR1 > > > Look at supporting other JMSX properties in JBossMQ -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-770) leaked connection in SFSB injected EntityManager after persist, passivate/activate, persist

by William DeCoste (JIRA)

leaked connection in SFSB injected EntityManager after persist, passivate/activate, persist ------------------------------------------------------------------------------------------- Key: EJBTHREE-770 URL: http://jira.jboss.com/jira/browse/EJBTHREE-770 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: William DeCoste Assigned To: William DeCoste recreated in org.jboss.ejb3.test.stateful.RemoteUnitTestCase.testExtendedPersistencePassivation() -- 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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-600) org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase fails

by Tom Elrod (JIRA)

org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase fails -------------------------------------------------------------------- Key: JBREM-600 URL: http://jira.jboss.com/jira/browse/JBREM-600 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport-multiplex Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) When run org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase, the test fails. From debugging, the ServerInvoker's leaseManagement variable is not set to true when it's invoke() method is called (thus by-passing leasing). Also noticed when debugging that when Connector.addConnectionListener() calls: invoker.addConnectionListener(listener); that the invoker instance was MultiplexServerInvoker[master] (this is where the leaseManagement variable gets set to true) and when the PING invocation request is processed within ServerInvoker.invoke() method (where checks to see if leaseManagement variable is true and is not), the invoker instance is MultiplexServerInvoker[virtual:/127.0.0.1:5400->/127.0.0.1:1914]. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBESB-16) Basic HTTP deployment

by Johan Kumps (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-16?page=comments#action_12346162 ] Johan Kumps commented on JBESB-16: ---------------------------------- DONE > Basic HTTP deployment > --------------------- > > Key: JBESB-16 > URL: http://jira.jboss.com/jira/browse/JBESB-16 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Distribution > Reporter: Mark Little > Assigned To: Johan Kumps > Priority: Minor > Fix For: 4.0 RC1 > > Time Spent: 1 day, 4 hours > Remaining Estimate: 0 minutes > > Implement a basic HTTP deployment for ESB. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3799) Eclipse 3.2 deploys new EAR, JBoss trys to unload old EAR from memory but gives error before able to load new EAR.

by Melinda Savoy (JIRA)

Eclipse 3.2 deploys new EAR, JBoss trys to unload old EAR from memory but gives error before able to load new EAR. ------------------------------------------------------------------------------------------------------------------ Key: JBAS-3799 URL: http://jira.jboss.com/jira/browse/JBAS-3799 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.5.GA Environment: Windows XP, Eclipse 3.2 Reporter: Melinda Savoy Assigned To: Dimitris Andreadis Our dev team just installed Eclipse 3.2 and JBoss 4.0.5.GA on our local Window XP machines. When trying to run on server a JSP page from within the Eclipse 3.2 IDE I am getting the following error: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:620) java.lang.ClassLoader.loadClass(Unknown Source) org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:464) org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405) java.lang.ClassLoader.loadClass(Unknown Source) java.lang.ClassLoader.loadClassInternal(Unknown Source) org.acegisecurity.ui.ntlm.NtlmProcessingFilter.onPreAuthentication(NtlmProcessingFilter.java:344) org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:200) org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:110) org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:191) org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:148) org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:90) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.20 logs. It appears(?) that the issue is that Eclipse will rebuild and redeploy the EAR to JBoss while at the same time opening up IE and trying to load the JSP. JBoss eventually will see the new EAR and it has to go through a process of unloading the current EAR from memory and then reloading the new EAR. The error I see is happening when JBoss unloads the current EAR from memory as far as I can tell. -- 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, 6 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 November 2006