December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBTM-80) consistent naming for jars

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-80?page=comments#action_12348550 ] Dimitris Andreadis commented on JBTM-80: ---------------------------------------- If you look at the majority of other jboss library the names would be: jboss-ts-jta.jar jboss-ts-jta-integration.jar jboss-ts-jts.jar jboss-ts-jts-integration.jar jboss-ts-jts-jacorb.jar jboss-ts-common > consistent naming for jars > -------------------------- > > Key: JBTM-80 > URL: http://jira.jboss.com/jira/browse/JBTM-80 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2 > Reporter: Mark Little > Assigned To: Kevin Conner > Priority: Minor > Fix For: 4.4 > > > It's either jbossjts as the base name for jars, or jbossts, but not both. So we need to either change jbossts-common.jar or the others. -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-806) Installer version of EJB3 incompatible with 4.0.5

by William DeCoste (JIRA)

Installer version of EJB3 incompatible with 4.0.5 ------------------------------------------------- Key: EJBTHREE-806 URL: http://jira.jboss.com/jira/browse/EJBTHREE-806 Project: EJB 3.0 Issue Type: Bug Reporter: William DeCoste Assigned To: William DeCoste Need installer to use EJB3 Hot redeploy fails on invocation of redeployed bean -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-797) JBoss Cache entity replication should have region based marshalling enabled

by Brian Stansberry (JIRA)

JBoss Cache entity replication should have region based marshalling enabled --------------------------------------------------------------------------- Key: EJBTHREE-797 URL: http://jira.jboss.com/jira/browse/EJBTHREE-797 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC10 - FD Replicating classes loaded from a scoped classloader requires use of the JBoss Cache region-based marshalling API. Therefore, region based marshalling needs to be enable in the entity cache configuration file. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-798) Implement temporary EJBTHREE-795 workaround in EJB3 codebase

by Brian Stansberry (JIRA)

Implement temporary EJBTHREE-795 workaround in EJB3 codebase ------------------------------------------------------------ Key: EJBTHREE-798 URL: http://jira.jboss.com/jira/browse/EJBTHREE-798 Project: EJB 3.0 Issue Type: Sub-task Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC10 - FD Likely long term fix is to update the org.hibernate.cache.TreeCache class. But, as a temporary workaround for the Stacks 1.1 release, I have implemented a new version of org.hibernate.cache.TreeCache in the EJB3 namespace, and updated TreeCacheProviderHook to use it. Updated version (o.j.ejb3.entity.JBCCache): Makes use of JBC's marshalling API to register a deployment's classloader with JBC and activate the relevant region when it is constructed. When the destroy() method is called, the region is inactivated and the classloader unregistered. Exception to this are the special regions named "org.hibernate.cache.StandardQueryCache" and "org.hibernate.cache.UpdateTimestampsCache", which 1) should not have a particular classloader registered with them, as they may be used by multiple deployments. 2) should not be inactivated when a particular JBCCache instance is destroyed, as other deployments may be using them. UpdateTimestampsCache does not actually replicate any custom classes, so the special handling for it in JBCCache is just to make sure JBCCache doesn't break anything. StandardQueryCache does have the potential to replicate classes, but since no classloader can be registered with it's cache region, such a replication attempt will fail. As a workaround, if the region's name is "org.hibernate.cache.StandardQueryCache", JBCCache will not replicate any queries placed in the region, but rather will only cache them locally. -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-796) Add tests of entity replication with scoped classloader

by Brian Stansberry (JIRA)

Add tests of entity replication with scoped classloader ------------------------------------------------------- Key: EJBTHREE-796 URL: http://jira.jboss.com/jira/browse/EJBTHREE-796 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC10 - FD -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1160) Javascript error in dashboard in FF

by Roy Russo (JIRA)

Javascript error in dashboard in FF ----------------------------------- Key: JBPORTAL-1160 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1160 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Priority: Critical Fix For: 2.6.Alpha1 "this.instancesForm has no properties" -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-576) Clean up pom.xml files (dependencyManagement, lock down plugin versions, ...)

by Geoffrey De Smet (JIRA)

