Error generating WebServices thro' Axis

Hi , On generating webservices for a simple program ( which add's two integer) I am getting following error in client side -
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: java.lang.InstantiationException: com.infosys.WebService.WebServiceProcessor
faultActor:
faultNode:
faultDetail:
{_http://xml.apache.org/axis/}stackTrace:java.lang.InstantiationException_: com.infosys.WebService.WebServiceProcessor
at org.apache.axis.message.SOAPFaultBuilder.createFault(_SOAPFaultBuilder.java:222_)
at org.apache.axis.message.SOAPFaultBuilder.endElement(_SOAPFaultBuilder.java:129_)
at org.apache.axis.encoding.DeserializationContext.endElement(_DeserializationContext.java:1087_)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContext.parse(_DeserializationContext.java:227_)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(_SOAPPart.java:696_)
at org.apache.axis.Message.getSOAPEnvelope(_Message.java:435_)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(_MustUnderstandChecker.java:62_)
at org.apache.axis.client.AxisClient.invoke(_AxisClient.java:206_)
at org.apache.axis.client.Call.invokeEngine(_Call.java:2784_)
at org.apache.axis.client.Call.invoke(_Call.java:2767_)
at org.apache.axis.client.Call.invoke(_Call.java:2443_)
at org.apache.axis.client.Call.invoke(_Call.java:2366_)
at org.apache.axis.client.Call.invoke(_Call.java:1812_)
at com.infosys.WebService.WebServiceProcessorSoapBindingStub.addNumber(_WebServiceProcessorSoapBindingStub.java:108_)
at com.infosys.WebService.WebServiceProcessorProxy.addNumber(_WebServiceProcessorProxy.java:50_)
at com.infosys.WebService.WebTest.main(_WebTest.java:16_)
Can anybody giude as what may be the problem?The server side Implementation class can be instantiated.

Hi,
Class WebServiceProcessor is an interface for the webservices. On instantiating its implementation class , it is thrwoing the above mentioned error in client side . Both cleint and server component is a part of Web Component and deployed in server , so those all should be in runtime classpath.
Can you tell me exactly what I need to do here?

Similar Messages

Error Generating WebService for SOAP over JMS

Hi,
I've been tring to create an addition web service thta takes two input and returns the sum. I was able to generate the WSDL using JDevelopers GUI tool for generating WSDL, but I notices that there was no transport layer, in thebinding that suppoerted SOAP, and the "create web service from WSDL" wizard also gave and error message:
oracle.jdeveloper.webservices.model.WebServiceException: The chosen WSDL contains no SOAP 1.1 bindings and is therefore unsuitable for generation of a JAX-RPC web service for WLS. Only SOAP 1.1 bindings are supported for generation of JAX-RPC web services for deployment to WLS.
This is the WSDL I created:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="http://www.example.org/addition"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.example.org/addition"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:jms="http://schemas.xmlsoap.org/wsdl/jms/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/">
<types>
<xsd:schema targetNamespace="http://www.example.org/addition/types"
elementFormDefault="qualified"/>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:add="http://www.example.org/addition"
targetNamespace="http://www.example.org/addition"
elementFormDefault="qualified">
<xsd:element name="additionInput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="a" type="xsd:int"/>
<xsd:element name="b" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="additionOutput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sum" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
<message name="AdditionInputMessage">
<part name="payload" element="tns:additionInput"/>
</message>
<message name="AdditionOutputMessage">
<part name="payload" element="tns:additionOutput"/>
</message>
<portType name="AdditionPortType">
<operation name="addition">
<input message="tns:AdditionInputMessage"/>
<output message="tns:AdditionOutputMessage"/>
</operation>
</portType>
<binding name="AdditionPortTypeJMSBinding" type="tns:AdditionPortType">
<jms:binding type="ObjectMessage"/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap typeName="tns:additionInput" formatType=""/>
<format:typeMap typeName="tns:additionOutput" formatType=""/>
</format:typeMapping>
<operation name="addition">
<input>
<jms:input parts="payload"/>
<jms:property name="payloadProperty" part="payload"/>
</input>
<output>
<jms:output parts="payload"/>
<jms:property name="payloadProperty" part="payload"/>
</output>
</operation>
</binding>
<service name="AdditionPortType">
<port name="AdditionPortTypePort" binding="tns:AdditionPortTypeJMSBinding"/>
</service>
</definitions>
Could someone please help me out? I've been struggling with this problem for two weeks and can't make any headway. It's really driving me nuts. I've looked all over the web, and while everyone agrees that SOAP over JMS is possible, no one sems to have a working solution. One example I was able to get hold of used ant for deployment, but the deploy task failed when I ran it. Please, please help me.

Hi,
I've been tring to create an addition web service thta takes two input and returns the sum. I was able to generate the WSDL using JDevelopers GUI tool for generating WSDL, but I notices that there was no transport layer, in thebinding that suppoerted SOAP, and the "create web service from WSDL" wizard also gave and error message:
oracle.jdeveloper.webservices.model.WebServiceException: The chosen WSDL contains no SOAP 1.1 bindings and is therefore unsuitable for generation of a JAX-RPC web service for WLS. Only SOAP 1.1 bindings are supported for generation of JAX-RPC web services for deployment to WLS.
This is the WSDL I created:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="http://www.example.org/addition"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.example.org/addition"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:jms="http://schemas.xmlsoap.org/wsdl/jms/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/">
<types>
<xsd:schema targetNamespace="http://www.example.org/addition/types"
elementFormDefault="qualified"/>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:add="http://www.example.org/addition"
targetNamespace="http://www.example.org/addition"
elementFormDefault="qualified">
<xsd:element name="additionInput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="a" type="xsd:int"/>
<xsd:element name="b" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="additionOutput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sum" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
<message name="AdditionInputMessage">
<part name="payload" element="tns:additionInput"/>
</message>
<message name="AdditionOutputMessage">
<part name="payload" element="tns:additionOutput"/>
</message>
<portType name="AdditionPortType">
<operation name="addition">
<input message="tns:AdditionInputMessage"/>
<output message="tns:AdditionOutputMessage"/>
</operation>
</portType>
<binding name="AdditionPortTypeJMSBinding" type="tns:AdditionPortType">
<jms:binding type="ObjectMessage"/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap typeName="tns:additionInput" formatType=""/>
<format:typeMap typeName="tns:additionOutput" formatType=""/>
</format:typeMapping>
<operation name="addition">
<input>
<jms:input parts="payload"/>
<jms:property name="payloadProperty" part="payload"/>
</input>
<output>
<jms:output parts="payload"/>
<jms:property name="payloadProperty" part="payload"/>
</output>
</operation>
</binding>
<service name="AdditionPortType">
<port name="AdditionPortTypePort" binding="tns:AdditionPortTypeJMSBinding"/>
</service>
</definitions>
Could someone please help me out? I've been struggling with this problem for two weeks and can't make any headway. It's really driving me nuts. I've looked all over the web, and while everyone agrees that SOAP over JMS is possible, no one sems to have a working solution. One example I was able to get hold of used ant for deployment, but the deploy task failed when I ran it. Please, please help me.

Error while invoking a webservice using Axis deployed in tomacat from Bpel

Hi,
I am trying to invoke a Axis webservice(from Java class to WSDL- bottom up java bean webservice approach) developed in Exclipse IDE, deployed in Tomcat.
When i am trying to invoke the service, from Bpel from Jdeveloper it is throwing error as such :
Invoke_1 (faulted)
[2009/05/22 14:32:18] Faulted while invoking operation "storeLoanData" on provider "LoanDataPersist".less
-<messages>
-<input>
-<Invoke_1_storeLoanData_InputVariable>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="p_request">
-<p_request xmlns="" xmlns:def="http://dtos.demo.com" xsi:type="def:LoanDataPersistRequest" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<customerName>wew
</customerName>
<netIncome>12
</netIncome>
<loanAmount>12
</loanAmount>
<realEstateAddress>wew
</realEstateAddress>
<customerID/>
</p_request>
</part>
</Invoke_1_storeLoanData_InputVariable>
</input>
-<fault>
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="summary">
<summary>exception on JaxRpc invoke: trailing block elements must have an id attribute
</summary>
</part>
</remoteFault>
</fault>
</messages>
I may add that, the WSDL generated is using "soap:enc:array ", rpc style.
Can anyone tell me the reason and suggest .

Hi Marc,
Thanks for the guidancer. But sir, i am unable to detect at which place i have to do the required changes.I found p_request as a parameter in the method only in the interface only.
As bcos ultimately , i am generating the tomcat /axis web service (WSDL) from the java class, which is using 2 Request and response java bean, in which they are doing someing like this:
private static org.apache.axis.description.TypeDesc typeDesc =
new org.apache.axis.description.TypeDesc(LoanDataPersistRequest.class, true);
static {
typeDesc.setXmlType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"));
org.apache.axis.description.ElementDesc elemField = new org.apache.axis.description.ElementDesc();
elemField.setFieldName("customerName");
elemField.setXmlName(new javax.xml.namespace.QName("", "customerName"));
elemField.setXmlType(new javax.xml.namespace.QName("", "string"));
elemField.setNillable(true);
etc etc...................}
And second thing is when the WSDL is generated, from that the stubs and skeletons is generated to test the service.
There in the Stub i found out "p_request" in this place:
private static void _initOperationDesc1(){
org.apache.axis.description.OperationDesc oper;
org.apache.axis.description.ParameterDesc param;
oper = new org.apache.axis.description.OperationDesc();
oper.setName("storeLoanData");
param = new org.apache.axis.description.ParameterDesc(*new javax.xml.namespace.QName("", "p_request")*, org.apache.axis.description.ParameterDesc.IN, new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"), com.demo.dtos.LoanDataPersistRequest.class, false, false);
oper.addParameter(param);
oper.setReturnType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistResponse"));
oper.setReturnClass(com.demo.dtos.LoanDataPersistResponse.class);
oper.setReturnQName(new javax.xml.namespace.QName("", "storeLoanDataReturn"));
oper.setStyle(org.apache.axis.constants.Style.RPC);
oper.setUse(org.apache.axis.constants.Use.ENCODED);
_operations[0] = oper;
And in skeleton :
static {
org.apache.axis.description.OperationDesc _oper;
org.apache.axis.description.FaultDesc _fault;
org.apache.axis.description.ParameterDesc [] _params;
_params = new org.apache.axis.description.ParameterDesc [] {
new org.apache.axis.description.ParameterDesc(*new javax.xml.namespace.QName("", "p_request")*, org.apache.axis.description.ParameterDesc.IN, new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"), com.demo.dtos.LoanDataPersistRequest.class, false, false),
oper = new org.apache.axis.description.OperationDesc("storeLoanData", params, new javax.xml.namespace.QName("", "storeLoanDataReturn"));
_oper.setReturnType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistResponse"));
_oper.setElementQName(new javax.xml.namespace.QName("urn:com.demo.service", "storeLoanData"));
_oper.setSoapAction("");
myOperationsList.add(oper);
if (_myOperations.get("storeLoanData") == null) {
_myOperations.put("storeLoanData", new java.util.ArrayList());
((java.util.List)_myOperations.get("storeLoanData")).add(_oper);
PLease suggest if i make some changes in stub and skeleton how it would reflect the WSDL... or else please suggest where shud i do the required changes.

Error generating/activating WebService BW DataSource

Hello,
I created a BW DataSource using WebService in BI7 and I got the following errors when trying to activate it.
Error generating Web service /BIC/CQZBRSDAT00001000
Message no. RSDS301
Error when activating DataSource ZBRSDATA WEBSERVICE
Message no. RSO404
Could anyone please advise for any inputs/tips for the issue? I found below two threads but the OSS Note 913944 appreantly does not exist anymore (not sure if it is being removed, updated, etc).
Web service data source - error RSDS301
Problems with DataSource Web Service BI 7.0
Thanks & Regards,
Andy

Hello
We will move this thread to the [SAP NetWeaver BW|SAP Business Warehouse; forum as this is not a PI specific issue. You will have a better chance of getting a quality answer to your query on this forum.
Regards
XI/PI Moderator

Implementing a Webservice with AXIS, which calls CORBA objects

Hi @all!
First my aim is it to invoke a Webservice by a Client. As toolkit for developing this Webservice I use AXIS 1.0. This Webservice in turn should establish a CORBA connection to a third application.
A direct access to the CORBA objects without the AXIS Webservice works fine. The Webservice without the Corba access is also running errorfree.
When trying to implement a Webservice with AXIS, which calls CORBA objects following fault was generated:
"internal Server Error(500)".
Are there known problems with AXIS in conjunction with CORBA?

Okay here's the error log file:
1000 of lines, which aren't very helpful for me.
As ORB I use JacORB.
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultString: (500)Internal Server Error
faultActor: null
faultDetail:
     null: return code: 500
<html><head><title>Apache Tomcat/4.1.18 - Error report</title><STYLE></STYLE> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Servlet execution threw an exception
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
     at java.lang.Thread.run(Thread.java:484)
</pre></p><p><b>root cause</b> <pre>java.lang.NoClassDefFoundError: org/omg/PortableServer/POAOperations
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:195)
     at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:187)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:171)
     at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:154)
     at org.apache.axis.utils.cache.ClassCache.lookup(ClassCache.java:122)
     at org.apache.axis.providers.java.JavaProvider.getServiceClass(JavaProvider.java:502)
     at org.apache.axis.providers.java.JavaProvider.initServiceDesc(JavaProvider.java:535)
     at org.apache.axis.handlers.soap.SOAPService.getInitializedServiceDesc(SOAPService.java:322)
     at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:477)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:312)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
     at org.apache.axis.deployment.wsdd.WSDDDeployment.getServiceByNamespaceURI(WSDDDeployment.java:503)
     at org.apache.axis.configuration.FileProvider.getServiceByNamespaceURI(FileProvider.java:273)
     at org.apache.axis.MessageContext.getPossibleOperationsByQName(MessageContext.java:226)
     at org.apache.axis.message.BodyBuilder.onStartChild(BodyBuilder.java:150)
     at org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:893)
     at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:459)
     at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:221)
     at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:874)
     at org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java:591)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:747)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1477)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
     at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
     at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
     at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:394)
     at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:232)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:546)
     at org.apache.axis.Message.getSOAPEnvelope(Message.java:377)
     at org.apache.axis.server.AxisServer.invoke(AxisServer.java:304)
     at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:701)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
     at java.lang.Thread.run(Thread.java:484)
