September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-447) correct NullPointer when processing PRIORITY rule tag

by G￡bor Lipt￡k (JIRA)

correct NullPointer when processing PRIORITY rule tag ----------------------------------------------------- Key: JBRULES-447 URL: http://jira.jboss.com/jira/browse/JBRULES-447 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 3.0.4 Reporter: G￡bor Lipt￡k Assigned To: Mark Proctor Attachments: jboss_rules_priority.diff diff attached. I'm not sure if using LshBuilder is the correct thing to do ... -- 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, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (JBRULES-445) behavior of globals?

by G￡bor Lipt￡k (JIRA)

behavior of globals? -------------------- Key: JBRULES-445 URL: http://jira.jboss.com/jira/browse/JBRULES-445 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.4 Reporter: G￡bor Lipt￡k Assigned To: Mark Proctor Priority: Minor It seems that the value of DRL globals without external env backup is removed between rules: package globaltest import Policy; global java.lang.String text; rule "Foo" salience 999 when Policy() then text="foo"; System.out.println("foo+"+text); end rule "Bar" salience 998 when Policy() then System.out.println("bar+"+text); text="bar"; System.out.println("bar+"+text); end results in: foo+foo bar+null bar+bar The documentation does not seem to provide details if this is the expected behavior. Please comment. 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

18 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-123) On preview topic view "Powered by JBoss Portal" tag flies around

by Ryszard Kozmik (JIRA)

On preview topic view "Powered by JBoss Portal" tag flies around ---------------------------------------------------------------- Key: JBFORUMS-123 URL: http://jira.jboss.com/jira/browse/JBFORUMS-123 Project: JBoss Forums Issue Type: Bug Affects Versions: 1.0.0 Alpha Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Minor While creating topic with preview the theme tag "Powered by JBoss Portal / Theme by ***" flies over forums. -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-742) PojoCache needs to propogate POJO events to remote nodes

by Ben Wang (JIRA)

PojoCache needs to propogate POJO events to remote nodes -------------------------------------------------------- Key: JBCACHE-742 URL: http://jira.jboss.com/jira/browse/JBCACHE-742 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ben Wang Assigned To: Ben Wang Priority: Critical Fix For: PojoCache 2.1.0 Currently, in the new 2.0 design, the POJO events, attach, detach, and field updates are local only. That is, remote node won't have any notification. This is an defficency. To crroect this, we will need to have another RPC layer that sits on the same channel as the the Cache to propogate the events. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-657) StatefulBean passivation is broken (ClassCastException in org.jboss.ejb3.stateful.NestedStatefulBeanContext)

by Carlo de Wolf (JIRA)

StatefulBean passivation is broken (ClassCastException in org.jboss.ejb3.stateful.NestedStatefulBeanContext) ------------------------------------------------------------------------------------------------------------ Key: EJBTHREE-657 URL: http://jira.jboss.com/jira/browse/EJBTHREE-657 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Carlo de Wolf Priority: Critical StatefulBean passivation is broken, because there is a conflict between what gets serialized (attribute contains) and what gets unserialized (attribute beanMO). 11:41:37,109 ERROR [STDERR] Caused by: java.lang.ClassCastException: java.util.ArrayList 11:41:37,109 ERROR [STDERR] at org.jboss.ejb3.stateful.NestedStatefulBeanContext.readExternal(Neste dStatefulBeanContext.java:60) 11:41:37,109 ERROR [STDERR] at org.jboss.serial.persister.ExternalizePersister.readData(Externalize Persister.java:72) 11:41:37,109 ERROR [STDERR] at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectD escriptionFromStreaming(ObjectDescriptorFactory.java:411) 11:41:37,109 ERROR [STDERR] at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromD escription(ObjectDescriptorFactory.java:81) 11:41:37,109 ERROR [STDERR] at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectIn put.readObject(DataContainer.java:639) 11:41:37,109 ERROR [STDERR] at org.jboss.serial.persister.ObjectInputStreamProxy.readObjectOverride (ObjectInputStreamProxy.java:68) 11:41:37,109 ERROR [STDERR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:333) 11:41:37,109 ERROR [STDERR] at java.util.ArrayList.readObject(ArrayList.java:592) 11:41:37,109 ERROR [STDERR] ... 74 more -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-511) JDBC and Transaction close/cleanup operations should be bullet-proofed JDBCChannelMapper and elsewhere.

by Joel Lindheimer (JIRA)

JDBC and Transaction close/cleanup operations should be bullet-proofed JDBCChannelMapper and elsewhere. ------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-511 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-511 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: Windows Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov I am concerned with object close and wrap.end() methods in JDBCChannelMapper possibly being bypassed if an exception is thrown in the rs.close(), ps.close() blocks (code below is an example of what is currently in the JDBCChannelMapper). JDBCChannelMapper : public DurableSubscription getDurableSubscription(String clientID, String subscriptionName, MessageStore ms, PersistenceManager pm, MemoryManager mm) throws Exception { // Look in memory first DurableSubscription sub = getDurableSubscription(clientID, subscriptionName); if (sub != null) { return sub; } //Now look in the db Connection conn = null; PreparedStatement ps = null; ResultSet rs = null; TransactionWrapper wrap = new TransactionWrapper(); try { conn = ds.getConnection(); ps = conn.prepareStatement(selectDurableSub); (do stuff here... ) return sub; } finally { if (rs != null) { // JL what if it blose up here? rs.close(); } if (ps != null) { // JL or here? ps.close(); } if (conn != null) { // or here? conn.close(); } wrap.end(); } } -- 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, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-500) Special connective "or" constraint

by Michael Neale (JIRA)

Special connective "or" constraint ---------------------------------- Key: JBRULES-500 URL: http://jira.jboss.com/jira/browse/JBRULES-500 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo, Rule Assemply/SPI Reporter: Michael Neale Assigned To: Mark Proctor Would be nice to have some construct like Person(address == null or age < 30) which would kind of short circuit (ideally). Could be done as a special thing with alpha nodes, or another type of join node, or something else. This is a common problem to have for users. -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-121) Check recovery

by Mark Little (JIRA)

Check recovery -------------- Key: JBTM-121 URL: http://jira.jboss.com/jira/browse/JBTM-121 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-463) audit log for all system actions

by Michael Neale (JIRA)

audit log for all system actions -------------------------------- Key: JBRULES-463 URL: http://jira.jboss.com/jira/browse/JBRULES-463 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3576) Unified Security Context

by Anil Saldhana (JIRA)

Unified Security Context ------------------------ Key: JBAS-3576 URL: http://jira.jboss.com/jira/browse/JBAS-3576 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta Currently the roles are an aspect of the Subject that is populated as part of the Jaas Authentication process (in the derivatives of the AbstractServerLoginModule). There is a need for the establishment of a security context to hold the roles, authoriation info etc. -- 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, 4 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006