[JBossWS] - JAX-RPC Enumeration type did not conform to expectations
by lds23
Hi,
When trying to deploy a webservice on JBoss 4.0.4 I get an exception and the only reference I cannot find any hints on the web. Any hints? The service was implemented by running wsimport on wsdl file (Parlay X Send SMS function). The implementation is a stateless session bean. I'll be really grateful for any tips:
org.jboss.ws.WSException: JAX-RPC Enumeration type did not conform to expectations
at org.jboss.ws.tools.schema.SchemaTypeCreator.handleJAXRPCEnumeration(SchemaTypeCreator.java:377)
at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:317)
at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:272)
at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:133)
at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:128)
at org.jboss.ws.tools.schema.SchemaTypeCreator.createFieldParticle(SchemaTypeCreator.java:597)
at org.jboss.ws.tools.schema.SchemaTypeCreator.introspectJavaProperties(SchemaTypeCreator.java:582)
at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:334)
at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:272)
at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:133)
at org.jboss.ws.tools.JavaToXSD.generateForSingleType(JavaToXSD.java:109)
at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType(JavaToWSDLHelper.java:555)
at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesForXSD(JavaToWSDLHelper.java:141)
at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration(JavaToWSDL11.java:236)
at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:168)
at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:318)
at org.jboss.ws.metadata.AnnotationsMetaDataBuilder.processOrGenerateWSDL(AnnotationsMetaDataBuilder.java:225)
at org.jboss.ws.metadata.AnnotationsMetaDataBuilder.setupEndpointFromAnnotations(AnnotationsMetaDataBuilder.java:174)
at org.jboss.ws.metadata.AnnotationsMetaDataBuilderJSE.buildMetaData(AnnotationsMetaDataBuilderJSE.java:82)
at org.jboss.ws.server.WebServiceDeployerJSE.createWebServicesMetaData(WebServiceDeployerJSE.java:196)
at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:103)
at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:66)
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.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy40.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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.invoke(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.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(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)
Regards,
DS
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982680#3982680
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982680
19 years, 5 months
[JBossWS] - Re: implementing wsse:UserNameToken
by sappenin
anonymous wrote : 7. how should I capture or examine the SOAP header in order to
| look for wsse usernametoken element? Is there any log file or option to
| log the SOAP header?
In your log4j.xml file (JBOSS_HOME/server/[servername]/conf/log4j.xml), set the CONSOLE appender threshold to DEBUG (instead of the default INFO). When you run your webservice, the in/out messages (including headers) will be displayed. You can do the same for other appenders if you want to capture logging info in other places.
|
| <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Target" value="System.out"/>
| <param name="Threshold" value="INFO"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <!-- The default pattern: Date Priority [Category] Message\n -->
| <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
| </layout>
| </appender>
|
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982651#3982651
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982651
19 years, 5 months