Generic WSDL element name

Hi Gurus,
For normal web services integration what kind of WSDL file should we use? custom or generic?
If we using generic how to check the element name or the display name?
Please advice.
Thanks in advance.

Hi, Would suggest custom, unless you like to build something that is generic which can work across multiple instances of CRMOD or goes across all fields / objects etc. Otherwise it may not worth the effort of managing the integration tags mapping related activities
-- Venky CRMIT

Similar Messages

Oracle OnDemand Generic WSDL Custom Element

Hi,
I have added a new field to the Activity object.
I am trying to set value and get values for this newly created field using web service 2.0.
If I download the Custom WSDL, I could see the tag name of the newly created field. But this does not appear in the Generic WSDL 2.0.
Your document says,
"For Generic WSDL files, custom fields are based on generic XML
tags: CustomNumber0, CustomCurrency0, and so on. Using these placeholders, together with
the Mapping Service or Field Management API allows applications to map the generic XML tags
to the field names that your company uses."
But it is not clear and I am unable to map the newly created fields using the mapping service.
Could you please help me on this?
Thanks,
Baskar.S

Hi, Would suggest custom, unless you like to build something that is generic which can work across multiple instances of CRMOD or goes across all fields / objects etc. Otherwise it may not worth the effort of managing the integration tags mapping related activities
-- Venky CRMIT

Generic WSDL vs Specific WSDL

Hi All,
Can you list down the differences between Generic WSDL vs Specific WSDL?
When do we need to prefer Generic against Specific or vice versa?
Also, following are my concerns on Generic WSDL:
If my front end application developed is using Generic wsdl and lets say there are changes to my rule base like adding/deleting entities in data model, or adding/deleting attributes or changing attributes text or changes to public names, then does the client stubs need to regenerate because of the changes to rule base?
Regards,
Mohan

Generic WSDL = XML structure does not change when policy model changes (i.e. new entity in model will mean a new data value is supported, but no change to WSDL)
Specific WSDL = XML structure changes with policy model (i.e. new entity in policy model means new XML element in NEW WSDL)
General Pros / Cons:
- Generic WSDL: WSDL doesn't change, stubs don't change, No useful compile time checking, validation can not occur because the XML elements are fixed regardless of policy model changes.
- Specific WSDL - better compile time checking, can do validation of XML against WSDL, but need to regenerate stubs for policy model changes.
In both cases, you still need to change the code to handle any changes to the policy model that impact the inbound or outbound data "contract". In the generic case, you would be changing which values should be put into the XML or should be expected from the XML (e.g. ID or name attribute values). In the specific WSDL case, you will be dealing with new or deleted XML elements, so generate stubs again and see the new / deleted stubs. Personally, I would use the specific WSDL approach because you will get more compile time checking following a policy model change and regenerating stubs.

Unexpected element name: expected error while invoking external web service

Hi,
In JDeveloper when I invoke external web service call, I am getting following exception
"unexpected element name: expected=..."
But the same application works fine in .NET. Can someone help me as to why I am getting the exception only in JDeveloper and how to fix this exception.
Thanks.

Hi,
Without more information, it will be hard to help, and tell you what could be teh issue.
Usually, this kind of error occurs when the payload and the WSDL schema are out of sync, for example if the order of the element on the wire do not match the order in a sequence declaration, you may get this error.
In such case, .NET handle the XML as if it was a 'all' -- no specific order -- and deserialize the message properly.
Hope this helps,
-eric

Unexpected element name - confusion of types in client

