1 Reply Latest reply: May 4, 2012 10:01 AM by Wolf-Dieter Fink RSS

Migration of Existing EJB 2 Entity Bean from Jboss AS 3.2.6 to Jboss AS 5

Viral Gohel Newbie

Hello,

 

I am trying to migrate my existing EJB 2 Entity beans that are currently deployed in Jboss AS 3.2.6 to Jboss AS 5. While deploying my application, i am getting the following exception stack in the server console of jboss as 5 :

 

org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/VirtualMachines/Jboss_Servers/jboss-eap-5.1/jboss-as/server/default/deploy/EJB_2_Entity_5.jar/ejbModule/

          at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)

          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)

          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)

          at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:95)

          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)

          at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)

          at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)

          at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

          at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

          at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

          at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)

          at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)

          at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)

          at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

          at org.jboss.Main.boot(Main.java:221)

          at org.jboss.Main$1.run(Main.java:556)

          at java.lang.Thread.run(Thread.java:679)

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: method-name not found as a child of method-attributes in unordered_sequence: method*

          at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)

          at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)

          at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)

          at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)

          at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)

          at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)

          at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304)

          at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:286)

          at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203)

          at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348)

          ... 35 more

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: method-name not found as a child of method-attributes in unordered_sequence: method*

          at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:383)

          at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)

          at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)

          at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)

          at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)

          at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)

          at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)

          at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

          at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

          at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

          at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

          at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

          at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

          at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

          ... 44 more

 

 

My Application uses the jboss.xml file.

 

The generated jboss.xml refers to the DTD "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd". For backward compatibility, JBoss 5.x provides "jboss_3_0.dtd" in "$JBOSS_EAP_DIST/docs/dtd/" so that application deployed on older versioned JBoss can be deployed in latest version. Now, in my application's jboss.xml, for an <entity>, a tag name <method-attributes> is used which possible elements(sub-tags) can be <method-name> and <read-only> according to "jboss_3_0.dtd". Now, if deploy my application with jboss.xml having following tags in xml, i am getting the above stack trace.

 

Is is that my jboss.xml cannot refer to http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd, or </method-attributes> is wrongly defined in jboss.xml?

 

This seems to work perfectly fine in my jboss 3.2.6, but throws the above exceptions as soon as i deploy the same in jboss 5. I have attached my jboss.xml file for reference alongwith the jboss_3_0.dtd.

 

Does anybody have any ideas as to why is this strange bahaviour when migrating to jboss as 5 ??

 

Regards,

Viral

  • 1. Re: Migration of Existing EJB 2 Entity Bean from Jboss AS 3.2.6 to Jboss AS 5
    Wolf-Dieter Fink Master

    I'm not sure, the version is really old.

     

    But I suppose that the AS5 (I hope you use 5.1) might not handle the old xml correct.

     

    Do you use a proper XML editor with highligting and dtd check? If not try jedit (with plugins) for example.

    I would check wether your jboss.xml is valid against the 3_0.dtd, if yes and still not working you should validate and fix against the latest dtd version of your current server version.

     

    And I expect other migration issues because there are some changes between such versions. Feel free to ask specifc