December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-792) Add support for JNDI bound SessionFactory

by C??dric Vidal (JIRA)

Add support for JNDI bound SessionFactory ----------------------------------------- Key: JBPM-792 URL: http://jira.jboss.com/jira/browse/JBPM-792 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: C??dric Vidal Assigned To: Tom Baeyens Today, jBPM manages the configuration of Hibernate which is fine in simple applications where jBPM is the main piece but in a enterprise application where jBPM is one of the many modules that are using Hibernate as a persistence mechanism, you don't want to configure your hibernate SessionFactory multiple times, so you want to configure your SessionFactory once, bind it to JNDI and tell jBPM to use it. It would be great if out of the box, jBPM would be able to lookup the SessionFactory it uses out of JNDI instead of configuring it locally. Regards, Cédric -- 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, 2 months

3
2
0 / 0

[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

19 years, 2 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-520) How to refer one rule in another

by Sridhar Ramaswamy (JIRA)

How to refer one rule in another -------------------------------- Key: JBRULES-520 URL: http://jira.jboss.com/jira/browse/JBRULES-520 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Environment: WSAD Reporter: Sridhar Ramaswamy Assigned To: Mark Proctor I have the following three rules created in a drl: rule "Sales" when abc: abcData( $abcName : abcName, $value: value > 20) then abc.setFlagColor("RED"); end rule "Count" when bcd: bcdData( $bcdName : bcdName, $count: count < 120) then abc.setFlagColor("RED"); end How to create a new rule which will use these rules, for instance rule "sales & count" when either rule "sales" is true or "count" is true and aaa: aaaData($aaaName: aaaName, $amount: amount < 1000) then aaa.setFlag("Critical"); end I am not able to call a rule into another rule to check that is also true. Thanks/Sri. -- 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, 2 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

19 years, 2 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

19 years, 2 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

19 years, 2 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

19 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-609) Decide the way to go forward (with or without Remoting)

by Ovidiu Feodorov (JIRA)

Decide the way to go forward (with or without Remoting) ------------------------------------------------------- Key: JBMESSAGING-609 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-609 Project: JBoss Messaging Issue Type: Task Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Alpha2 Conclude the http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971228 discussion thread and make a decision on how to go further: 1. Modify Remoting to include Messaging-specific requirements (asynchronicity, AMQP, etc) 2. Implement our own remoting solution. -- 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, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-832) Develop CacheSPI impl for use in JBoss JMX microkernel

by Brian Stansberry (JIRA)

Develop CacheSPI impl for use in JBoss JMX microkernel ------------------------------------------------------ Key: JBCACHE-832 URL: http://jira.jboss.com/jira/browse/JBCACHE-832 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.GA If we want JBC 2.0 to work in AS 4.2, we'll need a way to construct a CacheSPI via the 4.x microkernel/SARDeployer. Initial thoughts: 1) Create class "CacheSPIWrapper" that implements CacheSPI, plus exposes all the configuration-related mbean attributes from JBC 1.4. This is the class that's used for the "class" attribute of the mbean in the -service.xml file. 2) Class when instantiated also instantiates a Configuration object. When SARDeployer invokes the setters on the legacy mbean attributes, the values are passed through to the Configuration object. 3) In createService(), the Configuration object is passed to DefaultCacheFactory, which returns an instance of the standard CacheSPI impl. CacheSPIWrapper holds a ref to this object for use as a delegate. 4) CacheSPIWrapper implements CacheSPI by delegation to the standard object. If we decide we don't want to support use of JBC 2.0 in 4.2, this task can be closed. -- 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, 2 months

2
7
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 December 2006