</pre></p><HR size="1" noshade><h3>Apache Tomcat/4.1.18</h3></body></html>
(500)Internal Server Error
     at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:630)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:131)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:182)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2113)
     at org.apache.axis.client.Call.invoke(Call.java:2102)
     at org.apache.axis.client.Call.invoke(Call.java:1851)
     at org.apache.axis.client.Call.invoke(Call.java:1777)
     at org.apache.axis.client.Call.invoke(Call.java:1315)
     at CsbClient.main(CsbClient.java:82)
[INFO] enterprise - -Mapping Exception to AxisFault <(500)Internal Server Error>
(WSDDDeployableItem.java:312)
     at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
     at org.apache.axis.deployment.wsdd.WSDDDeployment.getServiceByNamespaceURI(WSDDDeployment.java:503)
     at org.apache.axis.configuration.FileProvider.getServiceByNamespaceURI(FileProvider.java:273)
     at org.apache.axis.MessageContext.getPossibleOperationsByQName(MessageContext.java:226)
     at org.apache.axis.message.BodyBuilder.onStartChild(BodyBuilder.java:150)
     at org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:893)
     at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:459)
     at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:221)
     at org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:874)
     at org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java:591)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:747)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1477)
     at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
     at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
     at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
     at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
     at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:394)
     at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:232)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:546)
     at org.apache.axis.Message.getSOAPEnvelope(Message.java:377)
     at org.apache.axis.server.AxisServer.invoke(AxisServer.java:304)
     at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:701)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
     at java.lang.Thread.run(Thread.java:484)
