Error when using wise to consume a webservice| JBoss.org Content Archive (Read Only)

15. Re: Error when using wise to consume a webservice

maeste Sep 4, 2008 5:27 AM (in response to stlecho)

You have to use a jdk to start the server (aka kdk have to be your JAVA-HOME). JAX-WS tools need to compile classes on the fly, so they need tools.jar included only in jdk (not in jre)

16. Re: Error when using wise to consume a webservice

stlecho Sep 4, 2008 5:38 AM (in response to stlecho)

set JAVA_HOME results in d:\java\jdk1.5.0_14, so I am pretty sure that JBossESB is using a JDK.

I've read the following comment in run.bat: A full JDK with tools.jar is not required anymore since jboss web packages the eclipse jdt compiler and javassist has its own internal compiler.

17. Re: Error when using wise to consume a webservice

maeste Sep 4, 2008 5:50 AM (in response to stlecho)

That's right for jboss web package, unfortunately not for WISE.
Anyway, The error you reported is caused by JAX-WS tools API can find a compiler in your class path. Normally it's because you are using a jre instead of jdk. To be totally sure have a look to boot.log where you can see all jvm properties and setting of jvm which is running your Jboss.

18. Re: Error when using wise to consume a webservice

stlecho Sep 4, 2008 6:07 AM (in response to stlecho)

I was debugging in Eclipse, but now that I've started from the command-line javac is found. However, now I receive an encoding error. This is probably linked to the encoding specified in the WSDL (UTF-8) and the use of (non UTF-8 compatible?) accented characters within this WSDL.

Is there a way to override the encoding specified in the WSDL and force JAWXS to use for instance the ISO8859-1 encoding ?

2008-09-04 11:55:44,311 ERROR [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] [domain:http://www.w3.org/TR/1998/REC-xml-19980210]::[key=InvalidByte]::Message=Invalid byte 2 of 3-byte UTF-8 sequence.
2008-09-04 11:55:44,311 ERROR [STDERR] it.javalinux.wise.core.exceptions.WiseRuntimeException: Error occurred while consuming wsdl: https://e-depottest.smals-mvm.be/fphp/3.1/ws/PersonQuery.jws?WSDL=
2008-09-04 11:55:44,311 ERROR [STDERR] at it.javalinux.wise.core.exceptions.WiseRuntimeException.rethrow(WiseRuntimeException.java:44)
2008-09-04 11:55:44,311 ERROR [STDERR] at it.javalinux.wise.core.client.WSDynamicClient.init(WSDynamicClient.java:156)
2008-09-04 11:55:44,342 ERROR [STDERR] at it.javalinux.wise.core.client.WSDynamicClient.init(WSDynamicClient.java:94)
2008-09-04 11:55:44,342 ERROR [STDERR] at it.javalinux.wise.core.client.WSDynamicClientFactory.getClient(WSDynamicClientFactory.java:121)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.java:225)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
2008-09-04 11:55:44,342 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
2008-09-04 11:55:44,342 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
2008-09-04 11:55:44,342 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2008-09-04 11:55:44,342 ERROR [STDERR] Caused by: org.apache.xerces.xni.XNIException: Parser should stop: [domain:http://www.w3.org/TR/1998/REC-xml-19980210]::[key=InvalidByte]::Message=Invalid byte 2 of 3-byte UTF-8 sequence.
2008-09-04 11:55:44,342 ERROR [STDERR] at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler.fatalError(JBossXSErrorHandler.java:78)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source)
2008-09-04 11:55:44,342 ERROR [STDERR] at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(Unknown Source)
2008-09-04 11:55:44,358 ERROR [STDERR] at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown Source)
2008-09-04 11:55:44,358 ERROR [STDERR] at org.apache.xerces.impl.xs.traversers.XSDHandler.resolveSchema(Unknown Source)
2008-09-04 11:55:44,358 ERROR [STDERR] at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown Source)
2008-09-04 11:55:44,358 ERROR [STDERR] at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source)
2008-09-04 11:55:44,374 ERROR [STDERR] at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)
2008-09-04 11:55:44,374 ERROR [STDERR] at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source)
2008-09-04 11:55:44,374 ERROR [STDERR] at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:182)
2008-09-04 11:55:44,374 ERROR [STDERR] at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:391)
2008-09-04 11:55:44,405 ERROR [STDERR] at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:172)
2008-09-04 11:55:44,405 ERROR [STDERR] at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128)
2008-09-04 11:55:44,405 ERROR [STDERR] at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:321)
2008-09-04 11:55:44,405 ERROR [STDERR] at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:85)
2008-09-04 11:55:44,405 ERROR [STDERR] at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:131)
2008-09-04 11:55:44,405 ERROR [STDERR] at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:61)
2008-09-04 11:55:44,421 ERROR [STDERR] at javax.xml.ws.Service.<init>(Service.java:83)
2008-09-04 11:55:44,421 ERROR [STDERR] at be.belgium.fsb.fphp.v3_0.PersonQuery.<init>(PersonQuery.java:40)
2008-09-04 11:55:44,421 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
2008-09-04 11:55:44,421 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
2008-09-04 11:55:44,436 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
2008-09-04 11:55:44,436 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
2008-09-04 11:55:44,452 ERROR [STDERR] at java.lang.Class.newInstance0(Class.java:350)
2008-09-04 11:55:44,452 ERROR [STDERR] at java.lang.Class.newInstance(Class.java:303)
2008-09-04 11:55:44,452 ERROR [STDERR] at it.javalinux.wise.core.client.WSDynamicClient.init(WSDynamicClient.java:150)
2008-09-04 11:55:44,452 ERROR [STDERR] ... 8 more