I have a web service definition that performs four operations:
- String getTitle(long) - returns a title for a single asset
- StringArrayType) getTitles(LongArrayType) - returns an ordered list of titles matching input list
- AssetSummaryType getSummary(long) - Returns a complex type, summary information of an asset
- AssetSummaryArrayType getSummaries(LongArrayType) - Returns an array of complex types
Based on the WSDL (included at the bottom of this posting) I then generate the service
endpoint using wscompile and -f:wsi option (JDK 1.4.2-05 and JWSDP-1.4).
This is built into a raw war file and then cooked using wsdeploy.
On the client side I create stubs using wscompile and -f:wsi and compile
the resultant code. My client invokes each of the operations in turn, having been
provided the relevant 'longs' as input.
The service is deployed in JBoss-3.2.2 and the client is then executed from a separate JVM.
I then see the following client error:
java.rmi.RemoteException: Runtime exception; nested exception is:
unexpected element name: expected={http://example.com/myAssetWebSvc}Str
ingElement, actual={http://example.com/MyAssetWebSvc}AssetSummaryElement
at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(
StreamingSender.java:318)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:300
at example.com.wsclient.asset.AssetService_Stub.getTitle(AssetService_St
ub.java:175)
at example.com.wsclient.asset.AssetClient.testAssetTitleRetrieval(AssetC
lient.java:82)
at example.com.wsclient.asset.AssetClient.main(AssetClient.java:51)
Caused by: unexpected element name: expected={http://example.com/MyAssetWebSvc}
StringElement, actual={http://example.com/MyAssetWebSvc}AssetSummaryElement
at com.sun.xml.rpc.encoding.literal.LiteralSimpleTypeSerializer.deserial
ize(LiteralSimpleTypeSerializer.java:106)
at example.com.wsclient.asset.AssetService_Stub._deserialize_getTitle(As
setService_Stub.java:318)
at example.com.wsclient.asset.AssetService_Stub._readFirstBodyElement(As
setService_Stub.java:276)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:215
... 3 more
If I deploy the same service with only the first two operations defined within wsdl,
the error is not seen.
I have also tried compilation on JWSDP 1.3 and JDK 1.4.1-03 and in this case the same error
occurs but the other way around. The two 'title' operations work but the summary
operations fail with the actual element encountered being a StringElement or StringArrayElement
and the expected an AssetSummaryElement or AssetSummaryArrayElement.
Further, if I change the name of the StringElement to for example 'MyStringElement', this is
reported as the actual - i.e. there is no confusion with a standard type at play here.
I also use handlers, one on the server side to inspect security information and one on the
client to insert relevant details and look for returned errors within the header.
Is this a known problem within JWSDP 1.3 and/or 1.4? Are there any workarounds.
My wsdl is provided below along with the wscompile options and the matching configuration
files used.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="MyAssetService" targetNamespace="http://example.com/MyAssetWebSvc"
     xmlns:tns="http://example.com/MyAssetWebSvc"
     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<wsdl:types>
<xsd:schema targetNamespace="http://example.com/MyAssetWebSvc"
          xmlns:tns="http://example.com/MyAssetWebSvc"
          xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="AssetSummaryType">
<xsd:all>
<xsd:element name="createdBy" type="xsd:string" />
<xsd:element name="createdDate" type="xsd:dateTime" />
<xsd:element name="description" type="xsd:string" />
<xsd:element name="fileSize" type="xsd:long" />
<xsd:element name="id" type="xsd:long" />
<xsd:element name="modifiedBy" type="xsd:string" />
<xsd:element name="modifiedDate" type="xsd:dateTime" />
<xsd:element name="organisation" type="xsd:string" />
<xsd:element name="owner" type="xsd:string" />
<xsd:element name="title" type="xsd:string" />
<xsd:element name="type" type="xsd:string" />
<xsd:element name="version" type="xsd:long" />
</xsd:all>
</xsd:complexType>
<xsd:complexType name="ExceptionType">
<xsd:all>
<xsd:element name="rootCause" type="xsd:string" nillable="true" />
</xsd:all>
</xsd:complexType>
<xsd:complexType name="LongArrayType">
     <xsd:sequence>
          <xsd:element name="LongItem" type="xsd:long" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
     </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="AssetSummaryArrayType">
     <xsd:sequence>
          <xsd:element name="AssetSummaryItem" type="tns:AssetSummaryType" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
     </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="StringArrayType">
     <xsd:sequence>
          <xsd:element name="StringItem" type="xsd:string" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
     </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CredentialsType">
<xsd:all>
<xsd:element name="principal" type="xsd:string" />
<xsd:element name="password" type="xsd:string" />
</xsd:all>
</xsd:complexType>
     <xsd:element name="LongElement" type="xsd:long"/>
<xsd:element name="StringElement" type="xsd:string"/>
<xsd:element name="LongArrayElement" type="tns:LongArrayType"/>
<xsd:element name="StringArrayElement" type="tns:StringArrayType"/>
<xsd:element name="AssetSummaryElement" type="tns:AssetSummaryType"/>
<xsd:element name="AssetSummaryArrayElement" type="tns:AssetSummaryArrayType"/>
     <xsd:element name="CredentialsElement" type="tns:CredentialsType"/>
     <xsd:element name="ExceptionElement" type="tns:ExceptionType"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="getSummaryMessage">
<wsdl:part name="resourceId" element="tns:LongElement" />
</wsdl:message>
<wsdl:message name="getSummaryResponse">
<wsdl:part name="assetSummary" element="tns:AssetSummaryElement" />
</wsdl:message>
<wsdl:message name="assetException">
<wsdl:part name="exception" element="tns:ExceptionElement" />
</wsdl:message>
<wsdl:message name="getTitle">
<wsdl:part name="resourceId" element="tns:LongElement" />
</wsdl:message>
<wsdl:message name="getTitleResponse">
<wsdl:part name="assetTitle" element="tns:StringElement" />
</wsdl:message>
<wsdl:message name="getSummaries">
<wsdl:part name="resourceIdList" element="tns:LongArrayElement" />
</wsdl:message>
<wsdl:message name="getSummariesResponse">
<wsdl:part name="assetSummaryList" element="tns:AssetSummaryArrayElement" />
</wsdl:message>
<wsdl:message name="getTitles">
<wsdl:part name="resourceIdList" element="tns:LongArrayElement" />
</wsdl:message>
<wsdl:message name="getTitlesResponse">
<wsdl:part name="assetTitleList" element="tns:StringArrayElement" />
</wsdl:message>
<wsdl:message name="securityHeader">
<wsdl:part name="credentials" element="tns:CredentialsElement" />
</wsdl:message>
<wsdl:portType name="AssetService">
<wsdl:operation name="getSummary" parameterOrder="resourceId">
<wsdl:input message="tns:getSummaryMessage" />
<wsdl:output message="tns:getSummaryResponse" />
<wsdl:fault name="AssetException" message="tns:assetException" />
</wsdl:operation>
<wsdl:operation name="getTitle" parameterOrder="resourceId">
<wsdl:input message="tns:getTitle" />
<wsdl:output message="tns:getTitleResponse" />
<wsdl:fault name="AssetException" message="tns:assetException" />
</wsdl:operation>
<wsdl:operation name="getSummaries" parameterOrder="resourceIdList">
<wsdl:input message="tns:getSummaries" />
<wsdl:output message="tns:getSummariesResponse" />
<wsdl:fault name="AssetException" message="tns:assetException" />
</wsdl:operation>
<wsdl:operation name="getTitles" parameterOrder="resourceIdList">
<wsdl:input message="tns:getTitles" />
<wsdl:output message="tns:getTitlesResponse" />
<wsdl:fault name="AssetException" message="tns:assetException" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AssetServiceBinding" type="tns:AssetService">
<wsdl:operation name="getSummary">
<wsdl:input>
<soap:header required="true" message="tns:securityHeader" part="credentials" use="literal" actor="security"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="AssetException">
<soap:fault name="AssetException" use="literal"/>
</wsdl:fault>
<soap:operation soapAction="" />
</wsdl:operation>
<wsdl:operation name="getTitle">
<wsdl:input>
<soap:header required="true" message="tns:securityHeader" part="credentials" use="literal"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="AssetException">
<soap:fault name="AssetException" use="literal"/>
</wsdl:fault>
<soap:operation soapAction="" />
</wsdl:operation>
<wsdl:operation name="getSummaries">
<wsdl:input>
<soap:header required="true" message="tns:securityHeader" part="credentials" use="literal"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="AssetException">
<soap:fault name="AssetException" use="literal"/>
</wsdl:fault>
<soap:operation soapAction="" />
</wsdl:operation>
<wsdl:operation name="getTitles">
<wsdl:input>
<soap:header required="true" message="tns:securityHeader" part="credentials" use="literal"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="AssetException">
<soap:fault name="AssetException" use="literal"/>
</wsdl:fault>
<soap:operation soapAction="" />
</wsdl:operation>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
</wsdl:binding>
<wsdl:service name="MyAssetService">
<wsdl:port name="AssetServicePort" binding="tns:AssetServiceBinding">
<soap:address location="http://localhost:9090/MyAssetWebSvc/asset" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Here is the wscompile for the server - this is within an ant script that substitutes the variables specified:
wscompile -keep -d ${path.classes} -s ${src.autojava} -import -model model.gz -f:wsi -f:documentliteral server-config.xml
and this is the server config:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<wsdl location="file:///C:temp/MyAssetService_wsi.wsdl" packageName="example.com.wsserver.asset.wrapper">
<handlerChains>
<chain runAt="server">
<handler className="example.com.wsserver.security.SecurityServerHandler">
<property name="name" value="SecurityServerHandler"/>
</handler>
</chain>
</handlerChains>
</wsdl>
</configuration>
On the client side, here is the wscompile, again with ant variable substitution:
wscompile -gen:client -keep -d ${path.build.wsclient.class} -s ${path.build.wsclient.autojava} -classpath ${path.build.wsclient.class} -f:wsi -f:documentliteral client-config.xml
And here is the client config:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<wsdl location="file:///C:/temp/MyAssetService_wsi.wsdl" packageName="example.com.wsclient.asset">
<handlerChains>
<chain runAt="client">
<handler className="example.com.wsclient.security.SecurityClientHandler">
<property name="name" value="SecurityClientHandler"/>
</handler>
</chain>
</handlerChains>
</wsdl>
</configuration>
Note that I generate slightly different packages on client and server side. The server includes a 'wrapper' path on the package name - purely because the
generated code wrappers an existent api that I am making available as a web service. This is not needed to be seen
on the client side - i.e. the service appears as is without the wrapper.
I have tried omitting the documentliteral from the wscompiles and this seems to have no effect.
Any help gratefully received.
Best regards
Lawrence

Thanks for the prompting. I was convinced that the error was occurring client side as I could see no activity on the server. However having captured the soap request and responses its evident that this is not the case (which I'm a little confused on based on my original tests, but the error makes more sense in this context).
The request is below:
<env:Envelope xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://example.com/myAssetWebSvc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
<ns1:mmsSecurity env:actor="security" env:mustUnderstand="1" xmlns:ns1="http://example.com/myAssetWebSvc">
<principal>example.user</principal>
<password>mypassword</password>
</ns1:mmsSecurity>
</env:Header>
<env:Body>
<ns0:LongElement>166333</ns0:LongElement>
</env:Body>
</env:Envelope>
I can see from the body that the signature is not unique - its the same as that of the Summary operation. In this case, the server side is performing the summary (rather than the title that I had intended) and returning that response. This gives rise to the deserialisation error on the client side for the response.
Presumably I need to move to the wrapped document literal style so that the request is uniquely identified on the server side.
To me this was not an obvious gotcha, Could the parser (wscompile) be enhanced to trap identical request message definitions within a single service/endpoint definition (i.e. WSDL)? If so where should I post the request?

Autotyping not preserving XML element names for use in Web service

I am trying to generate a web service from an existing WSDL (ServiceOrderingContract.wsdl,
attached). The WSDL contains as a message part with an element dsl_FirmOrderProvideRequest.
Autotyping produces a corresponding class DSLFirmOrderProvideRequest. I use the
output of autotyping to implement a web service corresponding to this WSDL. I
then deploy this web service. The WSDL of the DEPLOYED webservice now has a message
part with an element DSLFirmOrderProvideRequest, per the autotype, but in mismatch
with the source WSDL. Of course, the clientgen from the source WSDL wont work
against the latter deployed WSDL.
Something is changing dsl_ to DSL in the autotyping process. Is this a bug? Or
am I doing something wrong? Is there any option in autotype task to preserve element
names?
Thanks a lot.

Hello,
Take a look at the docs on roundtripping generated data types [1]
Regards,
Bruce
[1]
http://edocs.bea.com/wls/docs81/webserv/assemble.html#1074725
Suteertha wrote:
>
This is in basic WLS 8.1 SP2.

Unexpected element name: expected WHEN INVOKING A WEB SERVICE

I am pretty new to Web Services and need some helping in resolving the following error. I created following two classes and published one of the method savePerson. When I tried to invoke the webservice through my browser passing the following:
<ns1:savePersonElement xmlns:ns1="http://mypackage17/Person.wsdl/types">
<ns1:sex>simpleType value</ns1:sex>
<ns1:human>
<ns2:last xmlns:ns2="http://tempuri.org">simpleType value</ns2:last>
<ns3:first xmlns:ns3="http://tempuri.org">simpleType value</ns3:first>
</ns1:human>
</ns1:savePersonElement>
I get the following error:
<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://mypackage17/Person.wsdl/types">
<env:Body>
<env:Fault>
<faultcode>env:Client</faultcode>
<faultstring>caught exception while handling request: unexpected element name: expected={http://mypackage17/Person.wsdl/types}name, actual={http://mypackage17/Person.wsdl/types}sex</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
But passing the following works fine as have passed all the parameters data:
<ns1:savePersonElement xmlns:ns1="http://mypackage17/Person.wsdl/types">
<ns1:name>simpleType value</ns1:name>
<ns1:sex>simpleType value</ns1:sex>
<ns1:human>
<ns2:last xmlns:ns2="http://tempuri.org">simpleType value</ns2:last>
<ns3:first xmlns:ns3="http://tempuri.org">simpleType value</ns3:first>
</ns1:human>
</ns1:savePersonElement>
Here is the code I have for the webservice:
package mypackage17;
*@oracle.ws.WebService name = "MyWebService2", serviceName = "MyWebService2", description = "", targetNamespace = "http://tempuri.org", schemaTargetNamespace = "http://mypackage17/Person.wsdl/types", endpointInterface = "mypackage17.MyWebService1SEI"
*@oracle.ws.SOAPBinding style = "DOCUMENT", use = "LITERAL", documentWrapped = "true", bindingName = "MyWebService1SoapHttp", portName = "MyWebService1Port"
public class Person extends Human
private String name;
private String sex;
public Person(){}
public void setName(String name)
this.name = name;
public void setSex(String sex)
this.sex = sex;
public String getName()
return this.name;
public String getSex()
return this.sex;
*@oracle.ws.DocumentWrapper requestType = "savePerson", requestElement = "savePersonElement", requestPart = "parameters", responseType = "savePersonResponse", responseElement = "savePersonResponseElement", responsePart = "parameters"
*@oracle.ws.WebMethod operationName = "savePerson", description = "", oneway = "false", documentWrapped = "true", inputMessage = "MyWebService1SEI_savePerson", outputMessage = "MyWebService1SEI_savePersonResponse", responsePart = "result"
*@oracle.ws.ParamPart position = "0", partName = "name", mode = "IN", soapHeader = "false"
*@oracle.ws.ParamPart position = "1", partName = "sex", mode = "IN", soapHeader = "false"
*@oracle.ws.ParamPart position = "2", partName = "human", mode = "IN", soapHeader = "false"
public void savePerson(String name, String sex, Human[] human)
System.out.println("Name: " + name);
System.out.println("Sex: " + sex);
System.out.println(human.length);
System.out.println("1 First: " + human[0].getFirst());
System.out.println("1 Last: " + human[0].getLast());
System.out.println("2 First: " + human[1].getFirst());
System.out.println("2 Last: " + human[1].getLast());
/****** THE OTHER CLASS ********/
package mypackage17;
public class Human
private String first;
private String last;
public Human(){}
public void setFirst(String first)
this.first = first;
public void setLast(String last)
this.last = last;
public String getFirst()
return this.first;
public String getLast()
return this.last;
Here is the WSDL generated using JDeveloper 10.1.3:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions
name="MyWebService2"
targetNamespace="http://tempuri.org"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://tempuri.org"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:ns1="http://mypackage17/Person.wsdl/types"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://tempuri.org" elementFormDefault="qualified"
xmlns:tns="http://tempuri.org" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
<import namespace="http://mypackage17/Person.wsdl/types"/>
<complexType name="Human">
<sequence>
<element name="last" type="string" nillable="true"/>
<element name="first" type="string" nillable="true"/>
</sequence>
</complexType>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://mypackage17/Person.wsdl/types"
elementFormDefault="qualified" xmlns:tns="http://mypackage17/Person.wsdl/types"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://tempuri.org">
<import namespace="http://tempuri.org"/>
<complexType name="savePerson">
<sequence>
<element name="name" type="string" nillable="true"/>
<element name="sex" type="string" nillable="true"/>
<element name="human" type="ns1:Human" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="savePersonResponse">
<sequence/>
</complexType>
<element name="savePersonElement" type="tns:savePerson"/>
<element name="savePersonResponseElement" type="tns:savePersonResponse"/>
</schema>
</types>
<message name="MyWebService1SEI_savePerson">
<part name="parameters" element="ns1:savePersonElement"/>
</message>
<message name="MyWebService1SEI_savePersonResponse">
<part name="parameters" element="ns1:savePersonResponseElement"/>
</message>
<portType name="MyWebService2">
<operation name="savePerson">
<input message="tns:MyWebService1SEI_savePerson"/>
<output message="tns:MyWebService1SEI_savePersonResponse"/>
</operation>
</portType>
<binding name="MyWebService1SoapHttp" type="tns:MyWebService2">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="savePerson">
<soap:operation soapAction="http://tempuri.org:savePerson"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
</binding>
<service name="MyWebService2">
<port name="MyWebService1Port" binding="tns:MyWebService1SoapHttp">
<soap:address location="http://192.168.2.101:8988/JavaWebService/MyWebService2"/>
</port>
</service>
</definitions>
Can someone tell what am I doing wrong. As it looks like I have to pass all the parameters for the method that is published but what if some are missing basically I want to keep all the parameters optional. How can I make the service to return the same what is passed when invoked. Any help is appreciated. I am using JDeveloper 10.1.3.

To make the service return "whatever is passed", you have to take a step back and realize that there is a little understanding of XML Schema required.
When using a complexType, which is defined as a sequence, then you are implying an ordered sequence of elements. Default value for the 'minOccurs' attribute is 1. It's also important to understand that there is a difference between minOccurs=0 and nillable="true".
nillable="true" just means that the name element can carry a null value. If you want the name element to be optional, then you must use the minOccurs=0 and keep the maxOccurs to it's default value of 1. Using an array is just a bad work around. This is for deserialization (XML to JAVA).
The second part of you problem is on the serialization (or JAVA to XML). When you have a JAVA Bean, there is no way to make the difference between a member's value being null or not set, so it's impossible to decide if you need to send back a nul (xsi:nil="true"), an empty element <ns1:name/> or nothing.
That said, if you do want to go the XML route, you can use the dataBinding="false" flag in the different WSA command. Instead of converting XML into JAVA, you will have SOAPElement parameters, where you can do all you want (see WS user's guide [1] for details - chapter 16). Note that you have to make sure that the WSDL (your contract) reflect what you are doing on the wire (format of your messages), so that you do not geopardize your interoperability with other toolkit.
Note that this only applies to literal message formats (use attribute in WSDL), which is your case.
Hope this helps,
Eric
[1] http://download-west.oracle.com/otn_hosted_doc/ias/preview/web.1013/b14434.pdf

Error message : unexpected element name:

Hi people,
I'm trying to consume an external web service and encountered the following error when trying to run the service in JDeveloper. I'm new to both java and WSDL. Please lend a helping hand. Thanks for your help in advance.
Error:
C:\JDeveloper\jdk\bin\javaw.exe -client -classpath C:\E900\DEMO\Java\classes;C:\JDeveloper\webservices\lib\jaxrpc-api.jar;C:\JDeveloper\webservices\lib\wsclient.jar;C:\JDeveloper\webservices\lib\wsserver.jar;C:\JDeveloper\webservices\lib\wssecurity.jar;C:\JDeveloper\webservices\lib\wsdl.jar;C:\JDeveloper\webservices\lib\orasaaj.jar;C:\JDeveloper\webservices\lib\saaj-api.jar;C:\JDeveloper\webservices\lib\orawsdl.jar;C:\JDeveloper\webservices\lib\orawsrm.jar;C:\JDeveloper\webservices\lib\jaxr_api.jar;C:\JDeveloper\webservices\lib\orajaxr.jar;C:\JDeveloper\webservices\lib\relaxngDatatype.jar;C:\JDeveloper\webservices\lib\jaxb-impl.jar;C:\JDeveloper\webservices\lib\jaxb-libs.jar;C:\JDeveloper\webservices\lib\xsdlib.jar;C:\JDeveloper\webservices\lib\mdds.jar;C:\JDeveloper\jlib\jaxen.jar;C:\JDeveloper\jlib\oraclepki.jar;C:\JDeveloper\jlib\ojpse.jar;C:\JDeveloper\jlib\osdt_core.jar;C:\JDeveloper\jlib\osdt_cert.jar;C:\JDeveloper\jlib\osdt_xmlsec.jar;C:\JDeveloper\jlib\osdt_wss.jar;C:\JDeveloper\jlib\osdt_saml.jar;C:\JDeveloper\jlib\repository.jar;C:\JDeveloper\jlib\ojmisc.jar;C:\JDeveloper\j2ee\home\lib\http_client.jar;C:\JDeveloper\j2ee\home\jazncore.jar;C:\JDeveloper\j2ee\home\oc4jclient.jar;C:\JDeveloper\rdbms\jlib\xdb.jar;C:\JDeveloper\diagnostics\lib\ojdl2.jar;C:\E900\DEMO\ini\sbf;C:\E900\System\Classes\Base_JAR.jar;C:\E900\System\Classes\BizLogicContainer_JAR.jar;C:\E900\System\Classes\BusinessLogicServices_JAR.jar;C:\E900\System\Classes\Connector.jar;C:\E900\System\Classes\EventProcessor_JAR.jar;C:\E900\System\Classes\Generator_JAR.jar;C:\E900\System\Classes\JdbjBase_JAR.jar;C:\E900\System\Classes\JdbjInterfaces_JAR.jar;C:\E900\System\Classes\JdeNet_JAR.jar;C:\E900\System\Classes\Maf2Base_JAR.jar;C:\E900\System\Classes\mafsecurity.jar;C:\E900\System\Classes\Metadata.jar;C:\E900\System\Classes\MetadataInterface.jar;C:\E900\System\Classes\PMApi_JAR.jar;C:\E900\System\Classes\SBFFoundation_JAR.jar;C:\E900\System\Classes\Spec_JAR.jar;C:\E900\System\Classes\System_JAR.jar;C:\E900\System\Classes\SystemInterfaces_JAR.jar;C:\E900\System\Classes\castor.jar;C:\E900\System\Classes\log4j.jar;C:\E900\System\Classes\xerces.jar;C:\E900\System\Classes\xml-apis.jar;C:\E900\System\Classes\Rijndael.jar;C:\E900\System\Classes\ManagementAgent_JAR.jar;C:\E900\System\Classes\commons-logging.jar;C:\E900\System\Classes\commons-codec-1.3.jar;C:\E900\System\Classes\commons-httpclient-3.0.jar;C:\E900\System\Classes\jmxremote.jar;C:\E900\System\Classes\jmxremote_optional.jar;C:\E900\System\Classes\jmxri.jar;C:\E900\System\Classes\rmissl.jar;C:\E900\misc\classes12.jar;C:\E900\misc\mssqlserver.jar;C:\E900\misc\msutil.jar;C:\E900\misc\msbase.jar;C:\E900\misc\db2java.zip;C:\E900\misc\jt400.jar;C:\E900\misc\sqljdbc.jar;C:\E900\misc\ojdbc5.jar;C:\JDeveloper\lib\xmlparserv2.jar;C:\JDeveloper\lib\xml.jar oracle.e1.bssv.J5500002.proxy.CrmCustomerServiceClient
calling http://XXX.XX.XXX.XX:8080/PSIGW/HttpListeningConnector
*unexpected element name: expected={http://xxxx.xxxx.com}EnquiryByLegacyIdResponse, actual=EnquiryByLegacyIdResponse*
at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(LiteralObjectSerializerBase.java:231)
at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:159)
at oracle.e1.bssv.J5500002.proxy.runtime.CrmCustomerServiceSoapBinding_Stub._deserialize_EnquiryByLegacyId(CrmCustomerServiceSoapBinding_Stub.java:348)
at oracle.e1.bssv.J5500002.proxy.runtime.CrmCustomerServiceSoapBinding_Stub._readFirstBodyElement(CrmCustomerServiceSoapBinding_Stub.java:283)
at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:335)
at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:114)
at oracle.e1.bssv.J5500002.proxy.runtime.CrmCustomerServiceSoapBinding_Stub.enquiryByLegacyId(CrmCustomerServiceSoapBinding_Stub.java:238)
at oracle.e1.bssv.J5500002.proxy.CrmCustomerServiceClient.enquiryByLegacyId(CrmCustomerServiceClient.java:55)
at oracle.e1.bssv.J5500002.proxy.CrmCustomerServiceClient.main(CrmCustomerServiceClient.java:41)
Process exited with exit code 0.
--- the definition for java class "CrmCustomerServiceClient.java" ---_*
package oracle.e1.bssv.J5500002.proxy;
import oracle.webservices.transport.ClientTransport;
import oracle.webservices.OracleStub;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Stub;
public class CrmCustomerServiceClient {
private oracle.e1.bssv.J5500002.proxy.CrmCustomerService _port;
public CrmCustomerServiceClient() throws Exception {
ServiceFactory factory = ServiceFactory.newInstance();
_port = ((oracle.e1.bssv.J5500002.proxy.CrmCustomerServiceService)factory.loadService(oracle.e1.bssv.J5500002.proxy.CrmCustomerServiceService.class)).getCrmCustomerService();
* @param args
public static void main(String[] args) {
try {
oracle.e1.bssv.J5500002.proxy.CrmCustomerServiceClient myPort = new oracle.e1.bssv.J5500002.proxy.CrmCustomerServiceClient();
System.out.println("calling " + myPort.getEndpoint());
// Add your own code here
EnquiryByLegacyId test = new EnquiryByLegacyId ();
test.setSETID("CTN");
test.setCPL_LEGACY_ID("03-135452");
//EnquiryByLegacyIdResponse response = new EnquiryByLegacyIdResponse();
//response = myPort.enquiryByLegacyId(test);
//EnquiryByLegacyIdResponse response = myPort.enquiryByLegacyId(test);
CrmCustomerId cus = new CrmCustomerId();
//cus = response.getEnquiryByLegacyIdReturn();
cus = (myPort.enquiryByLegacyId(test)).getEnquiryByLegacyIdReturn();
System.out.println("Your username is " + cus.getCUST_ID()+cus.getRESPOND_MSG());
} catch (Exception ex) {
ex.printStackTrace();
* delegate all operations to the underlying implementation class.
public EnquiryByLegacyIdResponse enquiryByLegacyId(EnquiryByLegacyId parameters) throws java.rmi.RemoteException {
return _port.enquiryByLegacyId(parameters);
public EnquiryByNationalIdResponse enquiryByNationalId(EnquiryByNationalId parameters) throws java.rmi.RemoteException {
return _port.enquiryByNationalId(parameters);
public EnquiryByNameResponse enquiryByName(EnquiryByName parameters) throws java.rmi.RemoteException {
return _port.enquiryByName(parameters);
public EnquiryByPhoneCellResponse enquiryByPhoneCell(EnquiryByPhoneCell parameters) throws java.rmi.RemoteException {
return _port.enquiryByPhoneCell(parameters);
* used to access the JAX-RPC level APIs
* returns the interface of the port instance
public oracle.e1.bssv.J5500002.proxy.CrmCustomerService getPort() {
return _port;
public String getEndpoint() {
return (String) ((Stub) port).getProperty(Stub.ENDPOINT_ADDRESS_PROPERTY);
public void setEndpoint(String endpoint) {
((Stub) port).setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, endpoint);
public String getPassword() {
return (String) ((Stub) port).getProperty(Stub.PASSWORD_PROPERTY);
public void setPassword(String password) {
((Stub) port).setProperty(Stub.PASSWORD_PROPERTY, password);
public String getUsername() {
return (String) ((Stub) port).getProperty(Stub.USERNAME_PROPERTY);
public void setUsername(String username) {
((Stub) port).setProperty(Stub.USERNAME_PROPERTY, username);
public void setMaintainSession(boolean maintainSession) {
((Stub) port).setProperty(Stub.SESSION_MAINTAIN_PROPERTY, Boolean.valueOf(maintainSession));
public boolean getMaintainSession() {
return ((Boolean) ((Stub) port).getProperty(Stub.SESSION_MAINTAIN_PROPERTY)).booleanValue();
* returns the transport context
public ClientTransport getClientTransport() {
return ((OracleStub) _port).getClientTransport();
--- the definition for java class "EnquiryByLegacyIdResponse.java" ---_*
package oracle.e1.bssv.J5500002.proxy;
public class EnquiryByLegacyIdResponse implements java.io.Serializable {
protected oracle.e1.bssv.J5500002.proxy.CrmCustomerId enquiryByLegacyIdReturn;
public EnquiryByLegacyIdResponse() {
public oracle.e1.bssv.J5500002.proxy.CrmCustomerId getEnquiryByLegacyIdReturn() {
return enquiryByLegacyIdReturn;
public void setEnquiryByLegacyIdReturn(oracle.e1.bssv.J5500002.proxy.CrmCustomerId enquiryByLegacyIdReturn) {
this.enquiryByLegacyIdReturn = enquiryByLegacyIdReturn;
__--- the definition for the WSDL" ---__+
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://xxxx.xxxx.com" xmlns:intf="http://xxxx.xxxx.com" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xxxx.xxxx.com">

<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://xxxx.xxxx.com">
<element name="EnquiryByLegacyId">
<complexType>
<sequence>
<element name="SETID" type="xsd:string" />
<element name="CPL_LEGACY_ID" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="EnquiryByLegacyIdResponse">
<complexType>
<sequence>
<element name="EnquiryByLegacyIdReturn" type="impl:CrmCustomerId"/>
</sequence>
</complexType>
</element>
<complexType name="CrmCustomerId">
<sequence>
<element name="SETID" nillable="false" type="xsd:string"/>
<element name="CPL_LEGACY_ID" nillable="true" type="xsd:string"/>
<element name="CUST_ID" nillable="true" type="xsd:string"/>
<element name="RESPOND_MSG" nillable="false" type="xsd:integer"/>
</sequence>
</complexType>
<element name="EnquiryByNationalId">
<complexType>
<sequence>
<element name="SETID" type="xsd:string"/>
<element name="NATIONAL_ID" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="EnquiryByNationalIdResponse">
<complexType>
<sequence>
<element name="EnquiryByNationalIdReturn" type="impl:CrmCustomerId"/>
</sequence>
</complexType>
</element>
<complexType name="CrmCustomerId">
<sequence>
<element name="SETID" nillable="false" type="xsd:string"/>
<element name="CPL_LEGACY_ID" nillable="true" type="xsd:string"/>
<element name="CUST_ID" nillable="true" type="xsd:string"/>
<element name="RESPOND_MSG" nillable="false" type="xsd:integer"/>
</sequence>
</complexType>
<element name="EnquiryByName">
<complexType>
<sequence>
<element name="SETID" type="xsd:string"/>
<element name="LAST_NAME" type="xsd:string"/>
<element name="FIRST_NAME" type="xsd:string"/>
<element name="ADDRESS1" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="EnquiryByNameResponse">
<complexType>
<sequence>
<element name="EnquiryByNameReturn" type="impl:CrmCustomerId"/>
</sequence>
</complexType>
</element>
<complexType name="CrmCustomerId">
<sequence>
<element name="SETID" nillable="false" type="xsd:string"/>
<element name="CPL_LEGACY_ID" nillable="true" type="xsd:string"/>
<element name="CUST_ID" nillable="true" type="xsd:string"/>
<element name="RESPOND_MSG" nillable="false" type="xsd:integer"/>
</sequence>
</complexType>
<element name="EnquiryByPhoneCell">
<complexType>
<sequence>
<element name="SETID" type="xsd:string" />
<element name="PHONE_CELL" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="EnquiryByPhoneCellResponse">
<complexType>
<sequence>
<element name="EnquiryByPhoneCellReturn" type="impl:CrmCustomerId"/>
</sequence>
</complexType>
</element>
<complexType name="CrmCustomerId">
<sequence>
<element name="SETID" nillable="false" type="xsd:string"/>
<element name="CPL_LEGACY_ID" nillable="true" type="xsd:string"/>
<element name="CUST_ID" nillable="true" type="xsd:string"/>
<element name="RESPOND_MSG" nillable="false" type="xsd:integer"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
<wsdl:message name="EnquiryByLegacyIdRequest">
<wsdl:part element="intf:EnquiryByLegacyId" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnquiryByLegacyIdResponse">
<wsdl:part element="intf:EnquiryByLegacyIdResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnquiryByNationalIdRequest">
<wsdl:part element="intf:EnquiryByNationalId" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnquiryByNationalIdResponse">
<wsdl:part element="intf:EnquiryByNationalIdResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnquiryByNameRequest">
<wsdl:part element="intf:EnquiryByName" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnquiryByNameResponse">
<wsdl:part element="intf:EnquiryByNameResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnquiryByPhoneCellRequest">
<wsdl:part element="intf:EnquiryByPhoneCell" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnquiryByPhoneCellResponse">
<wsdl:part element="intf:EnquiryByPhoneCellResponse" name="parameters"/>
</wsdl:message>
<wsdl:portType name="CrmCustomerService">
<wsdl:operation name="EnquiryByLegacyId">
<wsdl:input message="intf:EnquiryByLegacyIdRequest" name="EnquiryByLegacyIdRequest"/>
<wsdl:output message="intf:EnquiryByLegacyIdResponse" name="EnquiryByLegacyIdResponse"/>
</wsdl:operation>
<wsdl:operation name="EnquiryByNationalId">
<wsdl:input message="intf:EnquiryByNationalIdRequest" name="EnquiryByNationalIdRequest"/>
<wsdl:output message="intf:EnquiryByNationalIdResponse" name="EnquiryByNationalIdResponse"/>
</wsdl:operation>
<wsdl:operation name="EnquiryByName">
<wsdl:input message="intf:EnquiryByNameRequest" name="EnquiryByNameRequest"/>
<wsdl:output message="intf:EnquiryByNameResponse" name="EnquiryByNameResponse"/>
</wsdl:operation>
<wsdl:operation name="EnquiryByPhoneCell">
<wsdl:input message="intf:EnquiryByPhoneCellRequest" name="EnquiryByPhoneCellRequest"/>
<wsdl:output message="intf:EnquiryByPhoneCellResponse" name="EnquiryByPhoneCellResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="CrmCustomerServiceSoapBinding" type="intf:CrmCustomerService">
<wsdlsoap:binding style=""/>
<wsdl:operation name="EnquiryByLegacyId">
<wsdlsoap:operation soapAction="#CPL_LEGACY_ID_ENQ#CCH_TEST"/>
<wsdl:input name="EnquiryByLegacyIdRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="EnquiryByLegacyIdResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="EnquiryByNationalId">
<wsdlsoap:operation soapAction="#CPL_NATIONAL_ID_ENQ#CCH_TEST"/>
<wsdl:input name="EnquiryByNationalIdRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="EnquiryByNationalIdResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="EnquiryByName">
<wsdlsoap:operation soapAction="#CPL_NAME_ENQ#CCH_TEST"/>
<wsdl:input name="EnquiryByNameRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="EnquiryByNameResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="EnquiryByPhoneCell">
<wsdlsoap:operation soapAction="#CPL_PHONE_CELL_ENQ#CCH_TEST"/>
<wsdl:input name="EnquiryByPhoneCellRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="EnquiryByPhoneCellResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="CrmCustomerServiceService">
<wsdl:port binding="intf:CrmCustomerServiceSoapBinding" name="CrmCustomerService">
<wsdlsoap:address location="http://XXX.XX.XXX.XX:8080/PSIGW/HttpListeningConnector"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

I do not understand this WSDL! Its wrong!!
For e.g. why is this section repeated so many times:
<complexType name="CrmCustomerId">
<sequence>
<element name="SETID" nillable="false" type="xsd:string"/>
<element name="CPL_LEGACY_ID" nillable="true" type="xsd:string"/>
<element name="CUST_ID" nillable="true" type="xsd:string"/>
<element name="RESPOND_MSG" nillable="false" type="xsd:integer"/>
</sequence>
</complexType>
Also when creating what mapping did you choose? JAX-B or JAX-RPC?
Try JAX-B.
Venkat

Element name too long when using ROWTYPE

I've come across an issue with xml element names longer than 30 characters. Seems it has something to do with ROWTYPE. Creation of this function is successful:
<pre>
CREATE OR REPLACE FUNCTION test_fnc
RETURN XMLTYPE
AS
var_return XMLTYPE;
l_dummy DUAL.dummy%TYPE;
BEGIN
SELECT dummy INTO l_dummy FROM DUAL;
SELECT XMLCONCAT(XMLELEMENT (
"TEST",
XMLFOREST (
l_dummy "THIS_IS_OVER_30_CHARACTERS_LONG"
data_set
INTO var_return
FROM DUAL;
RETURN var_return;
END test_fnc;
</pre>
However, specifying the variable as ROWTYPE gives ORA-00972 error (unless I shorten the element name...):
<pre>
CREATE OR REPLACE FUNCTION test_fnc
RETURN XMLTYPE
AS
var_return XMLTYPE;
l_dummy DUAL%ROWTYPE;
BEGIN
SELECT dummy INTO l_dummy FROM DUAL;
SELECT XMLCONCAT(XMLELEMENT (
"TEST",
XMLFOREST (
l_dummy.dummy "THIS_IS_OVER_30_CHARACTERS_LONG"
data_set
INTO var_return
FROM DUAL;
RETURN var_return;
END test_fnc;
</pre>
Has anyone come across this before, or have any ideas for a solution? I could specify all my variables as TYPE but as there are many within the tables it would be easier to use ROWTYPE.
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
Thanks.

it works if you add "AS" after l_dummy.dummy
SQL> CREATE OR REPLACE FUNCTION test_fnc
2     RETURN XMLTYPE
3 AS
4     var_return   XMLTYPE;
5     l_dummy      DUAL%ROWTYPE;
6 BEGIN
7     SELECT   dummy INTO l_dummy FROM DUAL;
8
9     SELECT   XMLCONCAT(XMLELEMENT (
10                           "TEST",
11                           XMLFOREST (
12                              l_dummy.dummy AS "THIS_IS_OVER_30_CHARACTERS_LONG"
13                           )
14                        ))
15                 data_set
16       INTO   var_return
17       FROM   DUAL;
18 RETURN var_return;
19 END test_fnc;
20 /
Function created.Ants

XML element names required in lower case

Hi,
I am on release 4.6C
I create an XML file from internal table using FM SDIXML_DATA_TO_DOM and SDIXML_DOM_TO_XML.
The internal table is defined such that the fieldnames of internal table are same as element names in XML file.
The XML file gets created properly, but the element names appear in upper case.
The requirement is to have it in lower case.
Does anybody have any idea about how to control the case here?

Hi Sudhir
you can convert field names manually using translate command to convert it to lower case.
hope this helps.

Simple Transformation with very long XML element names

I am trying to write a program to deserialize XML documents using the Simple Transformation technique. There are many optional elements in the XML document, so I need to have conditional statements statements to avoid trying to process elements that are not in the document. The XML document, however, has several Element Names that are greater than 30 characters in length. The Simple Transformation technique seems to require ABAP data dictionary structures that mirror the schema of the XML document. But one cannot create structure component names that are greater than 30 characters in length. We don't have any control over the XML schema as the XML documents come from the US government. The ST fragment below shows the statement that I want to write, but since the ABAP Structure PlasticCardInformationGroup cannot have a component AuthorizationResponseInformation, the ST syntax checker yields an "Illegal Reference ADDITIONALPLASTICCARDINFORMATION" error message.
Does anyone know a way to avoid this error?
<tt:d-cond check="exist(TRS_TradingPartner_Agreement.TRS_FinancialTransaction.PlasticCardInformationGroup.AdditionalPlasticCardInformation)">
<ns2:AdditionalPlasticCardInformation>
<tt:attribute name="CardNetworkType" value-ref="TRS_TRADINGPARTNER_AGREEMENT.TRS_FINANCIALTRANSACTION.PLASTICCARDINFORMATIONGROUP.ADDITIONALPLASTICCARDINFORMATI.CARDNETWORKTYPE"/>
<tt:attribute name="DraftLocatorNumber" value-ref="TRS_TRADINGPARTNER_AGREEMENT.TRS_FINANCIALTRANSACTION.PLASTICCARDINFORMATIONGROUP.ADDITIONALPLASTICCARDINFORMATI.DRAFTLOCATORNUMBER"/>
</ns2:AdditionalPlasticCardInformation>

could anyone help me?

Generic wsdl - how can you tell what the field assignment is?

When using the generic wsdl, it seems that your custom fields are mapped to fields such as:
customcurrency12
customtext4
When accessing the asset class, how can tell what field is assigned to what custom value? When I look in the admin > application customization > asset > asset field setup
I can see the list of fields and field types but not the number on the end so that I can assign it in my web service code. Is there a way to see what your custom fields are mapped to (i.e. custom standard discount is mapped to custompercent11)
Thanks in advance any help you can lend on this,
AspnetDev

You can use the getMapping web service to get al ist of all the fields for a record type. for each field you get the ElementName (which is what you get in the generic wsdl) and DisplayName which you can use it to match to your fields.
<Field>
     <DisplayName>My Custom Field</DisplayName>
     <ElementName>CustomText74</ElementName>
     <DataType>Text (Short)</DataType>
</Field>
-JLV

Specifying Case-Insensitive Element Names in XML Schema

Hope someone knows this!
Is it possible to define an an XML Schema Definition so that Element names in the target XML File can be case insensitive.
At the moment my Parser throws an error if the element names in the XML file do not have the exact same case as the definition in the XML schema.
E.g
In Schema i have:
<xsd:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" maxOccurs="unbounded" minOccurs="0"/>
but in xml file i have
<HostInventoryLine field=""/>
or
<hostinventoryline field=""/>
Does anyone know anyway to get around this, so that the parser accepts the HostInventoryLine element in the xml as an instance of the HOSTINVENTORYLINE element defined in the schema.
Thanks in Advance
JJ
Message was edited by:
[email protected]

You could use substitution groups to handle this. You would need an entry in the schema for each valid capitalization. This won't scale well if you want to be completely case insensitive, but if you only support lower case, upper case, and camel case it should do the trick.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:complexType name="HostInventoryLineType">
          <xs:sequence>
               <xs:element name="an-element" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="HostInventoryLine" type="HostInventoryLineType"/>
     <xs:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
     <xs:element name="hostinventoryline" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
</xs:schema>-Blaise

Dynamically Using XML Element name as column names

I have a requirement where I need to show data for 31 days or days of the month based on the data in the xml result.
Based on the month you are running the report, some may have 28 elements and some may have 31 elements in the data for days.
How do I dynamically show 28 columns or 31 columns etc - the trick here is I have to use the name of the XML element and not the value for column names.
My requirement is like this.
Deal --------01 -------- 02 -------- 03 -------- 04 05 .upto ... 31days
Deal 1 : 22218 : 32218 : 11918
Deal 2 : Qty1 : Qty2 : Qty3
I need to be able to use the XML Element names , Day01, Day02 etc as the column names in the report.
How can I use the XML Element name - in this case I need to remove the "Day" and use just the number part for the column name.
I can't have xml element names as numbers, thats why "Day" string is prefixed.
<Row state="">
<DEAL>Deal 1</DEAL>
<PORTFOLIO>AM ST Prod PDP</PORTFOLIO>
<CPTY>DTEGO</CPTY>
<FACILITY>MICHCON</FACILITY>
<POINT>100013 : Chestonia 17-Rec</POINT>
<TYPE>Purchase</TYPE>
<Day01>22218</Day01>
<Day02>32218</Day02>
<Day03>11918</Day03>
<Day04>11918</Day04>
<Day05>11918</Day05>
<Day06>11918</Day06>
<Day07>11918</Day07>
<Day08>11918</Day08>
<Day09>11918</Day09>
<Day10>11918</Day10>
<Day11>11918</Day11>
<Day12>23238</Day12>
<Day13>11918</Day13>
<Day14>11918</Day14>
<Day15>11918</Day15>
<Day16>32328</Day16>
<Day17>11918</Day17>
<Day18>11918</Day18>
<Day19>11918</Day19>
<Day20>11918</Day20>
<Day21>11918</Day21>
<Day22>11918</Day22>
<Day23>11918</Day23>
<Day24>11918</Day24>
<Day25>11918</Day25>
<Day26>11918</Day26>
<Day27>13511</Day27>
<Day28>13550</Day28>
<Day29>13550</Day29>
<Day30>13550</Day30>
</Row>

I have a requirement where I need to show data for 31 days or days of the month based on the data in the xml result.
Based on the month you are running the report, some may have 28 elements and some may have 31 elements in the data for days.
How do I dynamically show 28 columns or 31 columns etc - the trick here is I have to use the name of the XML element and not the value for column names.
My requirement is like this.
Deal --------01 -------- 02 -------- 03 -------- 04 05 .upto ... 31days
Deal 1 : 22218 : 32218 : 11918
Deal 2 : Qty1 : Qty2 : Qty3
I need to be able to use the XML Element names , Day01, Day02 etc as the column names in the report.
How can I use the XML Element name - in this case I need to remove the "Day" and use just the number part for the column name.
I can't have xml element names as numbers, thats why "Day" string is prefixed.
<Row state="">
<DEAL>Deal 1</DEAL>
<PORTFOLIO>AM ST Prod PDP</PORTFOLIO>
<CPTY>DTEGO</CPTY>
<FACILITY>MICHCON</FACILITY>
<POINT>100013 : Chestonia 17-Rec</POINT>
<TYPE>Purchase</TYPE>
<Day01>22218</Day01>
<Day02>32218</Day02>
<Day03>11918</Day03>
<Day04>11918</Day04>
<Day05>11918</Day05>
<Day06>11918</Day06>
<Day07>11918</Day07>
<Day08>11918</Day08>
<Day09>11918</Day09>
<Day10>11918</Day10>
<Day11>11918</Day11>
<Day12>23238</Day12>
<Day13>11918</Day13>
<Day14>11918</Day14>
<Day15>11918</Day15>
<Day16>32328</Day16>
<Day17>11918</Day17>
<Day18>11918</Day18>
<Day19>11918</Day19>
<Day20>11918</Day20>
<Day21>11918</Day21>
<Day22>11918</Day22>
<Day23>11918</Day23>
<Day24>11918</Day24>
<Day25>11918</Day25>
<Day26>11918</Day26>
<Day27>13511</Day27>
<Day28>13550</Day28>
<Day29>13550</Day29>
<Day30>13550</Day30>
</Row>

XSLT Transformation error: Non-canonical structure of element name

Good day experts,
I have recently started using xslt, and came upon the following demo in the sdn.
http://wiki.sdn.sap.com/wiki/display/ABAP/XMLXSLTwith+ABAP
I have retrieved the example xml files from airplus.com, as per the instructions, and implemented the code.
When I test the xslt transformation in se80, it transforms correctly.
However, when I run the program, I get the following error.
CX_XSLT_FORMAT_ERROR
Transformation error: Non-canonical structure of element name XML_OUTPUT
Is there an error in the example that I am not aware of?
Thanks in advance,
Johan Kriek

Found the solution.
You rename the tag <XML_OUTPUT> to anything else like <TEST>. And Hurray!!! it works.
It looks like SAP is using this name internally somewhere so we are getting error when we are using same name.
Anyways the problem is solved.
Regards,
Jai

Generic WSDL element name

Similar Messages

Maybe you are looking for