April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBXB-101) Cannot disable validation

by Scott M Stark (JIRA)

Cannot disable validation ------------------------- Key: JBXB-101 URL: http://jira.jboss.com/jira/browse/JBXB-101 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.0.CR2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossXB-2.0.0.CR3 Calling Unmarshaller.setValidation(false) has no affect on the parser validation. The following org.jboss.test.xml.SimpleTestCase test fails: public void testUnmarshalBooks2Dtd() throws Exception { // create an object model factory String xmlSource = "books2-dtd.xml"; ObjectModelFactory factory = new BookObjectFactory(); log.debug("<test-unmarshal-" + xmlSource + '>'); // get the XML stream URL xmlUrl = getResourceUrl("xml/book/" + xmlSource); // create unmarshaller Unmarshaller unmarshaller = getBookUnmarshaller(); unmarshaller.setValidation(false); // let the object model factory to create an instance of Book and populate it with data from XML Book book = (Book)unmarshaller.unmarshal(xmlUrl.openStream(), factory, null); checkUnmarshalledBook(book); log.debug("</test-unmarshal-" + xmlSource + '>'); } wth: org.jboss.xb.binding.JBossXBException: Failed to parse source: The content of element type "book" is incomplete, it must match "(title,author,character+,misc+)". @ *unknown*[18,8] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:187) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:169) at org.jboss.test.xml.SimpleTestCase.testUnmarshalBooks2Dtd(SimpleTestCase.java:94) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;J)Ljava.lang.Object;(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: org.xml.sax.SAXException: The content of element type "book" is incomplete, it must match "(title,author,character+,misc+)". @ *unknown*[18,8] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:406) at org.apache.xerces.util.ErrorHandlerWrapper.error(Ljava.lang.String;Ljava.lang.String;Lorg.apache.xerces.xni.parser.XMLParseException;)V(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Lorg.apache.xerces.xni.XMLLocator;Ljava.lang.String;Ljava.lang.String;[Ljava.lang.Object;S)V(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Ljava.lang.String;Ljava.lang.String;[Ljava.lang.Object;S)V(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Lorg.apache.xerces.xni.QName;Lorg.apache.xerces.xni.Augmentations;Z)V(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Lorg.apache.xerces.xni.QName;Lorg.apache.xerces.xni.Augmentations;)V(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement()I(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Z)Z(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Z)Z(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Z)Z(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Lorg.apache.xerces.xni.parser.XMLInputSource;)V(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Lorg.apache.xerces.xni.parser.XMLInputSource;)V(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Lorg.xml.sax.InputSource;)V(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Lorg.xml.sax.InputSource;)V(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:183) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:169) at org.jboss.test.xml.SimpleTestCase.testUnmarshalBooks2Dtd(SimpleTestCase.java:94) because there are no misc elements in the document. The point of the test is to be able to relax validation against the dtd as is required for application.xml deployments that only include sars. This is separate from the schema validation of JBMICROCONT-169 but related. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4300) StackOverflowError in JBossNS during lookup

by Martin Kirst (JIRA)

