Re: [jboss-user] [EJB 3.0] - Deployment Error : java.lang.RuntimeException: mapped-name is required
by Tharindu Malimage
Tharindu Malimage [http://community.jboss.org/people/tmalimage] replied to the discussion
"Deployment Error : java.lang.RuntimeException: mapped-name is required"
To view the discussion, visit: http://community.jboss.org/message/558513#558513
--------------------------------------------------------------
I'm using following technologies, servers to develop our application.
jboss-5.1.0.
EJB 3
Hibernate
Vaadin Framework (GWT - Google Web Tool)
Our application is a centralized Bank system. Currently It is running under Glassfish V2 server. Now we want to migrate deployment platform to Jboss-5.1.0. When we deploy our ear following errors have occured.
Note : CustomerFacade is a session bean which handle customers related to our bank application.
<code>
*10:19:46,633 ERROR [Ejb3Deployment] Exception while processing container metadata for EJB: CustomerFacade in unit: CopBank-ejb.jar*
*10:19:46,636 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/prime/jboss-5.1.0/server/default/deploy/CopBank.ear/ state=PreReal mode=Manual requiredState=Real*
*org.jboss.deployers.spi.DeploymentException: Error deploying CopBank-ejb.jar: Exception while processing container metadata for EJB: CustomerFacade in unit: CopBank-ejb.jar*
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:196)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:99)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
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:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
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:619)
Caused by: java.lang.Exception: Exception while processing container metadata for EJB: CustomerFacade in unit: CopBank-ejb.jar
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:549)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:189)
... 34 more
Caused by: java.lang.RuntimeException: mapped-name is required for bank.session.customer.CustomerFacade/customerDetailFacadeRemote of deployment CustomerFacade
at org.jboss.injection.ResourceHandler.loadXmlResourceEnvRefs(ResourceHandler.java:293)
at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:333)
at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:588)
at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:418)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:527)
</code>
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/558513#558513]
Start a new discussion in EJB 3.0 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 10 months
Re: [jboss-user] [jBPM] - def task var in jpdl with jbpm4.4
by dong liu
dong liu [http://community.jboss.org/people/dongliu] replied to the discussion
"def task var in jpdl with jbpm4.4"
To view the discussion, visit: http://community.jboss.org/message/558500#558500
--------------------------------------------------------------
Hi, http://community.jboss.org/people/rebody HuiSheng
I think task variable only be accessed for the task who declare it ,while process variable can accessed fro all.For different task they may be have variables that have same variable name,but the value is different.Of course,I could do some extra work to achieve this,But ,It would be very conveniencent if task could declare it's own variables in jpdl.
I also think elements,such as task,state,should have an id attribute in jpdl def ,name attribute should only for human reading in jpdl photograph.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/558500#558500]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 10 months