March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-191) Update CORBA examples

by Mark Little (JIRA)

Update CORBA examples --------------------- Key: JBTM-191 URL: http://jira.jboss.com/jira/browse/JBTM-191 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, JTS Implementation Affects Versions: 4.2.2 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.6 The CORBA examples are out-of-date, referring to BOA classes. -- 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: (JBTM-204) Provide support for Spring to use JBossTM

by Mark Little (JIRA)

Provide support for Spring to use JBossTM ----------------------------------------- Key: JBTM-204 URL: http://jira.jboss.com/jira/browse/JBTM-204 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Reporter: Mark Little Assigned To: Jonathan Halliday Just a thought. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-873) Upgrade to Hibernate 3.2.2 and Javassist 3.4

by Galder Zamarreno (JIRA)

Upgrade to Hibernate 3.2.2 and Javassist 3.4 -------------------------------------------- Key: EJBTHREE-873 URL: http://jira.jboss.com/jira/browse/EJBTHREE-873 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD Reporter: Galder Zamarreno Fix For: EJB 3.0 RC10 - FD Upgrade to Hibernate 3.2.2 and Javassist 3.4, amongst others, to fix the permanent generation leak. -- 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-901) move optimiticentity test to 4.2 branch

by William DeCoste (JIRA)

move optimiticentity test to 4.2 branch --------------------------------------- Key: EJBTHREE-901 URL: http://jira.jboss.com/jira/browse/EJBTHREE-901 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 4.2.0 CR1 Reporter: William DeCoste Assigned To: William DeCoste Fix For: AS 4.2.0 CR2 -- 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
4
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

19 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies

by Galder Zamarreno (JIRA)

Provide a clean jboss-messaging-client.jar without containing external dependencies ----------------------------------------------------------------------------------- Key: JBMESSAGING-804 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-804 Project: JBoss Messaging Issue Type: Feature Request Components: Build System Affects Versions: 1.0.1.SP3, 1.2.0.Beta1 Reporter: Galder Zamarreno Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2, 1.0.1.SP4 We've installed JBoss messaging instead of JBossMQ and updated our application to connect to this. We have to include jboss-messaging-client.jar to be able to use it, but now the following problem arises: jboss-messaging-client.jar has log4j classes in it, which are of an old version. Therefore, our .war cannot deploy because it uses methods of log4j of the newer version (e.g. Logger.isTraceEnabled()). To your approach of patching jboss-messaging-client.jar: maybe we'll try it, but I'm afraid it includes more classes that may clash with our system... What we need is a clean jboss-messaging-client.jar file, without external dependencies, but I don't want to build it myself as it makes maintaining our JBoss setup very hard. -- 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

6
14
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-725) Add a release-admin check that would cleanly stop the installation process if ant version is too old

by Ovidiu Feodorov (JIRA)

Add a release-admin check that would cleanly stop the installation process if ant version is too old ---------------------------------------------------------------------------------------------------- Key: JBMESSAGING-725 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-725 Project: JBoss Messaging Issue Type: Feature Request Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.CR1 ... and avoid cryptic failures like this one: [C:/temp/jboss-messaging-1.2.0.Beta1/util] ant -f release-admin.xml Buildfile: release-admin.xml default: BUILD FAILED C:\temp\jboss-messaging-1.2.0.Beta1\util\release-admin.xml:36: The following error occurred while ex ecuting this line: C:\temp\jboss-messaging-1.2.0.Beta1\util\release-admin.xml:519: Class org.apache.tools.ant.taskdefs. ConditionTask doesn't support the nested "length" element. Total time: 1 second [C:/temp/jboss-messaging-1.2.0.Beta1/util] ant -version Apache Ant version 1.6.2 compiled on July 16 2004 -- 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: (JBMESSAGING-925) Remove requirement to deploy JBM scoped in JB AS <= 4.2

by Tim Fox (JIRA)

Remove requirement to deploy JBM scoped in JB AS <= 4.2 ------------------------------------------------------- Key: JBMESSAGING-925 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-925 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.GA Reporter: Tim Fox Priority: Critical Fix For: 1.2.0.SP1 Currently JBM needs to be deployed as a scoped deployment in every all the GA releases of JBoss AS. This causes considerable configuration headaches for users and more than likely acts as a major barrier to adoption of JBM. We currently scope because we use more recent versions of JBoss Remoting and JBoss AOP than the versions deployed in JBAS. It appears that, other than JBM, only EJB3 and parts of JBoss WS actually use AOP and remoting so instead of deploying scoped we should first verify whether WS and EJB3 work with the later versions of AOP and remoting, and if not we should patch AOP and remoting to get them to work. Then we can overwrite the versions of remoting and aop in server/lib in the AS during the JBM install procedure and deploy unscoped - this would be a huge win for the project. -- 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: (JBRULES-706) Editor widgets to report "dirty" flat when editied

by Michael Neale (JIRA)

Editor widgets to report "dirty" flat when editied -------------------------------------------------- Key: JBRULES-706 URL: http://jira.jboss.com/jira/browse/JBRULES-706 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

19 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBFORUMS-193) Change attachments view

by Ryszard Kozmik (JIRA)

Change attachments view ----------------------- Key: JBFORUMS-193 URL: http://jira.jboss.com/jira/browse/JBFORUMS-193 Project: JBoss Forums Issue Type: Sub-task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC Attachments view have to be rewritten to new L&F. -- 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

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 March 2007