 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | Could not create deployment | Could not create deployment 2007-06-13 - By hartsock
Back
I've been working along for several months on an EJB3 project in an archive I
called tie.jar when I went to refactored a few class names. Now I suddenly get
this error:
| 13:43:19,144 INFO [Ejb3Deployment] EJB3 deployment time took: 102
| 13:43:19,231 ERROR [MainDeployer] Could not create deployment: file:/usr
/local/jboss-4 (See http://oss-4.ora-code.com).2.0.GA/server/ejb3-jbpm/deploy/tie.jar
| java.lang.NullPointerException 
| at org.jboss.ws.tools.schema.SchemaTypeCreator
.introspectJavaProperties(SchemaTypeCreator.java:578)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType
(SchemaTypeCreator.java:332)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.getType
(SchemaTypeCreator.java:273)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType
(SchemaTypeCreator.java:132)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType
(SchemaTypeCreator.java:127)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.createFieldParticle
(SchemaTypeCreator.java:607)
| at org.jboss.ws.tools.schema.SchemaTypeCreator
.introspectJavaProperties(SchemaTypeCreator.java:592)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType
(SchemaTypeCreator.java:332)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.getType
(SchemaTypeCreator.java:273)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType
(SchemaTypeCreator.java:132)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType
(SchemaTypeCreator.java:127)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.handleArray
(SchemaTypeCreator.java:525)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType
(SchemaTypeCreator.java:299)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.getType
(SchemaTypeCreator.java:273)
| at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType
(SchemaTypeCreator.java:132)
| at org.jboss.ws.tools.JavaToXSD.generateForSingleType(JavaToXSD
.java:109)
| at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType
(JavaToWSDLHelper.java:556)
| at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesForXSD
(JavaToWSDLHelper.java:141)
| at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration
(JavaToWSDL11.java:245)
| at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:168)
| at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:318)
| at org.jboss.ws.deployment.JSR181MetaDataBuilder
.processOrGenerateWSDL(JSR181MetaDataBuilder.java:289)
| at org.jboss.ws.deployment.JSR181MetaDataBuilder
.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:231)
| at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData
(JSR181MetaDataBuilderEJB3.java:75)
| at org.jboss.ws.deployment.ServiceEndpointDeployer.create
(ServiceEndpointDeployer.java:106)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.create
(DeployerInterceptor.java:80)
| at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create
(DeployerInterceptorEJB.java:44)
| at org.jboss.deployment.SubDeployerInterceptorSupport
$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
| at org.jboss.deployment.SubDeployerInterceptor.invoke
(SubDeployerInterceptor.java:91)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl (MBeanServerImpl.java
:659)
| at org.jboss.mx.util.MBeanProxyExt (MBeanProxyExt.java:210)
| at $Proxy29.create(Unknown Source)
| at org.jboss.deployment.MainDeployer (MainDeployer.java:969)
| at org.jboss.deployment.MainDeployer (MainDeployer.java:818)
| at org.jboss.deployment.MainDeployer (MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method (Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor
(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke
(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke
(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl (MBeanServerImpl.java
:659)
| at org.jboss.mx.util.MBeanProxyExt (MBeanProxyExt.java:210)
| at $Proxy8.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner
(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner
(URLDeploymentScanner.java:610)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner
$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner
$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner
$ScannerThread.run(AbstractDeploymentScanner.java:225)
|
How do I even go about diagnosing this error?
The tie.jar file deployed fine before the name changes and now even if I change
the names back the deploy fails. If I use an old copy of the tie.jar in a JBoss
server that the new deploy failed on the new jar fails until I stop the server,
clear the working files, and restart it.
My other EJB3 jar files are unaffected by the problem leading me to believe
that this is a problem in my code not in the server configuration.
I can't find where my code is causing the SchemaTypeCreator to fail out because
there is no trace message about my class file structure at all. None of the
classes from the tie.jar ... named tie.ClassName show up... how should I know
which classes of mine are causing this issue? I suspect it is a change I made
in the classes I refactored but I can't change the names back and get a working
copy.
Any ideas? Where do I even start?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic
&p=4054085#4054085
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode
=reply&p=4054085
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
jboss-user mailing list
jboss-user@(protected)
https://lists.jboss.org/mailman/listinfo/jboss-user
|
|
|