19. Re: Error when using wise to consume a webservice

maeste Sep 4, 2008 4:01 PM (in response to stlecho)

Hmm.. it's strange.
First of all, the problem is not specific to wise. It seems a problem of JBossWS during parsing. What is strange is that I just tried the wsdl you sent me and it seems to work.The only difference is that I used it reading a local file instead of http connection. Would you mind to make this try?
BTW (not related to your problems, but a good suggestion coming in my mind), be sure to put property wise.forceImportObject=false for production environment to avoid excessive regeneration of object and compilations.

thanks for the interest

20. Re: Error when using wise to consume a webservice

stlecho Sep 5, 2008 8:04 AM (in response to stlecho)

I'm referencing the WSDL locally, but the results remains the same :o(.

Based on http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101882, I've used the -Dfile.encoding setting and the result is ok :o)).

Regards, Stefan Lecho.

21. Re: Error when using wise to consume a webservice

stlecho Sep 5, 2008 8:06 AM (in response to stlecho)

If the wsdl is referenced with value="PersonQuery.wsdl", the wsdl should be located in %JBOSS_HOME%/bin.

I would like to deploy the WSDL in the ESB archive. Do you have an idea as on how to reference the WSDL contained in the ESB archive ?

22. Re: Error when using wise to consume a webservice

stlecho Sep 5, 2008 8:46 AM (in response to stlecho)

I'm making some progress, but now I'm receiving another exception.

I would like to debug this issue in Eclipse, but due to the earlier JDK-javac problem I am unable to do so. Any idea how this can be done ?

