JAXB - Elements declared as Complex Types becomming static inline classes

When a complex type is defined in the XSD as a complex type, compiling the scheme creates it as static class within the owning class.
Is there anyway to change the behavior so that a regular class is created? Or do I need to change the schema to declare the type 'at the top level'?

Similar Messages

Map xsd complex type to existing java class without adding JAXB annotations

Hello
I've got a case where I should map an xsd complex type to an existing Java class without modifying that class, i.e. without adding JAXB annotations to that class.
Is this possible somehow?
As far as I've understood, the <javaType> declaration (adapter, parse/print methods) can only be used for xsd simple types.
Thanks, Tom

It should be possible to implement an XmlAdapter<...,...> which performs the required conversion between the original type and a JAXB-annotated type. Then, at the places where the original type is used, the @XmlJavaTypeAdapter annotation would be used.
The xjc compiler supports this for xsd simple types (xjc:javaType annotation), but not for complex types.
Any idea why this is restricted to simple types?
Would it be possible to implement a xjc plugin which does this for complex types?
Thanks Tom.

How to pass values to XML complex type of a Webservice using PL/SQL

HI,
I need to call a web service from PL/SQL that has an complex type element. That complex type element has 4 child elements each of integer type.
I want to pass values for this complex type using SOAP_API.add_parameter but I can't understand how to pass the values.
<xsd:element name="getBestFit">
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element maxOccurs="1" minOccurs="1" name="circleId" type="xsd:string"/>
                    <xsd:element maxOccurs="1" minOccurs="1" name="usage" type="Q1:UsageInfoType"/>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
<complexType name="UsageInfoType">
     <sequence>
          <element maxOccurs="1" minOccurs="1" name="a1" type="int"/>
          <element maxOccurs="1" minOccurs="1" name="a2" type="int"/>
          <element maxOccurs="1" minOccurs="1" name="a3" type="int"/>
          <element maxOccurs="1" minOccurs="1" name="a4" type="int"/>
     </sequence>
</complexType>
Please help me in getting a solution here.
Thanks in advance.

Have you tried doing a google search on "SOAP_API.add_parameter" to see what comes back? I see a lot of hits come back so hopefully one of those will help you. I've never used soap_api as I used utl_http to make WS calls. This required me to build the SOAP message (aka XML of a specific nature) by hand and then pass it to the WS using utl_http. How this approach is done via SOAP_API, I can't say.

Web service call problem with complex types input

We are trying to call a web service and pass as parameter
some complex types. When invoking the web service everything works
well on flex side, but on the server side the input parameters we
get from flex are not correct - complex type is removed and the
elements of the complex type are sent. See the example:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:WebService id="ws_id" wsdl="link" useProxy="false"
fault="wsFault(event)">
<mx:operation id="op_id" name="op"
result="wsResult(event)">
<mx:request>
<parameters>
<parameter1>{value1}</parameter1>
<parameter2>{value2}</parameter2>
<parameter3>{value3}</parameter3>
<parameter4>
<parameter4_1>{value4_1}</parameter4_1>
<parameter4_2>{value4_2}</parameter4_2>
<parameter4_3>{value4_3}</parameter4_3>
</parameter4>
</parameters>
</mx:request>
</mx:operation>
</mx:WebService>
</mx:Application>
on server side we get this:
<parameters>
<parameter1>{value1}</parameter1>
<parameter2>{value2}</parameter2>
<parameter3>{value3}</parameter3>
<parameter4_1>{value4_1}</parameter4_1>
<parameter4_2>{value4_2}</parameter4_2>
<parameter4_3>{value4_3}</parameter4_3>
</parameters>
Instead of :
<parameters>
<parameter1>{value1}</parameter1>
<parameter2>{value2}</parameter2>
<parameter3>{value3}</parameter3>
<parameter4>
<parameter4_1>{value4_1}</parameter4_1>
<parameter4_2>{value4_2}</parameter4_2>
<parameter4_3>{value4_3}</parameter4_3>
</parameter4>
</parameters>
Any idea how is it possible to send complex type as web
service input from flex ?

Hi,
I also have similar type of problem where I need to invoke a Web service with Complex input parameters.
I followed Susan's blog but I stuck at a point where methos getItem is created.
Can anyone tell me how to get that method for my requirement.
If possible can you guys share your solutions here.
Thanks in advance.

Web Services Data Control - Complex type bindings

I am calling a web services using the web service data control. The request object is a complex type. I observed that some data managed to bind but some failed to bind (empty value on the outbound SOAP payload). Specifically, all the "scalar" elements within the complex type managed to bind. For example the following element snippet within the overall complex data did not bind the value entered to the SOAP payload:
<xsd:element minOccurs="0" name="zones">
<xsd:annotation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element type="xsd:string" maxOccurs="unbounded" minOccurs="1" name="zone"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
While the following complex element within the same payload managed to bind value entered:
<xsd:element minOccurs="0" name="orderBy">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="orderByItem">
<xsd:complexType>
<xsd:all>
<xsd:element type="xsd:string" name="fieldName"/>
<xsd:element type="xsd:boolean" name="ascending"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Any bug report of this?
Cheers
Boon

