Unexpected Element : :report

Hi Experts,
I am facing an error when ever i try to create a new report in BI Publisher.
The report works well in Query builder but when i view it online it gives me error Unexpected Element : :report
Even if i use oracle answer or file as data source it still gives me error
Please guide me to resolved this issue.
Thanks in Advance.
Cheers,
Andy.

Hello all,
This is due a a Bug/Feature where the "xmlns" attribute is not automatically inserted into the element in the xdo file for your report. To resolve the issue is quite simple.
1. Open the xdo file for you report in your favorite text editor
2. Insert the following attribute into the <report> element
xmlns="http://xmlns.oracle.com/oxp/xmlp"
The <report> element should now look something like this:
<report version="1.1" xmlns="http://xmlns.oracle.com/oxp/xmlp" defaultDataSourceRef="dev">
</report>
I wrote a small article about this here:
[http://mrmcgeek.blogspot.com/2008/11/rendering-error-unexpected-element.html|http://mrmcgeek.blogspot.com/2008/11/rendering-error-unexpected-element.html]

Similar Messages

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?

Sale order - Wbs element Report

Hi
Is there any report for sale order wise wbs element report.
In my sale order i will give wbs element and now i want to check "for one sale order , what are the wbs elements"

You can check the WBS for a sales order from the table view of VBAP.
The WBS field is PS_PSP_PNR.
Goto SE16 and give VBAP.
Enter your sales order number and execute. Look for your WBS elements in foeld PS_PSP_PNR for the different line items.
You can also create a quick SAP query on this.

WBS Element report in both currency- Urgent

hi
I want to pull WBS elements report in Both USD and CAN $ together but i do not know whr to do it.
plz tell me whr in Project System i can do this
plz help it is very urgent
Thanks
Manish

Hi Manish,
Use transaction code <b>CJI3</b>. When prompted, input controlling area, and on prompt for DB Profile, input <b>000000000001</b>. Input the WBS element in its field and execute. Once the report is displayed, Use the "<b>Change Layout</b>" icon to select the fields "<b>Value COCurr</b>", "<b>Value ObjCurr</b>", "<b>Value TranCurr</b>" etc. pull these across from the right hand side to the left hand side using the directional arrow. Press "Enter". The figures would now show in the report for the various currencies.
I hope this helps.
Do not forget to award the points please.
Regards,
Jacob

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

SOA composite failing with unexpected element

Hello All
In OIM 11g R2PS2 and SOA 11.1.1.7, we have a custom workflow which sends an approval request to all members in a specific role e.g. Role1 at operational level. I took that workflow and added a switch case which will send an approval to same role Role1 and further extended it by adding a sequential stage which will also send to all members to another role e.g. Role2. Before this switch case, there is a business rule component. After I deploy the composite and a user raise a request, the request goes to the operational level and when it is approved the request fails with the following exception in the soa log -
==> f-0 initial-fact()
<Error> <oracle.soa.services.rules> <BEA-000000> <<.> Error while executing the rule session.
The rule session 260012 failed to execute.
Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Error while executing the rule session.
The rule session 260012 failed to execute.
Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
at oracle.bpel.services.rules.rpi.AbstractDefaultRuleSession.execute(AbstractDefaultRuleSession.java:276)
at oracle.bpel.services.rules.rpi.oracle2.OracleRuleSession.execute(OracleRuleSession.java:278)
Caused By: javax.xml.bind.UnmarshalException: unexpected element (uri:"http://xmlns.oracle.com/RequestServiceApp/RequestDataService/CatalogData", local:"CatalogData"). Expected elements are <{http://xmlns.oracle.com/RequestServiceApp/RequestDataService/RoleData}RoleData>,<{http://xmlns.oracle.com/RequestServiceApp/RequestDataService/RoleData}RoleKey>
This exception only occurs when I add the new changes - i.e. new switch case and sequential stage. I do not understand where I am going wrong. I am attaching some screen shots -
The workflowselection component is as follows -
Please give me any advice, I am not understanding anything. Thank You in advance.

I am not quite following exactly what you are trying to accomplish but I have two things to look at.
1. When you added Role2 to the business rules, did you pass that in as a parameter? If so, did you remember to reflect that new parameter in the business rule and the bpel process?
2. In the copy rules from your screen shot, I see 3 slashes after catalogData. I would expect to see 2. However, it could be correct. I am not clear on exactly what is happening without seeing some actual source code.

Error 103: application.initialWindow.autoOrients is an unexpected element/attribute

Hello.
I'm using Flash Builder 4.5 to experiment with building a mobile app for my Android Nexus One. In order to keep the app in landscape mode, regardless of the orientation of the device, I've read that I need to set the following in the "AppName-app.xml" file:
<aspectRatio>landscape</aspectRatio>
<autoOrients>false</autoOrients>
And this does work fine in the debugger, however when I attempt to test it on my connected device it throws this error:
Error occurred while packaging the application:
D:\Projects\FlexMobile\AppName\bin-debug\AppName-app.xml(108): error 103: application.initialWindow.autoOrients is an unexpected element/attribute
I know that I'm able to build and test apps on my device, as I've been through the Flex Test Drive for Mobile tutorial (http://www.adobe.com/devnet/flex/testdrivemobile.html) and was able to build and run that app with no issues and this app I'm currently working on does run on the device if I do not attempt to restrict the auto orientation.
Thank you.
(Note: I'm re-posting this from the Flex SDK > Developers forum.)

User rblaa provided that answer in http://forums.adobe.com/thread/858772.
The <autoOrients> node (along with several others) occours twice in the generated -app.xml file. Do not un-comment the first instance, instead edit the parameters set in the second already un-commented autoOrients node.

Secondary cost element report

Hi experts,
i just looking for secondary cost element reports ?
regards,
Sanju M S

HI,
Go to T.code : S_SL0_21000007 and,
Go to bellow link
http://wiki.sdn.sap.com/wiki/display/PLM/SettlementandCostElementReports
http://help.sap.com/saphelp_46c/helpdata/en/a9/ab76ce414111d182b10000e829fbfe/content.htm
Thanks,
Raviteja

Settled costs don't display in hierachy and by cost element report!

Hi Experts,
After doing project settlement, I check in hierarchy cost report (S_ALR_87013533) and by cost element report (S_ALR_87013543) and found that: Costs which had been settled did not display anymore!!
It's not my expectation because I want to see the total actual cost of project.
Please help to advise.
Thanks and best regards,
Khoa Huynh

Hi Sreenivas Kadiam,
So you mean that only when we settle project cost to CO production order, in Project cost report, balance will be zero is the standard behavior, am I right?
Because when I settled the project cost to AUC, the total actual cost of project still display in Project cost report.
Thanks and best regards,
Khoa Huynh

Cost element report prob. with auxiliary account assignment

Hi,
WBS is statistical.
Orders are auxiliary account assigned to WBS.
When running cost element reports, cji3 ; settlement cost elements are not showing there for the order.
Kindly suggest.
Thanks,
Harsh.
Edited by: Harsh Saxena on Dec 8, 2010 2:12 PM

NOT RESOLVED

Change value in cost element report

Dear Experts,
Is dere any option to change value in the cost element report ie S_ALR_87013543...If it is possible please let me know......
By
AS

Hi,
I don't think that Price Change Functionality would be possible in any of the PS reports.
Regards,
Harsh.

GL/cost element report

Hi Friends,
Please let me know that which tcode or link i must use to check the cost coming from various GL/Cost elements
Rgds
Rahul
Edited by: rahul m on May 9, 2008 12:47 PM

Hi,
Pls check following transactions to execute hierarchy reports and cost element reports.:
CJE0: Execute Report: Hierarchy Report
CJEB:Execute Report: Hierarchy Report in Background
GR55:Execute Report: Cost Element Report
Reward if useful.
Regards,
Amit

Standard cost element reports are not available

Hi everyone,
I noticed that there are no standard cost element reports available in our SAP application. Is this because they are not imported or is this caused by another problem ?
Help would be greatly appreciated and points will be rewarded
Kind regards
Message was edited by:
Björn Demol
Message was edited by:
Björn Demol

can you tell me how did u resolve this issue
Regards
Bilal

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

DefaultValidationEventHandler: [ERROR]: Unexpected element {}:Key

When I tried to unmarshal the xml string to Jaxb generated java object I got following error:
DefaultValidationEventHandler: [ERROR]: Unexpected element {}:Key
Anyone has any idea about this?
I greatly appreciate your thoughts!
JAXBContext jc = JAXBContext.newInstance(feedXsd);
Unmarshaller unmarshaller = jc.createUnmarshaller();
ContentEnvelope contentEnvelope =(ContentEnvelope) unmarshaller.unmarshal(new StreamSource(new StringReader(feedStr)));
vini

Just would like to share with you -- I found what caused the exception thrown. My xml file is too big. After I resize the xml file it is working.
vini

Unexpected Element : :report

Similar Messages

Maybe you are looking for