</pre></p><HR size="1" noshade><h3>Apache Tomcat/4.1.18</h3></body></html>
(500)Internal Server Error
     at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:630)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:131)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:182)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2113)
     at org.apache.axis.client.Call.invoke(Call.java:2102)
     at org.apache.axis.client.Call.invoke(Call.java:1851)
     at org.apache.axis.client.Call.invoke(Call.java:1777)
     at org.apache.axis.client.Call.invoke(Call.java:1315)
     at CsbClient.main(CsbClient.java:82)
Exception in thread "main"

Error in Webservice toRFC

Hi All,
I am generating webservice in ID for an RFC and using this webservice in webdynpro application to get data from R/3 system.It is webservice to RFC synchronous scenario
In RFC response structure data type of one field is "xstring" in R/3 system. If we import this RFC in XI it is changing as "base64Binary" data type.
So if we test this webservice in SOAP sonar tool output for that field is different from the value which get in R/3 system by executing RFC in Se37.For other fields output is coming same as in R/3 output.
If data for that field is sent as "base64Binary" format to webdynpro application, it is not supported.
So in RFC particular field value is converted from "xstring" to "string" and stored in one more field.
Again RFC is imported in XI and webservice is generated.
While testing in SOAP sonar, error is coming as
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_GetPoPdf_Res_: Fatal Error: com.sap.engine.lib.xml.parser.Parser~
New field which we added in RFC is having lot of values and there are also some special characters in that field..How to solve this issue..?
Can any one give me some useful suggestion...
Regards,
Babu