OperationMetaData:
 qname={urn://fsb.belgium.be/fphp/v3_0}findPerson
 javaName=findPerson
 style=document/literal/WRAPPED
 oneWay=false
 soapAction=urn://fsb.belgium.be/fphp/v3_0/findPerson
ParameterMetaData:
 xmlName={urn://fsb.belgium.be/fphp/v3_0}findPerson
 partName=findPerson
 xmlType={urn://fsb.belgium.be/fphp/v3_0}findPerson
 javaType=be.belgium.fsb.fphp.v3_0.FindPerson
 mode=IN
 inHeader=false
 index=0
 wrappedParameters=[[name = {urn://fsb.belgium.be/fphp/v3_0/query}query, type = be.belgium.fsb.fphp.v3_0.query.Query, typeArgs = null, variable = query, index = 0]]
ReturnMetaData:
 xmlName={urn://fsb.belgium.be/fphp/v3_0}findPersonResponse
 partName=findPersonResponse
 xmlType={urn://fsb.belgium.be/fphp/v3_0}findPersonResponse
 javaType=be.belgium.fsb.fphp.v3_0.FindPersonResponse
 mode=OUT
 inHeader=false
 index=-1
 wrappedParameters=[[name = {urn://fsb.belgium.be/fphp/v3_0/person}personList, type = be.belgium.fsb.fphp.v3_0.person.PersonList, typeArgs = null, variable = personList, index = -1]]
2008-09-05 14:37:24,309 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Configure SOAPBinding
2008-09-05 14:37:24,324 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: PRE
2008-09-05 14:37:24,324 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: ENDPOINT
2008-09-05 14:37:24,324 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: POST
2008-09-05 14:37:24,324 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=PRE,info=[service={urn://fsb.belgium.be/fphp/v3_0}PersonQuery,port={urn://fsb.belgium.be/fphp/v3_0}PersonQuerySoap,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]
2008-09-05 14:37:24,324 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=POST,info=[service={urn://fsb.belgium.be/fphp/v3_0}PersonQuery,port={urn://fsb.belgium.be/fphp/v3_0}PersonQuerySoap,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]
2008-09-05 14:37:24,324 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=ENDPOINT,info=[service={urn://fsb.belgium.be/fphp/v3_0}PersonQuery,port={urn://fsb.belgium.be/fphp/v3_0}PersonQuerySoap,binding=http://schemas.xmlsoap.org/wsdl/soap/http]]
2008-09-05 14:37:24,324 DEBUG [org.jboss.ws.core.jaxws.binding.BindingImpl] setHandlerChain: []
2008-09-05 14:37:24,324 DEBUG [org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl] No port configuration for: {urn://fsb.belgium.be/fphp/v3_0}PersonQuerySoap
2008-09-05 14:37:24,324 INFO [org.jboss.soa.esb.actions.soap.wise.SOAPClient] adding logging handler
2008-09-05 14:37:24,356 DEBUG [org.jboss.ws.core.jaxws.binding.BindingImpl] setHandlerChain: [it.javalinux.wise.core.client.handler.LoggingHandler@15055c5]
2008-09-05 14:37:24,356 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/fphp_esb_request/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: b408f240-7661-4bcc-9bd6-19a69ec71181 RelatesTo: jms:correlationID#b408f240-7661-4bcc-9bd6-19a69ec71181 ]
java.lang.NullPointerException
 at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.java:280)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
 at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 at java.lang.Thread.run(Thread.java:595)
2008-09-05 14:37:24,356 DEBUG [com.notary.esb.jboss.ws.FSBRequestAction] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

2008-09-05 14:37:24,356 DEBUG [com.notary.esb.jboss.ws.FSBRequestAction] !ERROR!

23. Re: Error when using wise to consume a webservice

stlecho Sep 5, 2008 10:01 AM (in response to stlecho)

I'm able to debug in Eclipse and I found out that their was a mismatch between the SOAPAction defined in the WSDL and the one defined in the SOAPClient configuration.

The WSDL specifies the soapAction as

<soap:operation soapAction="urn://fsb.belgium.be/fphp/v3_0/findPerson" style="document"/>

. In the SOAPAction I'm currently using findPerson, without the urn:// part. This is working, but I was wondering if this is the correct way of working ?

The XML request should be send to another location as the one specified in the WSDL and I am confronted with the same issue reported in http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155812#4155812. Is the fix for this issue contained in the latest JBossESB release ?

2008-09-05 15:26:16,081 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Setting request header with Content-Type : text/xml; charset=UTF-8
2008-09-05 15:26:18,409 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Error invoking http client invoker.
java.net.UnknownHostException: vilcanota
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
 at java.net.Socket.connect(Socket.java:520)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:152)