February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-2577) isolating Hibernate as an internal impl detail

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2577?page=all ] Dimitris Andreadis updated JBAS-2577: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta4) Move to CR1. > isolating Hibernate as an internal impl detail > ---------------------------------------------- > > Key: JBAS-2577 > URL: http://jira.jboss.com/jira/browse/JBAS-2577 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Steve Ebersole > Assigned To: Steve Ebersole > Fix For: JBossAS-5.0.0.CR1 > > > Currently Hibernate is used within JBossAS for EJB3 as well as the Hibernate-intg code, with plans/discussions to expand usage to JBoss Messaging and JBossMQ. This represents Hibernate usage as an internal implementation detail > Additionally, Hibernate is also used within JBossAS by user applications. This represents Hibernate usage as a deployment detail. > Currently, the two are not isolated from each other. Thus, a user attempting to bundle Hibernate with their application is actually using the Hibernate bundled with EJB3 and/or the integration code. This can cause problems when we have internal usage and external usage needing to rely on different releases of Hibernate. > Need to devise a scheme to isolate the internal usages of Hibernate. Two potential solutions: > 1) source-level import and package renaming of Hibernate code (i.e. org.jboss.hibernate) > 2) some form of classloader isolation -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-2505) Hibernate integration in JBoss5

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2505?page=all ] Dimitris Andreadis resolved JBAS-2505. -------------------------------------- Resolution: Done Close the parent issue. > Hibernate integration in JBoss5 > ------------------------------- > > Key: JBAS-2505 > URL: http://jira.jboss.com/jira/browse/JBAS-2505 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > Assigned To: Steve Ebersole > Fix For: JBossAS-5.0.0.Beta4 > > > A containing task for Hiberate integration issues for the JBoss5 release -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures

by Scott M Stark (JIRA)

Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures ---------------------------------------------------------------------------- Key: JBAS-4292 URL: http://jira.jboss.com/jira/browse/JBAS-4292 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, Test Suite Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta3 If one adds a checkIncomplete call to validate a deployment in the legacy org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional failures and memory leaks that prevent the run from completing. It appears that tests are not cleaning up after failed deployments. -- 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, 3 months

6
12
0 / 0

[JBoss JIRA] Created: (JBAS-4647) Track jboss and thirdparty dependencies upgrades for JBoss 5.0.0.CR1

by Dimitris Andreadis (JIRA)

Track jboss and thirdparty dependencies upgrades for JBoss 5.0.0.CR1 -------------------------------------------------------------------- Key: JBAS-4647 URL: http://jira.jboss.com/jira/browse/JBAS-4647 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Fix For: JBossAS-5.0.0.CR1 Create subtasks to track jboss and thirdparty dependencies. -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBAS-2251) Fix JBoss Cache / AS integration issues

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2251?page=comments#action_12397795 ] Dimitris Andreadis commented on JBAS-2251: ------------------------------------------ Can we close this? > Fix JBoss Cache / AS integration issues > --------------------------------------- > > Key: JBAS-2251 > URL: http://jira.jboss.com/jira/browse/JBAS-2251 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Adrian Brock > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.0.Beta4 > > > The JBossCache standalone build includes: > jboss-aop.jar (ok - should be standalone project) > jboss-common.jar (ok - should be standalone project(s)) > jboss-j2ee.jar (TransactionManager interfaces) > jboss-jmx.jar (only for JBossNotificationBroadcasterSupport leaking from jboss-system.jar?) > jboss-minimal.jar (for MarshalledValue, etc.) > jboss-system.jar (for ServiceMBeanSupport) > We are heading for a fall on this (not to mention the other thirdparty jars that could get out-of-sync) > Some of this will probably have to wait until we have the proper federated build. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5196) Add a jboss.messaging.ServerPeerID system property to ServerPeer configuration in messaging-service.xml

by Dimitris Andreadis (JIRA)

Add a jboss.messaging.ServerPeerID system property to ServerPeer configuration in messaging-service.xml ------------------------------------------------------------------------------------------------------- Key: JBAS-5196 URL: http://jira.jboss.com/jira/browse/JBAS-5196 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JB5-Messaging Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta4 A quick solution to allow the creation of insta-clusters. JBoss Messaging ServerPeer needs a unique/persistent id (positive integer) to work, so allow the override of this from the command line. A better solution for automatically assigning unique/persistent server ids should found. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-518) Post condition of InstanceAdvisorDelegate.initializeAspects is not aspect != null

by Carlo de Wolf (JIRA)

Post condition of InstanceAdvisorDelegate.initializeAspects is not aspect != null --------------------------------------------------------------------------------- Key: JBAOP-518 URL: http://jira.jboss.com/jira/browse/JBAOP-518 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR3 Reporter: Carlo de Wolf I have an instance advisor, but no instance aspects. This leads into: java.lang.NullPointerException at org.jboss.aop.InstanceAdvisorDelegate.getPerInstanceAspect(InstanceAdvisorDelegate.java:182) at org.jboss.aop.GeneratedInstanceAdvisorMixin.getPerInstanceAspect(GeneratedInstanceAdvisorMixin.java:80) at org.jboss.ejb3.test.ejbthree1023.DefaultLocalBean$DefaultLocalBeanInstanceAdvisor.getPerInstanceAspect(DefaultLocalBean$DefaultLocalBeanInstanceAdvisor.java) (only reproducable with EJBTHREE-1174 patch #47) -- 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, 3 months

2
7
0 / 0

[JBoss JIRA] Updated: (JBREM-318) add remoting based chat sample

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-318?page=all ] Ron Sigal updated JBREM-318: ---------------------------- Fix Version/s: 2.4.1.Beta (was: 2.4.0.CR1 (Pinto)) > add remoting based chat sample > ------------------------------ > > Key: JBREM-318 > URL: http://jira.jboss.com/jira/browse/JBREM-318 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Assigned To: Ron Sigal > Priority: Optional > Fix For: 2.4.1.Beta > > > Add a simple chat application using remoting for the communication layer to the remoting samples. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5077) Messaging SeverPeer refactories for better JBossAS integration

by Scott M Stark (JIRA)

Messaging SeverPeer refactories for better JBossAS integration -------------------------------------------------------------- Key: JBAS-5077 URL: http://jira.jboss.com/jira/browse/JBAS-5077 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR1 This task links to the JBMESSAGING-1189 ServerPeer refactorings that we need to have better control of the messaging integration. Subtasks are needed for overriding the security aspects. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4706) Deployer to synchronize meta data after the unguaranteed parsing deployers

by Anil Saldhana (JIRA)

Deployer to synchronize meta data after the unguaranteed parsing deployers -------------------------------------------------------------------------- Key: JBAS-4706 URL: http://jira.jboss.com/jira/browse/JBAS-4706 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta3 As indicated on the forums, the parsing deployers are not guaranteed to run always. So any modifications to the meta data need to be performed in a separate deployer. -- 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, 3 months

3
4
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 February 2008