Hi All,
Can any one suggest some ideas to achieve some solution for the problem which I posted
Regards,
Babu

Generated webservices give null result in Flex 3

Hi there, I have a web service on my localhost. Calling this from a PHP page works fine and it returns the expected results. (I pass 2 values and it returns a different string depending on the values passed).
However, in Flex 3, I have generated the webservice proxy classes using the "Data" | "Manage Web Services" dialog. I am consuming these services using the following code:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
     <mx:Button click="clickHandler(event)"/>
     <mx:Script>
          <![CDATA[
               import generated.webservices.*;
               import mx.controls.Alert;
               import mx.rpc.events.FaultEvent;
               public var _ws:SalesService = new SalesService();
               private function clickHandler(_e:MouseEvent):void
                    _ws.addonsaleEventListener(resultHandler);
                    _ws.addSalesServiceFaultEventListener(faultHandler);
                    _ws.onsale(10,90);
               public function resultHandler(_e:OnsaleResultEvent):void
                    if(_e.result == null)
                         Alert.show("result is: null");
                    else
                         Alert.show("result is: "+_e.result);
               public function faultHandler(_e:FaultEvent):void
                    Alert.show(_e.message.toString());
          ]]>
     </mx:Script>
</mx:Application>
The "resultHandler" method is called and the "faultHandler" method is not called, which suggests a result is returned, but _e.result is null in the "resultHandler" method.
Can anyone see if I am missing something in the actionscript?
Andrew.
p.s.
I can post the generated proxy classes, or even the wsdl for the webservice if it helps.
A.