StackOverflowError in JBossNS during lookup ------------------------------------------- Key: JBAS-4300 URL: http://jira.jboss.com/jira/browse/JBAS-4300 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.0.5.GA Environment: [ServerInfo] Java version: 1.6.0_01,Sun Microsystems Inc. [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_01-b06,Sun Microsystems Inc. [ServerInfo] OS-System: Windows XP 5.1,x86 Reporter: Martin Kirst Assigned To: Scott M Stark Using "jboss-portal-2.4.2-bundled.zip" and deploying my own JSR168-PortletAppl. For this PortletAppl. I need a jdbc DataSource. So I added the following two files. Any ideas because of the problem? === PW2-Portal-App-ds.xml ===================================================== <datasources> <local-tx-datasource> <jndi-name>PortowebPool</jndi-name> <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}portoweb${/}portoweb</connection-url> <driver-class>org.hsqldb.jdbcDriver</driver-class> <user-name>sa</user-name> <password><![CDATA[]]></password> </local-tx-datasource> </datasources> ----------------------------- I've pre instanziated the portoweb hsqldb files with the hsqldbManager tool. (build schemas and so on). === warfile:WEB-INF/jboss-web.xml ========================== <?xml version="1.0" encoding="UTF-8" ?> <jboss-web> <resource-ref> <res-ref-name>jdbc/PortowebPool</res-ref-name> <jndi-name>java:comp/env/jdbc/PortowebPool</jndi-name> </resource-ref> </jboss-web> === But I got this StackOverFlow, when I start the server ================================== 2007-03-31 23:48:10,031 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/PW2-Portal-App]] Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/PortowebApp.xml]: Invocation of init method failed; nested exception is java.lang.StackOverflowError Caused by: java.lang.StackOverflowError at java.security.AccessController.doPrivileged(Native Method) at com.sun.naming.internal.VersionHelper12.getJndiProperties(VersionHelper12.java:89) at com.sun.naming.internal.ResourceManager.getInitialEnvironment(ResourceManager.java:138) at javax.naming.InitialContext.init(InitialContext.java:219) at javax.naming.InitialContext.<init>(InitialContext.java:197) at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1061) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:700) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:716) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1061) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:700) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:716) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1061) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:700) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:716) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1061) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:700) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:716) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:392) ... and so on and so on 2007-03-31 23:48:10,562 ERROR [org.apache.catalina.core.StandardContext] Error listenerStart 2007-03-31 23:48:10,562 ERROR [org.apache.catalina.core.StandardContext] Context [/PW2-Portal-App] startup failed due to previous errors 2007-03-31 23:48:10,562 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/PW2-Portal-App]] Closing Spring root WebApplicationContext -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Commented: (JGRP-47) Support for IPv6

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-47?page=comments#action_12358451 ] Brian Stansberry commented on JGRP-47: -------------------------------------- Lot's more info on this can be found at http://wiki.jboss.org/wiki/Wiki.jsp?page=IPv6 . > Support for IPv6 > ---------------- > > Key: JGRP-47 > URL: http://jira.jboss.com/jira/browse/JGRP-47 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.3 > > > Requires changes to IpAddress, maybe Ipv6Address (subclass of IpAddress) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-825) add EJB3 JMX metrics to EJB3

by William DeCoste (JIRA)

add EJB3 JMX metrics to EJB3 ---------------------------- Key: EJBTHREE-825 URL: http://jira.jboss.com/jira/browse/EJBTHREE-825 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste Stateless: AvailableCount, MaxSize, CurrentSize, etc Stateful: CacheSize, PassivatedCount, CreateCount, etc -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-4299) Running version-release target on build/build-release.xml needs dom4j.jar in ${jboss.dist}/lib

by Vivek Lakshmanan (JIRA)

Running version-release target on build/build-release.xml needs dom4j.jar in ${jboss.dist}/lib ---------------------------------------------------------------------------------------------- Key: JBAS-4299 URL: http://jira.jboss.com/jira/browse/JBAS-4299 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: JBossAS-4.2.0.CR1 Environment: Linux (Fedora Core 6 x86) + BEA 1.5 x86 JVM Reporter: Vivek Lakshmanan Assigned To: Rajesh Rajasekaran Priority: Minor Fix For: JBossAS-4.2.0.GA version-release target in build-release.xml (to produce distribution zips) has the following: <javac destdir="."> <src path="${jboss.build.dir}"/> <classpath> <pathelement location="${jboss.dist}/lib/dom4j.jar"/> </classpath> <include name="VersionRelease.java"/> </javac> However ${jboss.dist}/lib does not contain dom4j.jar. We should not add dom4j.jar to the lib directory unnecessarily for this. A suggestion by Ryan Campbell: replace ${jboss.dist}/lib with ${jboss.dist}/server/all/lib -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Commented: (JBAS-2026) Wrong placeholder ear created

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2026?page=comments#action_12358409 ] Dimitris Andreadis commented on JBAS-2026: ------------------------------------------ This change break org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase that assumes the opposite behaviour, so this test was excluded from the testsuite. > Wrong placeholder ear created > ----------------------------- > > Key: JBAS-2026 > URL: http://jira.jboss.com/jira/browse/JBAS-2026 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3RC1 > Environment: jxm, twiddle > Reporter: Fabiano C. de Oliveira > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2 > > Attachments: management.patch > > > When a WarModule is created a placeholder ear is Always created. When a module that have a child WarModule but is NOT a ear module a ear placeholder is created but this ear in truth dont exist. > Just take a look in the ServiceModule jbossweb-tomcat55.sar. The JMX-Console show it like a ServiceModule and a like a J2EEApplication. > This patch just take a look if the parent module is a EAR, otherwise WebModule use the J2EEServer as the parent. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1305) JSR77: ServiceModule should have a parent module to define the scope

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1305?page=all ] Dimitris Andreadis updated JBAS-1305: ------------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034690 > JSR77: ServiceModule should have a parent module to define the scope > -------------------------------------------------------------------- > > Key: JBAS-1305 > URL: http://jira.jboss.com/jira/browse/JBAS-1305 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-4.0.1 Final > Environment: Java version: 1.5.0,Sun Microsystems Inc. > Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Sun Microsystems Inc. > OS-System: Linux 2.4.21-4.EL,i386 > Reporter: Michael Kopp > Fix For: JBossAS-4.2.1.CR1 > > > If one has two -service.xml files with the same filename in different locations in the ear, there will only ever be one respective ServiceModule in the J2EE Management. > The reason for this is that there is no scope defined in the name, hence the filename has to be server-wide unique. > A ServiceModule should have a parent module like the EjbModule, which should make it possible to: > - have the same file name multiple times > - on the Server > - in one Application > - link the ServiceModule to the Application it belongs to. > Forum Topic: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862704#3862704 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4298) jsr77 EJBModule not deregistered correctly from J2EEServer