Hi Frank,
Thanks for the response. I looked further into the problem. This is what I found.
This is error message:
javax.xml.ws.soap.SOAPFaultException: Foundation Engine Error: '' is an Invalid search zone. Valid zones include: 'id_object','name','published.name','comment_text','published.comment_text','note','document_extension','published.document_extension','physical_id','file_title','published.created_by','content'
I turned on the trace and found the following message:
[SRC_METHOD: parse] [225] No XML file /ObjectiveSearch/send/params/searchRequest/searchInput/searchInfo/zones/zones.xml for metaobject ObjectiveSearch.send.params.searchRequest.searchInput.searchInfo.zones.zones
But when I looked into the model directory, I only able to find:
H:\JDeveloper\AdvancedSearch\Model\adfmsrc\ObjectiveSearch\send\params\searchRequest\searchInput\searchInfo\zones\zone.xml
It seems that WS data controller adapter is looking for zones/zones.xml. The wsdl specify zones with sub-elements(sequence) of zone (see wsdl below). The correct structure (zones/zone) is shown on the web service data control pallete and I can bind it to a JSF page.
wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:tns="urn:objective.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xi="http://www.w3.org/2001/XInclude" targetNamespace="urn:objective.com" name="searchService">
<wsp:Policy wsu:Id="WSSPortBindingInputPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sp:TransportBinding>
<wsp:Policy>
<wsp:All>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken RequireClientCertificate="false"/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic128/>
</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:Strict/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
</wsp:All>
</wsp:Policy>
</sp:TransportBinding>
<sp:EndorsingSupportingTokens>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:WssX509V3Token10/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:EndorsingSupportingTokens>
<sp:SignedParts>
<sp:Body/>
</sp:SignedParts>
<sp:SignedSupportingTokens>
<wsp:Policy>
<wsp:All>
<sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:NoPassword/>
</wsp:Policy>
</sp:UsernameToken>
</wsp:All>
</wsp:Policy>
</sp:SignedSupportingTokens>
<sp:Wss11>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefKeyIdentifier/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:Wss11>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsp:Policy wsu:Id="WSSPortBindingOutputPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sp:EndorsingSupportingTokens>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Always">
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:WssX509V3Token10/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:EndorsingSupportingTokens>
<sp:SignedParts>
<sp:Body/>
</sp:SignedParts>
<sp:Wss11>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefKeyIdentifier/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</sp:Wss11>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<types>
<xsd:schema targetNamespace="urn:objective.com">
<xsd:simpleType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="logicalOperatorType">
<xsd:annotation>
<xsd:documentation>The type of join of the condition 'and' 'or'.
               </xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="and"/>
<xsd:enumeration value="or"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="expressionType">
<xsd:sequence>
<xsd:choice maxOccurs="unbounded" minOccurs="0">
<xsd:element maxOccurs="unbounded" minOccurs="0" type="tns:expressionType" name="expression"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" type="tns:metadataCondition" name="condition"/>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="metadataCondition">
<xsd:annotation>
<xsd:documentation>
</xsd:documentation>
</xsd:annotation>
<xsd:all>
<xsd:element type="tns:logicalOperatorType" name="logicalOperator"/>
<xsd:element type="xsd:string" name="field"/>
<xsd:element type="xsd:string" name="operator"/>
<xsd:element minOccurs="0" type="xsd:string" name="value"/>
</xsd:all>
</xsd:complexType>
<xsd:element xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="searchRequest">
<xsd:annotation>
<xsd:documentation>
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:all>
<xsd:element name="searchInput">
<xsd:complexType>
<xsd:all>
<xsd:element name="searchInfo">
<xsd:complexType>
<xsd:all>
<xsd:element minOccurs="0" name="objectTypes">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" type="xsd:string" name="objectType">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:int" name="numResults">
<xsd:annotation>
<xsd:documentation>The maximum number of results to     search for.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:boolean" name="showDeleted">
<xsd:annotation>
<xsd:documentation>Show deleted objects in the search results?</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="textQuery">
<xsd:annotation>
<xsd:documentation>A Verity text query, by default the     syntax of the query is "Internet" but can also be changed     to 'Verity' via the query syntax argument.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element type="xsd:string" minOccurs="0" name="syntax">
<xsd:annotation>
<xsd:documentation>The syntax of the search query either
                                                                 'Internet' (default) or 'Verity'.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="searchScopes">