No, they're not exactly the same (see below).
Calling the same web service; Flex 3 is generating a
different result object than Flex 2, and therefore can/will not
type the results as the Array my original app had come to expect.
Is this by design?
A suggested code revision would help, but...
The question in my
original post is still in play:
Where would I have gone to learn this? The release notes are
simply a cut list of changes. Is there a resource which summarizes
the types of errors one is likely to see when porting a Flex 2 app
to Flex 3, along with the most-likely changes as causes? When CFMX
was first released, there was a helpful checklist of tags and
syntax to help you audit your CF5 for the upgrade. Has one of your
gurus blogged something like this for FX3 and I just can't find it?

Generating Webservice using HTTPS in XI.

Hi Experts,
I have generated webservice in XI using http , and i have tested using infopath soap client, its working fine. I have generated webservice in XI using htpps using the same scenario, when i am testing using infopath as soap client and tested, its giving error, request is not hitting the XI system at all. do i need to configure any certificate in infopath or in XI server, please can anyone advice. i have configured HPPTS without client authentication in SOAP adapter.
Thanks,
Dhanush

Hi Experts,
I am not able to get exact answer after reading the sap.help.com, sap notes.
My scenario is RFC < ---> SOAP ( webservice) , i have generated webservice with the HTTPS and secured port of XI, When i copy and past in IE browser, its showing status is OK, but request is not hitting the XI system. what are things to be taken care at soap client and XI server side, do i need to install any certificats at client side or server side. please advice me.
Thanks,
Siva

Problem generating webservices

Hello Experts,
My scenario is SOAP-->IDOC.As the customer is placing std ORDERS idoc structure as SOAP input, I used std ORDERS structure as target and source structure and did a 1-1 mapping.
I tried to generate webservice for sender SOAP channel.
Tools>Define Webservices>I gave the sender soap URL and navigated to the next screen to input the ORDERS message interface but I didn't see ORDERS in the list when I clicked F4.I'm not able to see my SWC at all.
I did SXI_CACHE cache refresh.But no use.
My design objects and configuration objects are active.
Please advise.
Shanthi.