Clean up pom.xml files (dependencyManagement, lock down plugin versions, ...) ----------------------------------------------------------------------------- Key: JBRULES-576 URL: http://jira.jboss.com/jira/browse/JBRULES-576 Project: JBoss Rules Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 3.1-m1 Reporter: Geoffrey De Smet Assigned To: Mark Proctor This patch does a bunch of improvements on the pom.xml files, including some best practices. I 've maven2ized several projects, including spring-rich-c.sf.net and networktools.sf.net. - Clean up order of elements - Lock down plugin versions (so the build is repreducable and behaves the same between all team members): probably the most important issue - jira location - use of dependencyManagement to declare the versions of dependencies and inherit that to all modules, which declare which dependencies they need - organization is now JBoss Inc. - lock down compiler source/target to 1.4 (you wouldn't want to publish a class version 49 (=1.5) jar to the central maven repo if you're using JDK 1.5 locally) - schema definitions for code-completion in the IDE while editing the pom.xml - servletapi:servletapi:2.3 dependency changed to javax.servlet:servlet-api:2.3 - and more :) It was just to much to try to make separate patches/jira's of it. Feel free to adjust it as you see fit. I had to test this patch with -Dmaven.test.skip=true because there was a failing testcase on the trunk: Running org.drools.base.ShadowProxyFactoryTest Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.125 sec <<< FAILURE! Note: drools (and it's submodules core, compiler, jsr94, decisiontables), drools-server, drools-repository and drools-jbrms build succesfully like this: mvn -Dmaven.test.skip=true clean install cd drools-server mvn -Dmaven.test.skip=true clean install cd ../drools-repository mvn -Dmaven.test.skip=true clean install cd ../drools-jbrms mvn -Dmaven.test.skip=true clean install So you should be able to just uncomment them in <modules> in the root pom.xml :) -- 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

17 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-261) Email helper util class and settings in PM need sync and cleanup

by Daniel Brum (JIRA)

Email helper util class and settings in PM need sync and cleanup ---------------------------------------------------------------- Key: JBESB-261 URL: http://jira.jboss.com/jira/browse/JBESB-261 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 RC1 Reporter: Daniel Brum Assigned To: Mark Little Fix For: 4.0 - Need to cleanup this util class and the properties read in from the main jbossesb-properties.xml. - need to add support for TLS authentication and any other switch/flag as required by ISP's to send smtp messages - need to ensure support for as many combinations of logging into smtp servers -- 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

17 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JGRP-380) MERGE3 can be left in an inconsistent state

by Vincent Hartsteen (JIRA)

MERGE3 can be left in an inconsistent state ------------------------------------------- Key: JGRP-380 URL: http://jira.jboss.com/jira/browse/JGRP-380 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Vincent Hartsteen Assigned To: Bela Ban Fix For: 2.4.1 MERGE3 can be left in an inconsistent state when it initiates a VIEW_CHANGE in case more than 1 coordinator is found on the network but when that VIEW_CHANGE is cancelled lateron in the stack. This leaves the node thinking it is a coordinator (is_coord remains true) but its announcements is not preloaded with its own address. The suggested fix is to add the local address of the node to the list of announcements right after the announcements list is cleared. void processAnnouncements() { if(announcements.size() > 1) { Vector coords=new Vector(announcements); // create a clone if(coords.size() > 1) { if(log.isDebugEnabled()) log.debug("passing up MERGE event, coords=" + coords); final Event evt=new Event(Event.MERGE, coords); if(use_separate_thread) { Thread merge_notifier=new Thread(Util.getGlobalThreadGroup(), "merge notifier thread") { public void run() { passUp(evt); } }; merge_notifier.setDaemon(true); merge_notifier.start(); } else { passUp(evt); } } announcements.clear(); announcements.add(local_addr); // ***** POSSIBLE FIX ***** } } -- 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

17 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-383) Port of JGRP-380 to 2.5

by Bela Ban (JIRA)

Port of JGRP-380 to 2.5 ----------------------- Key: JGRP-383 URL: http://jira.jboss.com/jira/browse/JGRP-383 Project: JGroups Issue Type: Task Affects Versions: 2.4.1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 -- 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

17 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006