[jboss-dev-forums] [Design of POJO Server] - Re: Structure deployer changes comitted to trunk

[scott.stark@jboss.org]

"kabir.khan at jboss.com" wrote : For me the MBean gets installed correctly, but the deployment of the nested .aop archive fails when using MainDeployer.deploy()
  | 
  | 
  |   | 2006-10-27 12:40:03,656 ERROR [org.jboss.ejb3.deployers.EJBRegistrationDeployer] Error during deployment: jar:file:/C:/cygwin/home/Kabir/sourcecontrol/jboss-head/testsuite/output/lib/aop-extendertest.sar!/aop-extendertest.aop
  |   | org.jboss.deployers.spi.DeploymentException: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
  |   | 	at org.jboss.ejb3.deployers.EJBRegistrationDeployer.deploy(EJBRegistrationDeployer.java:147)
  |   | 	at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
  |   | 	at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
  |   | 	at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
  |   | 	at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
  |   | 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:795)
  |   | 	at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:570)
  |   | ....
  |   | Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
  |   | 	at java.lang.String.substring(String.java:1768)
  |   | 	at org.jboss.ejb3.deployers.JBoss5DeploymentScope.<init>(JBoss5DeploymentScope.java:57)
  |   | 	at org.jboss.ejb3.deployers.EJBRegistrationDeployer.deploy(EJBRegistrationDeployer.java:131)
  |   | 
  |   | 
  | 
  | EJBRegistrationDeployer.deploy():
  | 
  |   | ...
  |   |          DeploymentScope scope = null;
  |   |          if (unit.getDeploymentContext().getParent() != null)
  |   |          {
  |   |             scope = new JBoss5DeploymentScope(unit.getDeploymentContext().getParent());
  |   |          }
  |   | ...
  |   | 
  | 
  | 
  |   |    public JBoss5DeploymentScope(DeploymentContext parent)
  |   |    {
  |   |       // Use the root vfs path name
  |   |       this.shortName = parent.getRoot().getPathName();
  |   | 
  |   | }
  |   | 
  | 
  | The pathname returned by the JARHandler is an empty string.
That is the opposite of why I changed the JBoss5DeploymentScope. It was using the full string name of the deployment url which is an invalid jmx name. I think we need a short/canonical name accessor on the DeploymentContext which returns the base vfs file name, or '/' if its the vfs root. I'll beef up the name handling error checking regardless.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981362#3981362

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3981362