<xsd:annotation>
<xsd:documentation>Search scopes to include in the
                                                                 search.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element type="xsd:string" maxOccurs="unbounded" minOccurs="1" name="searchScope"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="zones">
<xsd:annotation>
<xsd:documentation>Search zones to include in the
                                                                 search.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element type="xsd:string" maxOccurs="unbounded" minOccurs="1" name="zone"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element type="xsd:string" minOccurs="0" name="attributes">
<xsd:annotation>
<xsd:documentation>The attributes used when fetching
                                                                 results (these attributes are passed to inspect).
                                                            </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="behaviours">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="sections">
<xsd:annotation>
<xsd:documentation>     </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="orderBy">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="orderByItem">
<xsd:complexType>
<xsd:all>
<xsd:element type="xsd:string" name="fieldName"/>
<xsd:element type="xsd:boolean" name="ascending"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="searchRoot">
<xsd:annotation>
<xsd:documentation>The root container of the search, for a constrained search.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="depth">
<xsd:annotation>
<xsd:documentation>The depth to traverse.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:objective.com:ecosys" name="searchResult">
<xsd:complexType>
<xsd:all>
<xsd:element type="xsd:string" name="resultId">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element type="xsd:int" name="numberOfResults">
<xsd:annotation>
<xsd:documentation>     </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element type="xsd:boolean" name="sorted">
<xsd:annotation>
<xsd:documentation>     </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" type="xsd:string" name="sortError">
<xsd:annotation>
<xsd:documentation>     </xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:all>
<xsd:attribute name="instanceDomain" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
<message name="searchRequest">
<part name="searchRequest" element="tns:searchRequest"/>
</message>
<message name="searchResult">
<part name="searchResult" element="tns:searchResult"/>
</message>
<portType name="searchPortType">
<operation name="send">
<input message="tns:searchRequest"/>
<output message="tns:searchResult"/>
</operation>
</portType>
<binding name="searchBinding" type="tns:searchPortType">
<wsp:PolicyReference URI="#WSSPortBindingInputPolicy"/>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="send">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<wsp:PolicyReference URI="#WSSPortBindingOutputPolicy"/>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="searchService">
<documentation>"search" service.</documentation>
<port name="searchPort" binding="tns:searchBinding">
<soap:address location="https://youContentServer:443/services/search"/>
</port>
</service>
</definitions>
Cheers
Boon

Problems populating complex type structre in bpel

Hi All,
I'm trying to populate with no good results a complexType variable that contains n maxOccurs="unbounded" element.
This is the schema:
<xsd:complexType name="logWarnParam">
<xsd:sequence>
<xsd:element name="Message" type="xsd:string"/>
<xsd:element name="MessageParam" type="xsd:string" maxOccurs="unbounded"/>
<xsd:element name="context" type="ns1:context"/>
</xsd:sequence>
</xsd:complexType>
This is the bpel variable
<variable name="logWarnParamVariable" element="ns3:logWarnParam"/>
and these are the parts of the bpel that applies to this case:
<while name="While1"
condition="bpws:getVariableData('i')<number(5)">
<scope name="Log1" variableAccessSerializable="no">
<sequence name="Sequence1">
<assign name="assign1">
*<bpelx:append>*
*<bpelx:from expression="string('value1')"/>*
*<bpelx:to variable="logWarnParamVariable"*
query="/ns3:logWarnParam/MessageParam"/>
*</bpelx:append>*
<copy>
<from expression="bpws:getVariableData('i')+1"/>
<to variable="contador"/>
</copy>
</assign>
</sequence>
</scope>
</while>
Can anyone help me with the way to populate this structure?
Thanks in advance!

The complexType element defines a complex type. A complex type element is an XML element that contains other elements and/or attributes.
Its a place holder to hold different types of element or same set of elements.
In the below example you will get more information.
*<xs:element name="employee" type="fullpersoninfo"/>*
*<xs:complexType name="personinfo">*
<xs:sequence>
<xs:element name="firstname" type="xs:string"/>
<xs:element name="lastname" type="xs:string"/>
</xs:sequence>
</xs:complexType>
*<xs:complexType name="fullpersoninfo">*
<xs:complexContent>
<xs:extension base="personinfo">
<xs:sequence>
<xs:element name="address" type="xs:string"/>
<xs:element name="city" type="xs:string"/>
<xs:element name="country" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
In this example i would like to have more than one employee information. So i have created a complexType as "fullpersoninfo", Then in run time i will populate the values inside "fullpersoninfo"
not the employee or fullpersoninfo variable, rather i will populate the firstname, lastname, address, city and country.
The out put will be having value like the below.
<employee>
     <firstname></firstname>
     <lastname></lastname>
     <address>Duke Street</address>
     <city>Liverpool</city>
     <country>UK</country>
</employee>
<employee>
     <firstname></firstname>
     <lastname></lastname>
     <address>Duke Street</address>
     <city>Liverpool</city>
     <country>UK</country>