Hi,
Thanks for your answers.
I created the sender message interface and was able to generate Webservice.
But now, when I tried to test the scenario with Altova XML spy, I got the following error.
com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_BE_NOT_SUPP.
Do I need to create receiver message interface as well?
Can somebody help me to solve this.
Shanthi.

Weblogic generated webservice WSI compliant?

Hi,
As a basic profile/WSI-unaware developer I have been asked to ensure that the webservice I am about to develop using weblogic servicegen is WSI compliant.
Thus I have downloaded the official WSI compliance test tool from www.ws-i.org and tried to to run it my newly generated webservice.
The WSI test tool complains
"Element 'soap:binding' must have no character or element information item [children]"
Thus I have tried to change the generated construct
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
to the (I think) equivalent
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
- which causes the test tool to succeed.
Am I rigth considering this to be an error in the WSI test tool?
Next the test fails on a return type Attribute[], which is wsdl'ed as an unbounded ArrayOfAttribute. I believe the error is that the Array is unbounded (no minoccurs/maxoccurs). Is there any way to specify array boundaries to the servicegen task?
Regards
Peter Buus

What error are you getting in your client? The WSDLs are equivalent, one just uses annonymous complexTypes and the other doesn't.

How to generate Webservices.xml using tool in Sun One App Server?

How to generate Webservices.xml using tool in Sun One App Server?

Hi,
The build.xml file should be in a directory from where
you are running the asant command.
To resolve the common.xml file not found error,
open your build.xml and check from which location the common.xml file is incuded.
In the sample application it is four directories above
the directory where build.xml is located.
You can copy the common.xml in the current directory and then change the following in your build.xml
<!ENTITY include SYSTEM "../../../../common.xml">
to <!ENTITY include SYSTEM "common.xml">
Hope this helps.
Get back in case you have more issues

How does servicegen choose EJBs to generate webservices?

I'd like to know how servicegen Ant task chooses the EJBs to generate webservice operations from. In one of my sample applications the ejbgen Ant task (com.bea.wls.ejbgen.ant.EJBGenAntTask) generates stateless session beans. Servicegen then generates webservice operations for each of the public methods defined in the stateless session beans.
If a similar session bean is generated using XDoclet (xdoclet.modules.ejb.EjbDocletTask) instead of "ejbgen", servicegen does not find any operation to create webservices from! The <operations>-Element in the generated web-services.xml is empty (see error message below).
Are there any naming conventions a generator of EJB-Code should follow if the generated JAR file is used as input for servicegen afterwards?
<servicegen
<service
ejbJar="${build}/${ejb_jar_file}"
>
</service>
</servicegen>
weblogic.webservice.dd.DDProcessingException: There must be at least one <operation> element in <operations> (Line 14, Column 8)
at weblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:1000)
at weblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:986)
at weblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:497)
at weblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:310)
at weblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:298)
at weblogic.webservice.dd.DDLoader.load(DDLoader.java:276)
at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:86)
at weblogic.webservice.tools.build.internal.WSDLGenImpl.getWebServiceMBean(WSDLGenImpl.java:194)
at weblogic.webservice.tools.build.internal.WSDLGenImpl.run(WSDLGenImpl.java:133)
at weblogic.webservice.tools.build.internal.ClientGenImpl.doClientGenFromEAR(ClientGenImpl.java:438)
at weblogic.webservice.tools.build.internal.ClientGenImpl.run(ClientGenImpl.java:345)
at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.generateClient(ServiceGenTask.java:597)
at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:195)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:385)
at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:136)

Hi lerppu
I got same error messages. could you please post how you have solved this problem. i'm a student and is pretty new to j2ee projects. you help would be appreciated.
thanks in advance.

BI Publisher - PO_DISPATCH Error generating report output

