October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1034) Allow connection factories to be created programmatically

by Tim Fox (JIRA)

Allow connection factories to be created programmatically --------------------------------------------------------- Key: JBMESSAGING-1034 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1034 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 We should allow connection factories to be created programmatically on the client side - this allows people to use JBM when they don't have JNDI. -- 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

16 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (GPD-169) Transition text position not saving

by David Roberts (JIRA)

Transition text position not saving ----------------------------------- Key: GPD-169 URL: http://jira.jboss.com/jira/browse/GPD-169 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM JPDL Designer 3.1.0.GA Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1 Reporter: David Roberts Assigned To: Koen Aers Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem: All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. -- 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

16 years, 7 months

6
17
0 / 0

[JBoss JIRA] Created: (EJBTHREE-820) Hardcoded Destination Manager Reference

by Juha Lindfors (JIRA)

Hardcoded Destination Manager Reference --------------------------------------- Key: EJBTHREE-820 URL: http://jira.jboss.com/jira/browse/EJBTHREE-820 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: JBoss AS 4.0.5.GA + EJB 3.0 RC9 + JBoss Messaging Reporter: Juha Lindfors Priority: Minor When deploying an MDB that has been configured wrongly with a non existing destination the dubious feature that creates a temporary destination automatically fails due to hard coded destination manager reference that no longer exists if JBoss Messaging is used instead of JBossMQ. MessagingContainer: protected void createTemporaryDestination(Class type, String jndiSuffix) throws Exception 513 ObjectName destinationManagerName = new ObjectName("jboss.mq:service=DestinationManager"); Apologies, did not check if this issue exists still with the current code in the head/trunk, just needed to write it down before I forget it. -- 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

16 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3402) Web Console and Firefox

by Vladimir Gendler (JIRA)

Web Console and Firefox ----------------------- Key: JBAS-3402 URL: http://jira.jboss.com/jira/browse/JBAS-3402 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Affects Versions: JBossAS-4.0.4.GA Environment: MS W2000 SP4 Reporter: Vladimir Gendler Assigned To: Dimitris Andreadis Web Console output in Mozilla Firefox (and Seamonkey) is messed up. Compare the attached archive with snapshots from Mozilla Firefox and MSIE. -- 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

16 years, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-746) Ascertain whether any methods and attributes exposed by TreeCacheMBean can be marked serializable

by Jerry Gauthier (JIRA)

Ascertain whether any methods and attributes exposed by TreeCacheMBean can be marked serializable ------------------------------------------------------------------------------------------------- Key: JBCACHE-746 URL: http://jira.jboss.com/jira/browse/JBCACHE-746 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jerry Gauthier Assigned To: Jerry Gauthier Priority: Minor When TreeCacheMBean is accessed remotely via an mbean server such as jconsole, numerous attributes and methods are marked as problematic because they aren't serializable. While many are undoubtedly not serializable, it's worth reviewing the list to see if it would be appropriate to mark any additional attributes or method parameters as serializable. -- 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

16 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-687) General purpose BRMS query functionality

by Michael Neale (JIRA)

General purpose BRMS query functionality ---------------------------------------- Key: JBRULES-687 URL: http://jira.jboss.com/jira/browse/JBRULES-687 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

16 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4217) CheckValidConnectionSQL is not Serializable

by Purush Rudrakshala (JIRA)

CheckValidConnectionSQL is not Serializable ------------------------------------------- Key: JBAS-4217 URL: http://jira.jboss.com/jira/browse/JBAS-4217 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.CR1, JBossAS-4.0.5.GA, JBossAS-3.2.7 Final Reporter: Purush Rudrakshala Please refer to Bug 1192. This was closed incorrectly. The problem still exists in JBoss 3.2.7, 4.0.5 and 4.2 CR1 -- 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

16 years, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1138) User extensible configuration should be centralised - configuration settings allowing <class> and <properties> defintions

by Galder Zamarreno (JIRA)

User extensible configuration should be centralised - configuration settings allowing <class> and <properties> defintions ------------------------------------------------------------------------------------------------------------------------- Key: JBCACHE-1138 URL: http://jira.jboss.com/jira/browse/JBCACHE-1138 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Manik Surtani Priority: Minor Fix For: 2.1.0.GA There's a common pattern in configuration set for: - cache loader - buddy locator - and forthcoming singleton store cache loader The pattern is that all three are user extensible in the sense that: - user can redefine the class used to provide the functionality - properties of this functionality can be defined via <properties> element We should consolidate this into some kind of UserExtensibleConfigurationElement that includes class and properties logic. -- 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

16 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1251) Cannot remove a category if it was used in an archived rule

by Shahad Ahmed (JIRA)

Cannot remove a category if it was used in an archived rule ----------------------------------------------------------- Key: JBRULES-1251 URL: http://jira.jboss.com/jira/browse/JBRULES-1251 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.1 Reporter: Shahad Ahmed Assigned To: Mark Proctor The BRMS manual says you can delete a category if it is not in use by any current version of a rule. However, if you archive a rule that uses a category X, say, then you cannot remove category X in the Admin section, even if no other rules in the repository use category X. You get the following error message: "The category still has some assets linked to it. You will need to remove the links so you can delete the cateogory" (PS not the spelling mistake cateogory in the error message) Either the manual (Section 9.4.2.2) should be updated with a warning that you cannot remove a category used by archived rules, or is there is a bug in the remove category functionality for archived assets, as you can remove categories which are only used in old versions of a rule? -- 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

16 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1292) BRMS ignores "initial description" entered when creating new "Business rule using a DSL (text editor)" rule

by Phil Verghese (JIRA)

BRMS ignores "initial description" entered when creating new "Business rule using a DSL (text editor)" rule ----------------------------------------------------------------------------------------------------------- Key: JBRULES-1292 URL: http://jira.jboss.com/jira/browse/JBRULES-1292 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.2 Reporter: Phil Verghese Assigned To: Mark Proctor When creating a new rule asset through the BRMS using the type "Business rule using a DSL (text editor)", the initial description you put in is ignored. You always get the description "A dsl is a language mapping from a domain specific language to the rule language." -- 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

16 years, 7 months

6
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007