August 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1308) Genericize getData() Map returned by notication events

by Brian Stansberry (JIRA)

Genericize getData() Map returned by notication events ------------------------------------------------------ Key: JBCACHE-1308 URL: http://jira.jboss.com/jira/browse/JBCACHE-1308 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.1.0.GA Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Minor The Map returned by getData() in the various notification events is not genericized. AFAICT it should use the same <K, V> as the Cache<K, V> that emits the events. Relevant event classes are NodeActivatedEvent, NodeLoadedEvent, NodeModifiedEvent, NodePassivatedEvent. -- 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

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1015) Notify user (via callback) if application of (async or sync) replication fails

by Bela Ban (JIRA)

Notify user (via callback) if application of (async or sync) replication fails ------------------------------------------------------------------------------ Key: JBCACHE-1015 URL: http://jira.jboss.com/jira/browse/JBCACHE-1015 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Bela Ban Assigned To: Manik Surtani If a replication cannot be applied (no transactions), then invoke a callback notifying the application, so that some corrective action can be taken -- 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

15 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-5747) Upgrade to the latest JSF implementation 1.2_09 (from 1.2_08)

by Carsten Hoehne (JIRA)

Upgrade to the latest JSF implementation 1.2_09 (from 1.2_08) ------------------------------------------------------------- Key: JBAS-5747 URL: http://jira.jboss.com/jira/browse/JBAS-5747 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Reporter: Carsten Hoehne Fix For: JBossAS-5.0.0.CR2 Please have a look here: http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/... There seems to be a bug in 1.2_08 So it has to be upgraded. -- 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

15 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1702) BRMS: uploading a decision table breaks the package

by Jaroslaw Kijanowski (JIRA)

BRMS: uploading a decision table breaks the package --------------------------------------------------- Key: JBRULES-1702 URL: https://jira.jboss.org/jira/browse/JBRULES-1702 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 I create a rule, then upload a decision table (see attached) and: - if I compile the package it looks good, however it isn't, I cannot run a test scenario for example, because I will get missing imports of facts from the first rule; - if I create another rule, I won't be able to compile the package due to missing imports; I guess the reason for this is that the decision table adds its own import and package statements in the middle of the rule file. Here's the source of the package with one "regular" rule and one rule coming from the decision table: package myNewPAckage import com.model.Person import com.model.Alarm import com.model.Message rule "first" dialect "mvel" when Alarm( ) then Person fact0 = new Person(); fact0.setAge( 18 ); insert( fact0 ); end package XLSRules; #generated from Decision Table import com.model.Message; #From row number: 11 rule "HelloWorld_11" when m:Message(status == Message.HELLO) then System.out.println(m.getMessage()); m.setMessage("Goodbye cruel world");update(m); m.setStatus(Message.GOODBYE);update(m); end #From row number: 12 rule "HelloWorld_12" when m:Message(status == Message.GOODBYE) then System.out.println(m.getMessage()); end -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-5833) maxMessages in activation spec wrongly sets maxSession

by Takayoshi Kimura (JIRA)

maxMessages in activation spec wrongly sets maxSession ------------------------------------------------------ Key: JBAS-5833 URL: https://jira.jboss.org/jira/browse/JBAS-5833 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1 Reporter: Takayoshi Kimura Assignee: Jesper Pedersen This is simple error in the setter method: public void setMaxMessages(int maxMessages) { this.maxSession = maxMessages; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5761) Rename conf/*-service.xml to *-beans.xml to be consistent with naming conventions

by Scott M Stark (JIRA)

Rename conf/*-service.xml to *-beans.xml to be consistent with naming conventions --------------------------------------------------------------------------------- Key: JBAS-5761 URL: http://jira.jboss.com/jira/browse/JBAS-5761 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR2 The extension -service.xml is usually associated with JMX, but in this case the file is used with the microcontainer. I know that file naming conventions (e.g., *-service.xml) apply only in the deploy directory, and not in conf, but it can be initially confusing. -- 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

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5634) The drive name in jca sample for mssql is wrong

by Jason Oliveira (JIRA)

The drive name in jca sample for mssql is wrong ----------------------------------------------- Key: JBAS-5634 URL: http://jira.jboss.com/jira/browse/JBAS-5634 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: JBossAS-4.2.2.GA Environment: N/A Reporter: Jason Oliveira Assigned To: Samson Kittoli The drive name in jca sample for mssql is wrong. In the jca sample (tamplates for datasource configuration) the mssql-ds.xml speficies the driver-class like: com.microsoft.sqlserver.jdbc.SQLServerDriver But the driver-class for MSSQL2000 is: com.microsoft.jdbc.sqlserver.SQLServerDriver -- 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

15 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1713) Status message continue to show building package even when it errored out

by Seegler Ittyavirah (JIRA)

Status message continue to show building package even when it errored out ------------------------------------------------------------------------- Key: JBRULES-1713 URL: https://jira.jboss.org/jira/browse/JBRULES-1713 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.7 Reporter: Seegler Ittyavirah Assignee: Mark Proctor Try to build a package that will result in a build error(a wrong rule) Click on the "Build Package" button in "Verify and assemble package" window This shows a status message "Validating and building package, please wait..." in "Verify and assemble package" window Now the package build errors out and shows an error popup window with message "An error occurred executing the action." close the error popup by clicking on 'x' button However old message "Validating and building package, please wait..." still remains on the "Verify and assemble package" window -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-877) TreeCache usage should not depend on trove.jar

by Galder Zamarreno (JIRA)

TreeCache usage should not depend on trove.jar ---------------------------------------------- Key: JBCACHE-877 URL: http://jira.jboss.com/jira/browse/JBCACHE-877 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1 Reporter: Galder Zamarreno Assigned To: Manik Surtani Priority: Minor A customer is upgrading from JBC 1.1 to 1.4.0.SP1 and even though it only uses plain TreeCache, it gets a NoClassDefFoundError for trove classes. 2006-11-23 13:19:03,781 ERROR RpcDispatcher exception=java.lang.NoClassDefFoundError: gnu/trove/TObjectHashingStrategy This is a TreeCacheAop/PojoCache dependency and therefore, should be isolated and attempted to be loaded only when PojoCache used. -- 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

15 years, 9 months

7
28
0 / 0

[JBoss JIRA] Created: (JBRULES-1703) BRMS: test scenario should show which fileds don't match

by Jaroslaw Kijanowski (JIRA)

BRMS: test scenario should show which fileds don't match -------------------------------------------------------- Key: JBRULES-1703 URL: https://jira.jboss.org/jira/browse/JBRULES-1703 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 I'll attach screenshots... what I mean is that when I run this test scenario, I would expect to see a green icon next to: [Person] field [age] was [123]. and [Person] field [name] was [Pierre]. and a yellow next to [Person] field [sex] was [m] expected [f]. (like it is now). These first two fields (age and name) should be green in the 1st screenshot; have a look at the 2nd screenshot, I didn't change anything, just the 3rd field to match the expectations with the results. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2008