Hi everyone,
Sorry for my bad english... having said that...
I need to modify the Purchase Order print. First, I wanted to see the standard version to get an idea of how much different it was. Well, I don't know because it doesn't work.
Error:
Error generating report output: (235,2309)
Error occurred during the process of generating the output file from template file, XML data file, and translation XLIFF file.
I know there are several topics on the web, but all of them are about new or custom reports, this is a standard one. When I preview the report on the report definition it works fine, so I assume there's a problem with the XML file generated. When I preview the report specifying an alternative XML I get the same error. The XML file I choose was the one generated by PeopleSoft when trying to view the printable version of the PO online.
So, I start cutting portions of the XML File. I started leaving only de Header Data and it works OK, when I add the Lines it failed. I add the Line Fields one by one to detect what was the problem... And finally it failed when I add AMT_LINE_MAX. Why? No idea, is it because its value is '0,000' instead of '0.000'? I don't think that should be the problem since there are other numeric fields on the header, all with ',' as a decimal separator...
Am I missing some configuration?
Thanks in advance.
Regards,
Veronica.

Have a look at the following doc:
"Error generating report output. (235,2309)" When Running the "PO XMLP Dispatch" XML Publisher Report (PO_DISPATCH) for a Purchase Order with a Ship To Location with Special Characters in the Address [ID 1299876.1]
https://support.oracle.com/epmos/faces/DocContentDisplay?id=1299876.1
Stating this happens for example when there is a location with special characters.

Error generating report job with the task name 'FSRM_Report_Task

Since this morning we have been having a problem with FSRM on Windows Server 2008 R2, it is no longer running storage reports (both scheduled and on-demand).
We get the following in the event logs:
Log Name: Application
Source: SRMREPORTS
Date: 09/06/2014 08:09:55
Event ID: 752
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: FILESERVER2.curriculum.riddlesdown.local
Description:
Error generating report job with the task name 'FSRM_Report_Task{3add1760-4e79-4141-baba-cb53391bef3e}'.
Context:
- Exception encountered = Invalid argument: StorageType = '101'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="SRMREPORTS" />
<EventID Qualifiers="0">752</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-06-09T07:09:55.000000000Z" />
<EventRecordID>42920</EventRecordID>
<Channel>Application</Channel>
<Computer>FILESERVER2.curriculum.riddlesdown.local</Computer>
<Security />
</System>
<EventData>
<Data>Error generating report job with the task name 'FSRM_Report_Task{3add1760-4e79-4141-baba-cb53391bef3e}'.
Context:
- Exception encountered = Invalid argument: StorageType = '101'
</Data>
</EventData>
</Event>
We have uninstalled and reinstalled the FSRM role service but are still having the same problem.
Anybody have any ideas?

Hi,
From the error message, it failed because of "invalid argument: storagetype = '101' ".
101 means the storage type is "system" + "cache". Is there any change on your storage before the issue occurs? For example whether the source storage is changed?
FsrmStorageModuleType enumeration
http://msdn.microsoft.com/en-us/library/dd392346(v=vs.85).aspx
If you have any feedback on our support, please send to [email protected]

JDev generated webservices encodes XML output from PL/SQL procedure

I have a PL/SQL packaged procedure which takes some input parameters and produces one output parameter. The output parameter is of type CLOB and after the procedure has run, it contains a big piece of XML data.
Using JDeveloper 10.1.3.1, I've published this packaged procedure as a webservice. The generated webservice is fine and works, except for one tiny little issue: the XML that is taken from the output parameter is encoded.
Here is an example of the SOAP message that the webservice returns:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://gbv0300u/GBV0300U.wsdl/types/"><env:Body><ns0:gbv0300uResponse
Element><ns0:result><ns0:obvglijstOut> & gt;type>GBV0001& gt ;/type& lt;
& gt;diensten& lt;
& gt;dienst>some value& gt;/dienst& lt;
& gt;/diensten& lt;
</ns0:obvglijstOut></ns0:result></ns0:gbv0300uResponseElement></env:Body></env:Envelope>
(I've manually added an extra space between the & and lt; or gt; to make sure a browser will not translate it into a < or >!)
The contents of the <ns0:obvglijstOut> element are filled with the output parameter from the PL/SQL package.
How can I change the generated webservice, so the output from the PL/SQL package is used as is instead of being encoded?

Update: I've tested a bit more by adding some output statements to the java code that JDeveloper generated. I'm now 100% sure the PL/SQL code gives the XML data correctly to the webservice.
At this moment my guess is that somewhere in the WSDL definition there is something that enables the encoding of the data. But I'm not sure.
Any help is greatly appreciated.

Error generating WebServices thro' Axis

Similar Messages

Maybe you are looking for