[JBossWS] - JBoss JAXRPC SOAP client type mapping problem
by bypaik
hi, i've been stuck on this issue for a few days and have no idea what's causing the following stack track:
org.jboss.ws.WSException: Cannot obtain java type mapping for: {urn:grainger-com:xi:addrval_webservice:types}>AddrRequest
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.processDocElement(JAXRPCMetaDataBuilder.java:627)
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildParameterMetaDataDoc(JAXRPCMetaDataBuilder.java:886)
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.setupOperationsFromWSDL(JAXRPCMetaDataBuilder.java:214)
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaDataInternal(JAXRPCClientMetaDataBuilder.java:216)
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:133)
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:85)
at org.jboss.ws.core.jaxrpc.client.ServiceImpl.(ServiceImpl.java:111)
at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128)
i'm using JBoss 4.0.5 on jdk 1.4 (i have no choice but to use jdk 1.4 and thus can't use the newer ws api). my wsdl looks like the following:
<?xml version="1.0"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:p1="urn:me-com:xi:addrval_webservice"
xmlns:p2="urn:me-com:xi:addrval_webservice:types"
targetNamespace="urn:me-com:xi:addrval_webservice"
name="MI_Request_To_Grp1">
<wsdl:types>
<xsd:schema targetNamespace="urn:me-com:xi:addrval_webservice:types">
<xsd:element name="AddrRequest">
<xsd:complexType name="Request">
<xsd:all>
<xsd:element name="InputKeyValue" type="xsd:string" />
<xsd:element name="FirmName" type="xsd:string" />
<xsd:element name="AddressLine1" type="xsd:string" />
<xsd:element name="City" type="xsd:string" />
...
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="AddrResponse">
<xsd:complexType name="Response">
<xsd:all>
<xsd:element name="Status" type="xsd:string" />
<xsd:element name="StatusCode" type="xsd:string" />
<xsd:element name="StatusDescription" type="xsd:string" />
<xsd:element name="InputKeyValue" type="xsd:string" />
<xsd:element name="FirmName" type="xsd:string" />
<xsd:element name="AddressLine1" type="xsd:string" />
<xsd:element name="AddressLine2" type="xsd:string" />
<xsd:element name="AddressLine3" type="xsd:string" />
<xsd:element name="AddressLine4" type="xsd:string" />
<xsd:element name="City" type="xsd:string" />
<xsd:element name="StateProvince" type="xsd:string" />
<xsd:element name="PostalCode" type="xsd:string" />
...
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name="getRequest">
<wsdl:part name="body" element="p2:AddrRequest"/>
</wsdl:message>
<wsdl:message name="returnResponse">
<wsdl:part name="body" element="p2:AddrResponse"/>
</wsdl:message>
<wsdl:portType name="MI_Request_To_Grp1PortType">
<wsdl:operation name="MI_Request_To_Grp1">
<wsdl:input message="p1:getRequest"/>
<wsdl:output message="p1:returnResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="MI_Request_To_Grp1Binding" type="p1:MI_Request_To_Grp1PortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="MI_Request_To_Grp1">
<soap:operation style="document" soapAction="http://someservicehere.com/soap1.1"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="BusService_Grp1AddrVal_WebService">
<wsdl:port name="MI_Request_To_Grp1Port" binding="p1:MI_Request_To_Grp1Binding">
<soap:address location="http://me.com"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
wstools successfully generates the java files for the 2 objects, the service and remote interfaces. however, the debug logging shows the following similar errors:
org.jboss.ws.tools.helpers.MappingFileGeneratorHelper:getJavaTypeAsString:758 - Typemapping lookup failed for {urn:grainger-com:xi:addrval_webservice:types}AddrRequest
org.jboss.ws.tools.helpers.MappingFileGeneratorHelper:getJavaTypeAsString:759 - Falling back to identifier generation
org.jboss.ws.tools.helpers.MappingFileGeneratorHelper:getJavaTypeAsString:758 - Typemapping lookup failed for {urn:grainger-com:xi:addrval_webservice:types}AddrResponse
org.jboss.ws.tools.helpers.MappingFileGeneratorHelper:getJavaTypeAsString:759 - Falling back to identifier generation
although i have used wstools to generate the java classes, i am not using the JBoss generated jaxrpc-mapping.xml to create the service instance. the following is my java code:
ServiceFactoryImpl factory = new ServiceFactoryImpl();
QName namespace = new QName("urn:me-com:xi:addrval_webservice", "BusService_Grp1AddrVal_WebService");
ServiceImpl service = null;
try {
service = (ServiceImpl) factory.createService(this.getURL(wsdlLocation), namespace);
} catch (ServiceException sex) {
// whoops
}
return service;
it appears that the JBoss api cannot successfully find the elements from the messages. why would that be?
i have validated my wsdl vs. the w3c specifications (or at least i think i have) and the wsdl can successfully hit the service via XmlSpy.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042426#4042426
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042426
17 years, 8 months
[JBossWS] - how to deal with unicode
by thanatosis
I wrote a little library that can do simple translations, for example, i can select an operation such as english -> russian. Then if i send my library the string "greetings" it will return to me "??????" (privet) in cyrillic. Since java stores it's strings in unicode, this is all very easy, so long as the result string gets output with something like this :
PrintStream out = new PrintStream(System.out, true, "UTF-8");
out.print(results);
I'm trying to wrap a POJO web service around it, and it works fine with latin chars, but with things like cyrillic, something in the soap stack is mangling up my result string. I don't know what kind of output encoding the xml writer is using, but the string it generates is useless.
is it possible to tell the soap stack to use UTF-8? I'm not sure what can be done to solve my problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042272#4042272
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042272
17 years, 8 months
[JBossWS] - Generate WSDL (From JBoss Eclipse IDE or Command line)
by grdzeli_kaci
hi all,
i am newbie on this,
i need help.
i have documentation about Jboss Web Services and i am trying to run one small example (This is Thomas Diesler's example)
here is example from doc:
1. Remote Interface :
| import javax.ejb.Remote;
| public interface EJB3RemoteInterface {
| String echo(String input);
| }
|
2. Implementation
| import javax.annotation.Resource;
| import javax.ejb.Remote;
| import javax.ejb.SessionContext;
| import javax.ejb.Stateless;
| import javax.jws.WebMethod;
| import javax.jws.WebService;
| import javax.jws.soap.SOAPBinding;
| import org.jboss.annotation.ejb.RemoteBinding;
| import org.jboss.ws.annotation.WebContext;
|
| /**
| * Test the JSR-181 javax.jws.WebService annotation on an EJB3 endpoint.
| *
| * Uses the wsdlLocation attribute.
| *
| * @author Thomas.Diesler(a)jboss.org
| * @since 29-Apr-2005
| */
| @WebService(
| name = "EndpointInterface",
| targetNamespace = "http://www.openuri.org/2004/04/HelloWorld",
| serviceName = "TestService",
| wsdlLocation = "META-INF/wsdl/TestService.wsdl")
| @WebContext(contextRoot = "/jaxws-samples-webservice02-ejb3", urlPattern = "/*")
| @SOAPBinding(style = javax.jws.soap.SOAPBinding.Style.RPC)
| @Remote(EJB3RemoteInterface.class)
| @RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
| @Stateless
| public class EJB3Bean02 implements EJB3RemoteInterface {
| @Resource
| SessionContext sessionContext;
| @WebMethod
| public String echo(String input) {
| System.out.println("Reseive = " + input);
| return input + " - Reseived";
| }
| }
|
3. soapui-project.xml
| <?xml version="1.0" encoding="UTF-8"?>
| <con:soapui-project name="CustomerCare" soapui-version="SNAPSHOT" xmlns:con="http://eviware.com/soapui/config">
| <con:settings>
| <con:setting id="Output Classes Directory">/CustomerCare/bin</con:setting>
| <con:setting id="Output Source Directory">src</con:setting>
| <con:setting id="JBossWS wstools">/home/paatal/InstalledPrograms/jbossws-1.2.1.GA/install/bin</con:setting>
| <con:setting id="Add JBossWS JAR">true</con:setting>
| <con:setting id="com.eviware.soapui.jbosside.jbosswsNature">true</con:setting>
| </con:settings>
| </con:soapui-project>
|
i add JbossWs Nature For My Project from right click on project and add JBossWS -> Add JBossWS Nature,
I want generate WSDL from this class (EJB3Bean02)
after all i tried to generate wsdl from right click on this class and JBossWS -> Publish as web service, enter some parameters and than click generate but i got an error like this :
|
| Running JBossWS wstools for [CustomerCare]
| directory: /home/paatal/InstalledPrograms/Temp/Workshop_Studio_3.2_589/workspace/CustomerCare
| command: sh -c .//home/paatal/InstalledPrograms/jbossws-1.2.1.GA/install/bin/wstools.sh -cp bin -config /tmp/wstools-config52642.xml -dest /home/paatal/InstalledPrograms/Temp/Workshop_Studio_3.2_589/workspace/CustomerCare/src
| -cp: .//home/paatal/InstalledPrograms/jbossws-1.2.1.GA/install/bin/wstools.sh: No such file or directory
|
There is Incorrect path (There is two backslash - > ".//" i don't know why :( ) Is This JBoss Eclipse IDE Bug or maybe i have something incorrect
i configure my JBossWS Instalation Directory From Window -> Preferances -> JBoss Eclipse IDE -> Integrated Tools and set classpath for JBossWS wstools : "/home/paatal/InstalledPrograms/jbossws-1.2.1.GA/install/bin"
am i right ? can anybody help me on it ???
after all i tried to generate wsdl from command line without JBoss Eclipse IDE
| paatal@paatal:~/InstalledPrograms/jbossws-1.2.1.GA/install/bin> ./wstools.sh -cp bin -config /tmp/wstools-config52642.xml -dest /home/paatal/InstalledPrograms/Temp/Workshop_Studio_3.2_589/workspace/CustomerCare/src
|
but i got another error like This :
| Exception in thread "main" java.lang.NoClassDefFoundError: javax/jws/soap/SOAPBinding$ParameterStyle
| at org.jboss.ws.tools.helpers.ToolsHelper.handleJavaToWSDLGeneration(ToolsHelper.java:105)
| at org.jboss.ws.tools.WSTools.process(WSTools.java:133)
| at org.jboss.ws.tools.WSTools.generate(WSTools.java:69)
| at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
| at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
|
did i something incorrect ?
can anybody help me ?
Regards,
Paata.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042125#4042125
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042125
17 years, 8 months
[JBossWS] - java.lang.NoSuchMethodError during webservice deployment
by trivedi
Hi,
I am deploying a document style webservice on jboss4.0.4GA and jbossws1.2.1. I was getting the following error:
=================================
2007-05-01 20:06:07,788 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/D:/Program Files/jboss-4.0.4.GA/server/default/deploy/TestDoc.war
java.lang.NoSuchMethodError: com.sun.xml.bind.api.JAXBRIContext.newInstance([Ljava/lang/Class;)Ljavax/xml/bind/JAXBContext;
at org.jboss.ws.metadata.acessor.JAXBAccessor$1.create(JAXBAccessor.java:67)
at org.jboss.ws.metadata.acessor.JAXBAccessor$1.create(JAXBAccessor.java:54)
at org.jboss.ws.metadata.umdm.ParameterMetaData.eagerInitialize(ParameterMetaData.java:470)
at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:466)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:516)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:502)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:490)
at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMetaData.java:429)
at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:192)
at org.jboss.ws.core.server.ServiceEndpoint.start(ServiceEndpoint.java:112)
at org.jboss.ws.core.server.ServiceEndpointManager.startServiceEndpoint(ServiceEndpointManager.java:646)
at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:140)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
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 $Proxy47.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(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.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)
==================================
Pls help me in resolving this issue.
Thanks,'
trivedi
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042105#4042105
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042105
17 years, 8 months
[JBossWS] - Autogeneration of wrapper beans not supported with JAXRPC
by timeagentess
Hello all,
I am using JBoss as the application server for deploying web services. In particular, I use wscompile to generate the wsdl file, and I am starting from java beans with xdoclet annotations.
The rpc/literal web services work perfectly, even tested them with a .NET client, arrays are passed ok as well.
When I set wscompile to use document/literal (without any other modifications), though, JBoss complains on deployment about the .ear file and says :
org.jboss.deployment.DeploymentException: Cannot start service endpoint; - nested throwable: (org.jboss.ws.WSException: Autogeneration of wrapper beans not supported with JAXRPC)
The only Google hits when searching for that error point to the JBossWS SVN repository. Browsing through the JBossWS SVN, I suspect that one of these two operations:
+ ClassLoader loader = getOperationMetaData().getEndpointMetaData().getClassLoader();
+ wrapperBean = JavaUtils.loadJavaType(javaTypeName, loader);
returns a null in the loadWrapperBean() method in the org.jboss.ws.metadata.umdm.ParameterMetaData class. But these are only speculations.
Has someone any idea regarding this problem, perhaps something that I am doing wrong? Or maybe a more straightforward way of building document/literal WS, if nothing else?
Thanks a lot!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042070#4042070
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042070
17 years, 8 months
[JBossWS] - Re: JAX-WS servlet initializing error during deployment of j
by trivedi
"oskar.carlstedt" wrote : Hi Trivedi!
|
| Can you please give me some more of your code. Then I might help you. I have been struggeling al lot now an finally found a solution that seems to work for me.
|
| //Oskar
|
Hi Oskar,
Sorry for the late response from my side. Currently I again started working on web services, got stuck now with the above issue. Here is the code that I written:
Here is my wsdl
----------------------------------------------------------------------
<definitions name='EchoService' targetNamespace='http://echo/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://echo/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<xs:schema targetNamespace='http://echo/' version='1.0' xmlns:tns='http://echo/' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
<xs:element name='echo' type='tns:echo'/>
<xs:element name='echoResponse' type='tns:echoResponse'/>
<xs:complexType name='echo'>
<xs:sequence>
<xs:element minOccurs='0' name='arg0' type='xs:string'/>
</xs:sequence>
</xs:complexType>
<xs:complexType name='echoResponse'>
<xs:sequence>
<xs:element minOccurs='0' name='return' type='xs:string'/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
<soap:operation soapAction=''/>
<soap:body use='literal'/>
<soap:body use='literal'/>
<soap:address location='http://AIBD305014842:8080/AddNumbersWS/Echo'/>
----------------------------------------------------------
Using Jax-WS generated the java classes from it.
Here is the interface that got created with it
================================
@WebService(name = "Echo", targetNamespace = "http://echo/")
public interface Echo {
/**
*
* @param arg0
* @return
* returns java.lang.String
*/
@WebMethod
@WebResult(targetNamespace = "")
@RequestWrapper(localName = "echo", targetNamespace = "http://echo/", className = "echo.Echo_Type")
@ResponseWrapper(localName = "echoResponse", targetNamespace = "http://echo/", className = "echo.EchoResponse")
public String echo(
@WebParam(name = "arg0", targetNamespace = "")
String arg0);
}
The Implementation Class is here:
package echo;
@javax.jws.WebService(endpointInterface="echo.Echo",
portName="EchoPort")
public class EchoImpl implements Echo{
public String echo(String arg0) {
return "hi " + arg0;
}
}
Here are the artifacts that i created for this service:
1. web.xml
<servlet-name>Echo</servlet-name>
<display-name>Echo</display-name>
JAX-WS endpoint - InteropWS
<servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<servlet-mapping>
<servlet-name>Echo</servlet-name>
<url-pattern>/Echo</url-pattern>
</servlet-mapping>
2. sun-jaxws.xml
<endpoint name="Echo"
implementation="echo.EchoImpl"
url-pattern="/Echo" />
And after this I created the war from it by adding the following jars into WEB-INF lib folder
1. jaxws-api.jar 2.jaxws-rt.jar 3. jaxws-tools.jar 4. jsr181-api.jar 5.jsr250-api.jar
After deploying I was getting the above error.
Pls help me in running this service. Thanks in advance.
Again I am really sorry for the late reply.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042046#4042046
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042046
17 years, 8 months
[JBossWS] - Error with JbossWS in JbossAS 4.0.4
by trivedi
Here is my env:
JbossAS = 4.0.4 GA
JbossWS = 1.2.1 GA
Java = 1.5
I have created a webservice and deployed it in JbossAS. During deployment I got the following error:
====================================
14:08:48,110 INFO [TomcatDeployer] deploy, ctxPath=/Echo, warUrl=.../tmp/deploy/tmp34622Echo-exp.war/
14:08:48,281 INFO [WSDLFilePublisher] WSDL published to: file:/D:/Program Files/jboss-4.0.4.GA/server/default/data/wsdl/Echo.war/EchoImplService34623.wsdl
14:08:48,297 ERROR [MainDeployer] Could not start deployment: file:/D:/Program Files/jboss-4.0.4.GA/server/default/deploy/Echo.war
java.lang.NoSuchMethodError: com.sun.xml.bind.api.JAXBRIContext.newInstance([Ljava/lang/Class;)Ljavax/xml/bind/JAXBContext;
at org.jboss.ws.metadata.acessor.JAXBAccessor$1.create(JAXBAccessor.java:67)
at org.jboss.ws.metadata.acessor.JAXBAccessor$1.create(JAXBAccessor.java:54)
at org.jboss.ws.metadata.umdm.ParameterMetaData.eagerInitialize(ParameterMetaData.java:470)
at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:466)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:516)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:502)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:490)
at org.jboss.ws.metadata.umdm.ServiceMetaData.eagerInitialize(ServiceMetaData.java:429)
at org.jboss.ws.metadata.umdm.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:192)
at org.jboss.ws.core.server.ServiceEndpoint.start(ServiceEndpoint.java:112)
at org.jboss.ws.core.server.ServiceEndpointManager.startServiceEndpoint(ServiceEndpointManager.java:646)
at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:140)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
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 $Proxy47.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(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.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:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(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.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(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.server.Invocation.invoke(Invocation.java:86)
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 $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(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.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 $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:464)
at java.lang.Thread.run(Thread.java:595)
14:08:48,391 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
14:08:48,656 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
============================================
However I was able to see my wsdl thru "http://localhost:8080/Echo/Echo?wsdl" link. And I wrote the WS client in C# and trying to execute it but getting the exception in C#. I went and looked into server log file and following error has been showed:
===============================================
4:15:49,547 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: Endpoint cannot handle requests in state: CREATED
at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:176)
at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448)
at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
==========================================
Pls help me to resolve this issue, I was trying since 2 whole days to successfully deploy a simple webservice on jboss, but I couldnt. Need somebody help. Thanks in advance.
Trivedi
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042036#4042036
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042036
17 years, 8 months