</employee>
I will populate the elements inside the complex type element not it self.
I took the example from below URL
http://www.w3schools.com/schema/el_complextype.asp
You should modify your assign as below.
<bpelx:append>
<bpelx:from expression="string('value1')"/>
<bpelx:to variable="logWarnParamVariable"
query="*/ns3:logWarnParamVariable/ns3:logWarnParam/ns3:MessageParam*"/>
</bpelx:append>
Let me know how you go !!
Thanks,
Vijay

Complex type return.

Hi guys;
I have this simple class
//This class is implemented as webservice which return complex type of World.
public class HelloWorld {
     public World sayHelloWorld(World world,String countryCode) {
          if(new World().isValidWorld(world))return world;
          else return null;
public class World {
     private String world1 = "us";
     private String world2 = "uk";
     public boolean isValidWorld(World world){
          System.out.println("client passed: world1 "+world.getWorld1()+" world2: "+world.getWorld2());
          if(world.getWorld1().equalsIgnoreCase(this.getWorld1()) && world.getWorld2().equalsIgnoreCase(this.getWorld2()))return true;
          else
               return false;
     //getter and setter for world1 and world2
Now in weblogic test page.I have
parameter as world ,type as World and value as follows:
<world xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:n1="java:com.util"
xsi:type="n1:World">
<world1 href="#ID_2">
</world1>
<world2 href="#ID_2">
</world2>
<xsd:string xsi:type="xsd:string"
id="ID_2">sample string</xsd:string>
</world>
and for next i have parameter as string,type as string and value as text box to input.
But i don't understand or don't know why there is only one input value to put ie. <xsd:string xsi:type="xsd:string"
id="ID_2">sample string</xsd:string> .there should be 2 to input world1 and world2.and now if i input value abc instead of sample string it will pass
the same value(abc) for both world1 and world2 to server.Is that i did sth. wrong in build or there is more.I shall appreciate if somebody
has answer onto this.Basically for complex type i need like this automatically..
<world xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:n1="java:com.util"
xsi:type="n1:World">
<world1 href="#ID_1">
</world1>
<world2 href="#ID_2">
</world2>
<xsd:string xsi:type="xsd:string"
id="ID_1">sample string</xsd:string>
<xsd:string xsi:type="xsd:string"
id="ID_2">sample string</xsd:string>
</world>
any suggestion??

Hi there,
Can you explain what you mean by this :
I have an entry like :
<xs:element name="retrieveDetailsResponse">
                <xs:complexType>
                    <xs:sequence>
                        <xs:element minOccurs="0" name="return" nillable="true" type="ax21:Details"/>
                    </xs:sequence>
                </xs:complexType>
            </xs:element>Do you mean changing the name element to retrieveDetailsReturn - i.e
<xs:element minOccurs="0" name="retrieveDetailsReturn" nillable="true" type="ax21:Details"/>or just
<xs:element minOccurs="0" name="retrieveDetails" nillable="true" type="ax21:Details"/>I can't get any of these to work....
Edited by: uefa_celt on Feb 27, 2009 8:23 AM

Define complex types

Hi,
I'm trying to define a new complex type in my .wsdl file of my bpel process project.
I want one of the elements in this complex type to be of the same type as an element defined in one of my partner link's WSDL.
How can I make this connection (what do I define as namespaces) from my .wsdl file to a partner link's wsdl file.
Thank you!!!

Thanks Clemens!
I will try the first option.
This is my wsdl b - the wsdl I want to import types from :
<definitions
targetNamespace="http://Images/WebService"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:s0="http://Images/WebService"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
<import namespace="http://Images/WebService" location="webServiceFlickr.wsdl"/>
<plnk:partnerLinkType name="webServiceFlickrHttpGet_PL">
<plnk:role name="webServiceFlickrHttpGet_Role">
<plnk:portType name="s0:webServiceFlickrHttpGet"/>
</plnk:role>
</plnk:partnerLinkType>
<plnk:partnerLinkType name="webServiceFlickrSoap_PL">
<plnk:role name="webServiceFlickrSoap_Role">
<plnk:portType name="s0:webServiceFlickrSoap"/>
</plnk:role>
</plnk:partnerLinkType>
<plnk:partnerLinkType name="webServiceFlickrHttpPost_PL">
<plnk:role name="webServiceFlickrHttpPost_Role">
<plnk:portType name="s0:webServiceFlickrHttpPost"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
and this is the beginning of wsdl a - the one I want to import the type into :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="process10"
targetNamespace="http://xmlns.oracle.com/process10"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/process10"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
     <types>
          <schema attributeFormDefault="qualified"
               elementFormDefault="qualified"
               targetNamespace="http://xmlns.oracle.com/process10"
               xmlns="http://www.w3.org/2001/XMLSchema">
I undestand I need to import the namespace of wsdl b , but can't figure out how,
What do I define instead of XXX ?
xmlns:n1="XXX">
<import namespace="XXX" schemaLocation="XXX"/>
Thank you !!

Wsdl2java: Two declarations cause a collision in the ObjectFactory class.

I am using Apache CXF wsdl2java tool to create client classes for a wsdl generated by microsoft .net webservice.
I get this error:
WSDLToJava Error: Thrown by JAXB : Two declarations cause a collision in the ObjectFactory class.
the generated wsdl have complexTypes and elements of the same name for many of its response objects.
For example:
<xs:complexType name="ResponseCode">
<xs:sequence>
<xs:element minOccurs="0" name="Code" type="xs:int"/>
<xs:element minOccurs="0" name="Description" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
<xs:element name="ResponseCode" nillable="true" type="tns:ResponseCode"/>
Does anyone know a solution for dealing with this so that wsdl2java will correctly generate client classes to talk to this server?
Thanks.

I partially fixed this issue by using a jaxb bindings file. This resolved all the places where an element and complextype had the same name.
However, there is still a place where Type: Prompt has an Element: Value
which conflicts with the fact that there is a Type and Element names PromptValue
Here is the binding I used to fix so far, but cannot figure out how to fix the second issue yet.
     <jxb:schemaBindings>
          <jxb:package name="org.datacontract.schemas"/>
          <jxb:nameXmlTransform>
               <jxb:elementName suffix="Element"/>
          </jxb:nameXmlTransform>
     </jxb:schemaBindings>
If anyone has solved this I would appreciate the help.
Thanks.

How to access the JAXB generated methods of Complex element

Hi all,
I am generating the java classes from the a XSD file which contains the Complex element , which again contains the simple elements. JAXB is generating the interface and public static class for the inner Complex element. But i not able to create the object of this inner class using the Object factory class. Then without object how can i access the setter and getter methods contained in this complex element.
My XSD file looks like -
<xs:element name="SSDecisionActivity">
<xs:complexType >
<xs:sequence>
<xs:element name="Id" type="xs:ID"/>
xs:element name="ConditionFlow">
     <xs:complexType>
     <xs:sequence>
     <xs:element name="Condition" type="xs:string"/>
     <xs:element name="DecisionCriteria" type="xs:string" minOccurs="2" maxOccurs="unbounded"/>
How shall i access the methods from the ConditionFlow (Complex element) like setCondition(....),getCondition().
If anybody knows plz tell me the way.
Ravi

I'm a bit confused about this design approach.
[Bindable] public var storyList:IdmlStory = null;
The reason why the above line fails to compile in StoryList.mxml is that a variable of the same name already exists. You have specified a List with an id of storyList. The translation process will yield:
var storyList:List = new List();
and then fill in the properties.

JAXB problem to manage nested complex types

Hi!
I've defined a XSD schema to design a folder structure. So I created a complex type which contains a sequence of 'folder' type elements.
The folder type element includes several elements and a final one which is another 'folder' type element.
So it is easy to model a general folder structure, no matter the depth and length.
When I compile it with JAXB to have an OO view I catch the following error:
Nested type Folder hides an enclosing type
The fragment of code which caused the error is:
* Java content class for Folder complex type.
* <p>The following schema fragment specifies the expected content contained within this java content object. (defined at file:/C:/Progetti/folderschemaexample.xsd line 10)
* <p>
* <pre>
* <complexType name="Folder">
*   <complexContent>
*     <restriction base="{http://www.w3.org/2001/XMLSchema}anyType">
*       <choice maxOccurs="unbounded" minOccurs="0">
*         <element name="folder_name" type="{http://www.w3.org/2001/XMLSchema}string"/>
*         <element name="security" type="{}ACL"/>
*         <element name="folder" type="{}Folder"/>
*       </choice>
*     </restriction>
*   </complexContent>
* </complexType>
* </pre>
*/The error is raised when JAXB tries to compile a Folder interface as inner in another Folder interface (generated.Folder.Folder).
Is any JAXB guru able to suggest me how to exit from this situation to create succesfully a JAXB compliant schema which models this folder structure?
TIA

Hi!
I've defined a XSD schema to design a folder structure. So I created a complex type which contains a sequence of 'folder' type elements.
The folder type element includes several elements and a final one which is another 'folder' type element.
So it is easy to model a general folder structure, no matter the depth and length.
When I compile it with JAXB to have an OO view I catch the following error:
Nested type Folder hides an enclosing type
The fragment of code which caused the error is:
* Java content class for Folder complex type.
* <p>The following schema fragment specifies the expected content contained within this java content object. (defined at file:/C:/Progetti/folderschemaexample.xsd line 10)
* <p>
* <pre>
* <complexType name="Folder">
*   <complexContent>
*     <restriction base="{http://www.w3.org/2001/XMLSchema}anyType">
*       <choice maxOccurs="unbounded" minOccurs="0">
*         <element name="folder_name" type="{http://www.w3.org/2001/XMLSchema}string"/>
*         <element name="security" type="{}ACL"/>
*         <element name="folder" type="{}Folder"/>
*       </choice>
*     </restriction>
*   </complexContent>
* </complexType>
* </pre>
*/The error is raised when JAXB tries to compile a Folder interface as inner in another Folder interface (generated.Folder.Folder).
Is any JAXB guru able to suggest me how to exit from this situation to create succesfully a JAXB compliant schema which models this folder structure?
TIA

JAXB compiler error : Complex Type Definition Representation Error

Hi,
I have a problem when I try to generate Java classes for the XML Digital Signature schema along with the XAdES extension. Apparently, we got an XML validation issue when the XAdES schema is parsed.
Here is the xjc tool ouput :
[ERROR] src-ct.1: Complex Type Definition Representation Error for type 'IdentifierType'. When complexContent is used, the base type must be a complexType.
line 33 of XAdES.xsd
[ERROR] src-ct.1: Complex Type Definition Representation Error for type 'EncapsulatedPKIDataType'. When complexContent is used, the base type must be a complexType.
line 57 of XAdES.xsdNow these are the schema lines from XAdES.xsd that cause the problem :
<xsd:complexType name="IdentifierType">
<xsd:complexContent>
    <xsd:extension base="xsd:anyURI">
      <xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
    </xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="EncapsulatedPKIDataType">
<xsd:complexContent>
    <xsd:extension base="xsd:base64Binary">
      <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
    </xsd:extension>
</xsd:complexContent>
</xsd:complexType>The most disturbing thing is that those two schemas I used (e.g. xmldsig-core-schema.xsd and XAdES.xsd) come directly from the W3C, so they should be fully compliant to the XML schema spec, shouldn't they ?
Moreover, I tried to validate these two schemas with XML Spy 4.3 and the problem occurs in slightly different way. In fact, the <xsd:complexContent> tags are replaced silently by XML Spy with <xsd:simpleContent> tags in order to validate the schema. So XML Spy seems to have a problem too with these complex type definitions. Besides, if I replace the <xsd:complexContent> tags the same way as XML Spy does, and if I run again the JAXB compiler, it works fine...
Does anyone have any knowledge about this issue ? I'd like very much to hear about anyone who has experienced or better solved the same kind of issue.
By the way, here is the version of JAXB that I use :
xjc version "1.0.2-b15-fcs"
JavaTM Architecture for XML Binding(JAXB) Reference Implementation, (build 1.0.2-b15-fcs)Any help appreciated.
Thanks,
Gregory

<xsd:extension base="xsd:anyURI">
<xsd:extension base="xsd:base64Binary">
The base attribute of the xs:extension elements shoule refer to a complexType.
For example,
<xs:complexType name="complexTypeA">
</xs:complexType>
<xsd:complexType name="IdentifierType">
<xsd:complexContent>
<xsd:extension base="complexTypeA">
<xsd:attribute name="Qualifier" type="QualifierType" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

WSDL & local qualified accessors (complex type - child elements)

Why does the WLS8.1 generated WSDL file specify
elementFormDefault="qualified" in the schema for complex types.
The resulting runtime SOAP bodies that are sent have unqualified child
elements and tools like JAX-RPC, determine from the WSDL schema that these
child elements SHOULD be qualified and fail to parse the body. I understand
that the spec states that they should not be qualified but then why does the
schema not specify
elementFormDefault="unqualified"?
I have to manually edit the WSDL (to say "unqualified") to generate a client
using JAX-RPC.
Is there some way I can tell <wsdlgen> task to do this?
Thanks,
M
Here's the excerpt from my WLS 8.1 generated WSDL file:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tp="java:com.xxx.framework.persist"
xmlns:stns="java:com.xxx.businessservices.indexservice.valueobjects"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.xxx.businessservices.indexservice.valueobjects">
<xsd:import namespace="java:com.xxx.framework.persist" />
<xsd:import namespace="java:language_builtins.util" />
<xsd:complexType name="IndexVO">
<xsd:complexContent>
<xsd:extension xmlns:tp="java:com.xxx.framework.persist"
base="tp:FW_PersistentObject">
<xsd:sequence>
<xsd:element type="xsd:string" name="code" minOccurs="1" nillable="true"
maxOccurs="1" />
<xsd:element type="xsd:string" name="description" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="indexID" minOccurs="1" maxOccurs="1"
/>
<xsd:element type="stns:IndexProviderVO" name="indexProviderVO"
minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="stns:IndexSourceVO" name="indexSourceVO" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="name" minOccurs="1" nillable="true"
maxOccurs="1" />
<xsd:element type="xsd:dateTime" name="nextUpdateDate" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="providerID" minOccurs="1"
maxOccurs="1" />
<xsd:element type="xsd:long" name="scheduleID" minOccurs="1"
maxOccurs="1" />
<xsd:element type="stns:UpdateScheduleVO" name="scheduleVO" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="sourceID" minOccurs="1" maxOccurs="1"
/>
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:List"
name="updateFrequencies" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element xmlns:tp="java:com.xxx.framework.persist"
type="xsd:dateTime" name="updatesDisabledDate" minOccurs="1" nillable="true"
maxOccurs="1" />
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:List"
name="values" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
"Scott Ziegler" <[email protected]> wrote in message
news:[email protected]...
On Mon, 21 Jul 2003 09:31:45 -0500, Mark Fine wrote:
I've been debugging an XML-RPC generated client and came across the
following problem:
I have a webserice serialized Object, "IndexVO" that has an attribute
(ie.
element) "code".
The WLS8.1 generated WSDL schema declares that code is in the
"com...valueobjects" namespace by virtue of a default (target)namespace.
At runtime, the SOAP envelope that is created seems to put the
attribute/element "code" in the EMPTY namespace, and not in the
"com...valueobjects" namespace. The XML-RPC generated client code is
looking for "code" in the "com...valueobjects" namespace and skips overit
because it is in the "", blank namespace (according to the XML parser).
I'm not a XML expert but from what I can tell, the SOAP envelope that is
returned does not match the WSDL file with respect to the namespace ofthe
attributes in IndexVO.
Am I reading this wrong?We did this for interoperability reasons. Some other stacks that we were
trying to work with would not work if those elements were qualified. The
problem really stems from SOAP 1.1:http://www.w3.org/TR/SOAP/#_Toc478383520
>
"Accessors whose names are local to their containing types have
unqualified element names; all others have qualified names."
SOAP stacks that are not schema aware basically require this behavior.
You might try using a doc-literal service (which is more faithful to the
schema) if that fits your situation.
--Scott

Currently there is no option to make elementFormDefault
unqualified. I filed an enhancement CR (112776).
Regards,
-manoj
http://manojc.com
"Mark Fine" <[email protected]> wrote in message
news:[email protected]...
Why does the WLS8.1 generated WSDL file specify
elementFormDefault="qualified" in the schema for complex types.
The resulting runtime SOAP bodies that are sent have unqualified child
elements and tools like JAX-RPC, determine from the WSDL schema that these
child elements SHOULD be qualified and fail to parse the body. Iunderstand
that the spec states that they should not be qualified but then why doesthe
schema not specify
elementFormDefault="unqualified"?
I have to manually edit the WSDL (to say "unqualified") to generate aclient
using JAX-RPC.
Is there some way I can tell <wsdlgen> task to do this?
Thanks,
M
Here's the excerpt from my WLS 8.1 generated WSDL file:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tp="java:com.xxx.framework.persist"
xmlns:stns="java:com.xxx.businessservices.indexservice.valueobjects"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.xxx.businessservices.indexservice.valueobjects">
<xsd:import namespace="java:com.xxx.framework.persist" />
<xsd:import namespace="java:language_builtins.util" />
<xsd:complexType name="IndexVO">
<xsd:complexContent>
<xsd:extension xmlns:tp="java:com.xxx.framework.persist"
base="tp:FW_PersistentObject">
<xsd:sequence>
<xsd:element type="xsd:string" name="code" minOccurs="1"nillable="true"
maxOccurs="1" />
<xsd:element type="xsd:string" name="description" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="indexID" minOccurs="1" maxOccurs="1"
/>
<xsd:element type="stns:IndexProviderVO" name="indexProviderVO"
minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element type="stns:IndexSourceVO" name="indexSourceVO"minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:string" name="name" minOccurs="1"nillable="true"
maxOccurs="1" />
<xsd:element type="xsd:dateTime" name="nextUpdateDate" minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="providerID" minOccurs="1"
maxOccurs="1" />
<xsd:element type="xsd:long" name="scheduleID" minOccurs="1"
maxOccurs="1" />
<xsd:element type="stns:UpdateScheduleVO" name="scheduleVO"minOccurs="1"
nillable="true" maxOccurs="1" />
<xsd:element type="xsd:long" name="sourceID" minOccurs="1"maxOccurs="1"
/>
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:List"
name="updateFrequencies" minOccurs="1" nillable="true" maxOccurs="1" />
<xsd:element xmlns:tp="java:com.xxx.framework.persist"
type="xsd:dateTime" name="updatesDisabledDate" minOccurs="1"nillable="true"
maxOccurs="1" />
<xsd:element xmlns:tp="java:language_builtins.util" type="tp:List"
name="values" minOccurs="1" nillable="true" maxOccurs="1" />
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
"Scott Ziegler" <[email protected]> wrote in message
news:[email protected]...
On Mon, 21 Jul 2003 09:31:45 -0500, Mark Fine wrote:
I've been debugging an XML-RPC generated client and came across the
following problem:
I have a webserice serialized Object, "IndexVO" that has an attribute
(ie.
element) "code".
The WLS8.1 generated WSDL schema declares that code is in the
"com...valueobjects" namespace by virtue of a default (target)namespace.
At runtime, the SOAP envelope that is created seems to put the
attribute/element "code" in the EMPTY namespace, and not in the
"com...valueobjects" namespace. The XML-RPC generated client code is
looking for "code" in the "com...valueobjects" namespace and skips
over
it
because it is in the "", blank namespace (according to the XML
parser).
>>>
I'm not a XML expert but from what I can tell, the SOAP envelope thatis
returned does not match the WSDL file with respect to the namespace ofthe
attributes in IndexVO.
Am I reading this wrong?We did this for interoperability reasons. Some other stacks that we
were
trying to work with would not work if those elements were qualified.The
problem really stems from SOAP 1.1:
http://www.w3.org/TR/SOAP/#_Toc478383520
"Accessors whose names are local to their containing types have
unqualified element names; all others have qualified names."
SOAP stacks that are not schema aware basically require this behavior.
You might try using a doc-literal service (which is more faithful to the
schema) if that fits your situation.
--Scott

Can we declare more than one sequence tags in a complex type?

Hi all,
Can we use more than one <sequence> tags in the xml schema?
<xs:complexType name="Demo">
<xs:sequence minoccurs = "1" maxoccurs = "1">
</xs:sequence>
<xs:sequence minoccurs = "0" maxoccurs = "1">
</xs:sequence>
</xs:complexType>
If you observe the above sample xml there are two sequences in one complex type with different values for minoccurs and maxoccurs. Is this xml valid? why I need this is I have an
XML with lot of elements some of them should have minoccurs = "1" maxoccurs = "1" and some other should have the other combination of min and max attributes. I want to
declare it in the sequence rather than declaring beside each individual element. is that possible?
Thanks.

Hi,
Is this xml valid? No, a complexType expects only one child, but you can do this :
<xs:complexType name="Demo">
<xs:sequence>
    <xs:sequence minOccurs = "1" maxOccurs = "1">
    </xs:sequence>
    <xs:sequence minOccurs = "0" maxOccurs = "1">
    </xs:sequence>
</xs:sequence>
</xs:complexType>However...
XML with lot of elements some of them should have minoccurs = "1" maxoccurs = "1" and some other should have the other combination of min and max attributes.
I want to declare it in the sequence rather than declaring beside each individual element. is that possible?minOccurs and maxOccurs declared in the sequence apply to the sequence as a whole, not to its individual components.
For example :
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:complexType name="Demo">
          <xs:sequence>
               <xs:sequence maxOccurs="1" minOccurs="1">
                    <xs:element name="test1" type="xs:string"/>
                    <xs:element name="test2" type="xs:string"/>
               </xs:sequence>
               <xs:sequence maxOccurs="1" minOccurs="0">
                    <xs:element name="test3" type="xs:string"/>
                    <xs:element name="test4" type="xs:string"/>
               </xs:sequence>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="root" type="Demo"/>
</xs:schema>What you expect will work for the first sequence of elements (test1 and test2) but anyway minOccurs and maxOccurs for elements default to 1, so why bother wrapping them in a sequence?
If I understand what you want correctly, it won't work for the second sequence.
For instance, this will be valid :
<root>
<test1/>
<test2/>
<test3/>
<test4/>
</root>but this will not :
<root>
<test1/>
<test2/>
<test3/>
</root>

Import not allowed on nodes of type element declaration

I have 2 very simple transformation processes, consisting of:
1. hit a web service
2. filter the output
3. transform into a variable of type defined by a schema document
4. get the variable as a string
5. call another web service and pass the string
The processes are identical except for the variable type. One process works, the other fails when converting to a string. Here is the error message:
<2005-10-25 11:33:40,627> <ERROR> <default.collaxa.cube.xml> ORABPEL-09500
XPath expression failed to execute.
Error while processing xpath expression, the expression is "orcl:get-content-as-string(bpws:getVariableData("OutputDocument"))", the reason is import not allowed on nodes of type element declaration.
I can successfully use an xsl to convert the variable to a string, but when I utilize the assign activity, it produces the error above. Obviously, the schema files are different for the 2 variables, but I cannot see a problem. The schemas are both valid.
Has anyone encountered this error?
Thanks,
Dave

The cast does not throw an exception, but the resulting string is empty.
The problem is that I do not understand the error message. I am not sure what import it is referring to.
Thanks

JAXB - Elements declared as Complex Types becomming static inline classes

Similar Messages

Maybe you are looking for