by Dimitris Andreadis (JIRA)

jsr77 EJBModule not deregistered correctly from J2EEServer ---------------------------------------------------------- Key: JBAS-4298 URL: http://jira.jboss.com/jira/browse/JBAS-4298 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Affects Versions: JBossAS-4.2.0.CR1, JBossAS-4.0.5.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.1.CR1 The deployedObjects[] attribute of jboss.management.local:name=Local, j2eeType=J2EEServer contains the objectname of an undeployed EJBModule, e.g: jboss.management.local:J2EEApplication=j2eeapplication_ejb_vehicle.ear,J2EEServer=Local,j2eeType=EJBModule,name=j2eeapplication_ejb_vehicle_ejb.jar You can verify the inconcistensy using 'twiddle jsr77' that traverses the jsr77 tree: X:\cvs\jboss-public\jboss-4.2\build\output\jboss-4.2.0.GA\bin>twiddle jsr77 J2EEDomain=jboss.management.local J2EEServer=Local serverVendor=JBoss (http://www.jboss.org/) serverVersion=4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200703301703) ServiceModule=ejb3.deployer MBean=jboss.remoting%3atype%3dConnector%2cname%3dDefaultEjb3Connector%2cha ndler%3dejb3 stateMonitored=false StateString=j2ee.object.deleted MBean=jboss.ejb3%3aservice%3dJarsIgnoredForScanning stateMonitored=true StateString=j2ee.object.deleted MBean=jboss.ejb3%3aservice%3dEJB3Deployer stateMonitored=true StateString=j2ee.state.running ... MBean=jboss.deployment%3atype%3dDeploymentScanner%2cflavor%3dURL stateMonitored=true StateString=j2ee.state.running EJBModule=j2eeapplication_ejb_vehicle_ejb.jar 20:57:20,975 ERROR [Twiddle] Exec failed javax.management.InstanceNotFoundException: jboss.management.local:J2EEApplicati on=j2eeapplication_ejb_vehicle.ear,J2EEServer=Local,j2eeType=EJBModule,name=j2ee application_ejb_vehicle_ejb.jar is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistr y.java:523) at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java :550) at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerA ... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4262) Port JBAS-4229 fix to Branch_4_0

by Brian Stansberry (JIRA)

Port JBAS-4229 fix to Branch_4_0 -------------------------------- Key: JBAS-4262 URL: http://jira.jboss.com/jira/browse/JBAS-4262 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.0.5.SP1 Port the fix, but the default value for HASingletonController.restartOnMerge needs to be 'false', since this will go into an SP or micro 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

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-172) Add support for explicit aliases to the BeanMetaData/XML

by Adrian Brock (JIRA)

Add support for explicit aliases to the BeanMetaData/XML -------------------------------------------------------- Key: JBMICROCONT-172 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-172 Project: JBoss MicroContainer Issue Type: Sub-task Reporter: Adrian Brock Fix For: JBossMC_2_0_0_CR1 Now that the AbstractController supports aliases this should be available in the BeanMetaData and xml, e.g. <bean name="Name1"> <alias>Alias1</alias> <alias>Alias2</alias> This should just be a case of "stealing" the aliases from the BeanMetaData when creating the KernelControllerContext. -- 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, 3 months

2
3
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 2007