April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5427) Bug in local DTD jboss-ds_1_5.dtd due to bad typo correction

by Julien Kronegg (JIRA)

Bug in local DTD jboss-ds_1_5.dtd due to bad typo correction ------------------------------------------------------------ Key: JBAS-5427 URL: http://jira.jboss.com/jira/browse/JBAS-5427 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Environment: Windows 2000, Jboss AS 4.2.2.GA, Eclipse 3.3.2 Reporter: Julien Kronegg Priority: Minor Overview: the DTD file jboss-ds_1_5.dtd has a typo wich was corrected with errors, leading to a bug. Problem statement: In the JBOSS_HOME\docs\dtd\jboss-ds_1_5.dtd, there are two references to the element "url-delimetir", but this element is not declared, leading to an error (Eclipse says: "The element 'url-delimetir' has not been declared."). However, an element named "url-delimeter" is declared (notice the differences between the two orthograps). This seems to come from the correction done in: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/branches/Branch_4_2/co... http://lists.jboss.org/pipermail/jboss-cvs-commits/2007-January/019748.html So the problems are: 1) bad element name leading to an error 2) typo (should be written "url-delimiter" instead of "url-delemiter" Note: there is also a type in the online DTD ("url-delimeter" vs. "url-delimiter"): http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd It seems that the correction has (hopefully) not been made everywhere... Affects: Users who use the local DTD file JBOSS_HOME\docs\dtd\jboss-ds_1_5.dtd are affected. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5232) HAR deployment broken

by Javid Jamae (JIRA)

HAR deployment broken --------------------- Key: JBAS-5232 URL: http://jira.jboss.com/jira/browse/JBAS-5232 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Javid Jamae Assigned To: Dimitris Andreadis I tried deploying a HAR both standalone and inside of an EAR and got an exception: 21:10:08,156 ERROR [AbstractKernelController] Error installing to Start: name=jbia.har:app=Video state=Create mode=Manual requiredState=Installed org.jboss.deployment.DeploymentException: Unable to determine urls from classloader [BaseClassLoader@1e6661{vfsfile:/C:/jboss-5.0.0.Beta4/server/deployment/deploy/video.har}] at org.jboss.hibernate.jmx.Hibernate.scanForMappings(Hibernate.java:272) ... See forum reference for full stack trace. -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-5423) AnnotationMetaDataDeployer defaults "metadata-complete" to true, should be false

by Andrew Lee Rubinger (JIRA)

AnnotationMetaDataDeployer defaults "metadata-complete" to true, should be false -------------------------------------------------------------------------------- Key: JBAS-5423 URL: http://jira.jboss.com/jira/browse/JBAS-5423 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR1 EJB3 Core Specification, Deployment Descriptor XML Schema: "If metadata-complete is not specified or is set to 'false', the deployment tool must examine the class files of the application for annotations, as specified by the specifications." The same exists in the JEE Specification. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1274) Interceptors tests get confused about classloading

by Kabir Khan (JIRA)

Interceptors tests get confused about classloading -------------------------------------------------- Key: EJBTHREE-1274 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1274 Project: EJB 3.0 Issue Type: Bug Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: AS 5.0.0.CR1 BasicTestSuite's constructor sets the classloaders and deploys its aop information to the aspectmanager. Unfortunately this constructor is called whenever we call other tests as well, so everything gets confused. Refactor this test so that the classloaders are set and the information is deployed only when this test is actually invoked. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-716) TCP based configs need UNICAST for correct ordering

by Bela Ban (JIRA)

TCP based configs need UNICAST for correct ordering --------------------------------------------------- Key: JGRP-716 URL: http://jira.jboss.com/jira/browse/JGRP-716 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.3, 2.7 In a TCP based config *without* UNICAST, messages can get delivered out of order if a thread pool is enabled at the transport level. Example: - Sender A sends unicast messages (same for multicast messages) M1, M2 and M3 to B - B's transport dispatches the 3 messages to a thread pool (if bundling is enabled, then this issue might not occur as all 3 messages might have gotten bundled, and will then get delivered as a bundle, by the same thread) - M1 is processed by thread-1, M2 by thread-2 and M3 by thread-3 ==> There are no guarantees with respect to ordering now, as thread pool destroyed ordering and there is no UNICAST to make sure messages arriving in different threads get ordered accoring to sequence number TODO: ship all TCP based protocols with UNICAST WORKAROUND: disable the thread pool(s) in the TCP transport -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Assigned: (HIBERNATE-78) Explanation for customers why Enterprise Hibernate does not support JDK 1.4

by Gail Badner (JIRA)

[ http://jira.jboss.com/jira/browse/HIBERNATE-78?page=all ] Gail Badner reassigned HIBERNATE-78: ------------------------------------ Assignee: Gail Badner (was: Aaron Darcy) > Explanation for customers why Enterprise Hibernate does not support JDK 1.4 > --------------------------------------------------------------------------- > > Key: HIBERNATE-78 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-78 > Project: Hibernate > Issue Type: Task > Reporter: Gail Badner > Assigned To: Gail Badner > > GSS needs to have an explanation to provide to customers about why JDK 1.4 is not supported for Enterprise Standalone 3.2.4.sp1.cp03. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (HIBERNATE-85) Build Enterprise Hibernate with JDK 1.5 using dependencies shipped with EAP

by Gail Badner (JIRA)

[ http://jira.jboss.com/jira/browse/HIBERNATE-85?page=all ] Gail Badner reassigned HIBERNATE-85: ------------------------------------ Assignee: Gail Badner (was: Aaron Darcy) > Build Enterprise Hibernate with JDK 1.5 using dependencies shipped with EAP > --------------------------------------------------------------------------- > > Key: HIBERNATE-85 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-85 > Project: Hibernate > Issue Type: Task > Reporter: Gail Badner > Assigned To: Gail Badner > > In EAP 4.2 CP01 and CP02, JDK 1.4 was used with old versions of JBoss Cache (1.3) and other JBoss dependencies (4.0.3) to build hibernate. Hibernate really should be built using dependencies shipped with EAP 4.2 CP03. > JDK 1.5 will be required to build Hibernate because the versions of JBoss Cache and its dependencies to be shipped with EAP 4.2 CP03 require JDK 1.5. > Please note that this is a change in JDK version and dependencies for building hbernate for EAP 4.2 CP03. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1987) Integrate content framework rendering to use public navigational state

by Julien Viet (JIRA)

Integrate content framework rendering to use public navigational state ---------------------------------------------------------------------- Key: JBPORTAL-1987 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1987 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Reporter: Julien Viet Assigned To: Julien Viet Fix For: 2.7 Final Documentation needs to be updated accordingly. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-6) Enhance jboss.xml and Metadata to support Pluggable JNDI via XML

by Andrew Lee Rubinger (JIRA)

Enhance jboss.xml and Metadata to support Pluggable JNDI via XML ---------------------------------------------------------------- Key: JBMETA-6 URL: http://jira.jboss.com/jira/browse/JBMETA-6 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: 1.0.0.Beta7 EJBTHREE-1101 defines a Pluggable JNDI Strategy; XML support is required. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-5425) Upgrade to jboss-test 1.1.0.GA (from 1.0.5.GA)

by Dimitris Andreadis (JIRA)

Upgrade to jboss-test 1.1.0.GA (from 1.0.5.GA) ---------------------------------------------- Key: JBAS-5425 URL: http://jira.jboss.com/jira/browse/JBAS-5425 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.CR1 Switch to the latest org.jboss.test:jboss-test:1.1.0.GA In this version the ServerManager functionality is broken out to: org.jboss.jbossas:jboss-server-manager:0.1.0.GA -- 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, 1 month

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 April 2008