Apex Code Development You need to sign in to do that
Don't have an account?
brad4d Namespace references incorrect and unmanageable in the generated apex client to a webservice.
I am using the following wsdl:
Code:
<—xml version="1.0" encoding="UTF-8" –> - <!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.2-b05-RC1. --> - <definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="urn:specific_calculator-services-kronos-com:specific_calculator" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:specific_calculator-services-kronos-com:specific_calculator" name="SpecificCalculatorService"> - <types> - <xs:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:specific_calculator-services-kronos-com:specific_calculator" elementFormDefault="unqualified" attributeFormDefault="unqualified"> - <!-- a name value pair used to add custom attributes to punches, pay code edits, scheduled_shifts, and others. These values assist the rules to make their decisions. --> - <xs:complexType name="TagType"> - <xs:sequence> - <!-- categorization for tags. e.g. pay_category, pay_code, cost_center, exception --> <xs:element name="name" type="xs:string" /> - <!-- tag value. e.g. regular, break, lunch, deli, late_in, very_late_out --> <xs:element name="value" type="xs:string" /> </xs:sequence> </xs:complexType> - <!-- A quantity and units. (aka value). This typically denotes the duration for a block of time. Also the quantity for a total --> - <xs:complexType name="QuantityType"> - <xs:sequence> - <!-- numerical value --> <xs:element name="amount" type="xs:double" /> - <!-- change back to unitsType --> <xs:element name="units" type="xs:string" minOccurs="0" maxOccurs="1" /> </xs:sequence> </xs:complexType> - <!-- The Engine assigns values denoting quantities of time. e.g. Regular=5 hrs, Late=5 times to a pay category. These are typically the durations for a particular scheduled block of time or period block of time. --> - <xs:complexType name="TotalType"> - <xs:sequence> - <!-- Effective date. change back to date --> <xs:element name="effective_date" type="xs:dateTime" /> - <!-- actual, scheduled, or projected. change back to total_type --> <xs:element name="total_type" type="xs:string" /> - <!-- type of pay for employee --> <xs:element name="pay_code" type="xs:string" /> - <!-- total value. (has amount and units) --> <xs:element name="quantity" type="tns:QuantityType" /> </xs:sequence> </xs:complexType> - <!-- punches in the clock or modified by the manager --> - <xs:complexType name="PunchType"> - <xs:sequence> <xs:element name="id" type="xs:string" /> <xs:element name="effective_date" type="xs:dateTime" /> - <!-- change back to punch_direction --> <xs:element name="punch_direction" type="xs:string" /> </xs:sequence> </xs:complexType> - <!-- Work that was actually done. --> - <xs:complexType name="PayCodeEditType"> - <xs:sequence> <xs:element name="id" type="xs:string" /> <xs:element name="pay_code_category" type="xs:string" minOccurs="0" maxOccurs="1" /> <xs:element name="pay_code" type="xs:string" minOccurs="0" maxOccurs="1" /> - <!-- start time. typically populated --> <xs:element name="start_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- end time. typically populated or duration --> <xs:element name="end_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- length of this pay_code_edit --> <xs:element name="duration" type="tns:QuantityType" minOccurs="0" maxOccurs="1" /> </xs:sequence> </xs:complexType> - <xs:complexType name="BreaksType"> - <xs:sequence> <xs:element name="id" type="xs:string" /> <xs:element name="pay_code" type="xs:string" minOccurs="0" maxOccurs="1" /> - <!-- start time. typically populated --> <xs:element name="start_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- end time. typically populated or duration --> <xs:element name="end_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- length of this shift --> <xs:element name="duration" type="tns:QuantityType" minOccurs="0" maxOccurs="1" /> </xs:sequence> </xs:complexType> - <xs:complexType name="ExceptionType"> - <xs:sequence> <xs:element name="rule_id" type="xs:string" /> - <!-- id into resource bundle --> <xs:element name="resource_name" type="xs:string" /> </xs:sequence> </xs:complexType> - <xs:complexType name="ScheduledShiftType"> - <xs:sequence> <xs:element name="id" type="xs:string" minOccurs="0" maxOccurs="1" /> <xs:element name="pay_code_category" type="xs:string" minOccurs="0" maxOccurs="1" /> <xs:element name="pay_code" type="xs:string" minOccurs="0" maxOccurs="1" /> - <!-- start time. typically populated --> <xs:element name="start_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- end time. typically populated or duration --> <xs:element name="end_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- length of this shift. --> <xs:element name="duration" type="tns:QuantityType" minOccurs="0" maxOccurs="1" /> - <!-- breaks during this shift --> <xs:element name="breaks" type="tns:BreaksType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> - <xs:complexType name="ComputedPunchType"> - <xs:sequence> <xs:element name="id" type="xs:string" /> - <!-- exceptions on this punch --> <xs:element name="exceptions" type="tns:ExceptionType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> - <xs:complexType name="ComputedPayCodeEditType"> - <xs:sequence> <xs:element name="id" type="xs:string" /> - <!-- exceptions on this pay_code_edit --> <xs:element name="exceptions" type="tns:ExceptionType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> - <xs:complexType name="ComputedBreakType"> - <xs:sequence> <xs:element name="id" type="xs:string" /> <xs:element name="pay_code" type="xs:string" minOccurs="0" maxOccurs="1" /> - <!-- computed start time. populated if break taken --> <xs:element name="start_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- computed end time. populated if taken (no duration) --> <xs:element name="end_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- punch that starts this break --> <xs:element name="start_punch" type="tns:ComputedPunchType" minOccurs="0" maxOccurs="1" /> - <!-- punch that ends this break --> <xs:element name="end_punch" type="tns:ComputedPunchType" minOccurs="0" maxOccurs="1" /> - <!-- exceptions on this break. --> <xs:element name="exceptions" type="tns:ExceptionType" minOccurs="0" maxOccurs="unbounded" /> - <!-- The Engine assigns values denoting quantities of time. e.g. Regular=5 hrs, Late=5 times to a pay category. These are typically the durations for a particular scheduled block of time or period block of time. --> <xs:element name="totals" type="tns:TotalType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> - <!-- The schedule blocks of time that are populated with exceptions, flags (containing pay categories), actuals, and all sorts of entries. Possibly contains newly created blocks of time that are not scheduled. --> - <xs:complexType name="ComputedShiftType"> - <xs:sequence> <xs:element name="id" type="xs:string" /> <xs:element name="pay_code_category" type="xs:string" minOccurs="0" maxOccurs="1" /> <xs:element name="pay_code" type="xs:string" minOccurs="0" maxOccurs="1" /> - <!-- date to assign this shift. this used day divide. change back to date --> <xs:element name="effective_date" type="xs:dateTime" /> - <!-- computed start time. typically populated --> <xs:element name="start_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- computed end time. typically populated or duration --> <xs:element name="end_date" type="xs:dateTime" minOccurs="0" maxOccurs="1" /> - <!-- computed length of this shift. populated for some pay code edits. --> <xs:element name="duration" type="tns:QuantityType" minOccurs="0" maxOccurs="1" /> - <!-- punch that starts this shift --> <xs:element name="start_punch" type="tns:ComputedPunchType" minOccurs="0" maxOccurs="1" /> - <!-- punch that ends this shift --> <xs:element name="end_punch" type="tns:ComputedPunchType" minOccurs="0" maxOccurs="1" /> - <!-- paycode edit id that was used to create this shift --> <xs:element name="pay_code_edit" type="tns:ComputedPayCodeEditType" minOccurs="0" maxOccurs="1" /> - <!-- exceptions on this shift. (all exceptions˜ summary™) --> <xs:element name="exceptions" type="tns:ExceptionType" minOccurs="0" maxOccurs="unbounded" /> - <!-- breaks during this shift --> <xs:element name="computed_breaks" type="tns:ComputedBreakType" minOccurs="0" maxOccurs="unbounded" /> - <!-- The Engine assigns values denoting quantities of time. e.g. Regular=5 hrs, Late=5 times to a pay category. These are typically the durations for a particular scheduled block of time or period block of time. --> <xs:element name="totals" type="tns:TotalType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> - <!-- units used for Block of Time amount. 'COUNT' denotes a units of quantity rather than units of time. --> - <xs:simpleType name="UnitsTypeEnum"> - <xs:restriction base="xs:string"> <xs:enumeration value="SECONDS" /> <xs:enumeration value="MINUTES" /> <xs:enumeration value="HOURS" /> <xs:enumeration value="DAYS" /> <xs:enumeration value="WEEKS" /> <xs:enumeration value="MONTHS" /> <xs:enumeration value="QUARTERS" /> <xs:enumeration value="YEARS" /> <xs:enumeration value="COUNT" /> </xs:restriction> </xs:simpleType> - <xs:simpleType name="TotalTypeEnum"> - <xs:restriction base="xs:string"> <xs:enumeration value="ACTUAL" /> <xs:enumeration value="SCHEDULED" /> <xs:enumeration value="PROJECTED" /> </xs:restriction> </xs:simpleType> - <xs:simpleType name="PunchDirectionEnum"> - <xs:restriction base="xs:string"> <xs:enumeration value="IN" /> <xs:enumeration value="OUT" /> </xs:restriction> </xs:simpleType> - <!-- method request, responses --> - <xs:element name="CalculateRequest"> - <xs:complexType> - <xs:sequence> - <!-- start of period window. change to date? --> <xs:element name="start_date" type="xs:dateTime" /> - <!-- end of period window. change to date? --> <xs:element name="end_date" type="xs:dateTime" /> - <!-- current point in window --> <xs:element name="now" type="xs:dateTime" /> - <!-- punches in the clock or modified by the manager --> <xs:element name="PunchType" type="tns:PunchType" minOccurs="0" maxOccurs="unbounded" /> - <!-- Work that was actually done. --> <xs:element name="pay_code_edits" type="tns:PayCodeEditType" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="scheduled_shifts" type="tns:ScheduledShiftType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> - <xs:element name="CalculateResponse"> - <xs:complexType> - <xs:sequence> - <!-- The schedule blocks of time that are populated with exceptions, flags (containing pay categories), actuals, and all sorts of entries. Possibly contains newly created blocks of time that are not scheduled. --> <xs:element name="computed_shifts" type="tns:ComputedShiftType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> - <!-- faults --> - <xs:element name="BadInputFault"> - <xs:complexType> - <xs:sequence> <xs:element name="code" type="xs:string" /> <xs:element name="message" type="xs:string" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> </types> - <!-- messages --> - <message name="CalculateRequest"> <part name="parameters" element="tns:CalculateRequest" /> </message> - <message name="CalculateResponse"> <part name="parameters" element="tns:CalculateResponse" /> </message> - <message name="BadInputFault"> <part name="fault" element="tns:BadInputFault" /> </message> - <!-- port --> - <portType name="SpecificCalculatorPortType"> - <operation name="calculate"> <input message="tns:CalculateRequest" /> <output message="tns:CalculateResponse" /> <fault name="BadInputFault" message="tns:BadInputFault" /> </operation> </portType> - <!-- binding --> - <binding name="SpecificCalculatorBinding" type="tns:SpecificCalculatorPortType"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /> - <operation name="calculate"> <soap:operation soapAction="/calculate" style="document" /> - <input> <soap:body use="literal" /> </input> - <output> <soap:body use="literal" /> </output> - <fault name="BadInputFault"> <soap:fault name="BadInputFault" use="literal" /> </fault> </operation> </binding> - <!-- service --> - <service name="SpecificCalculatorService"> - <port name="SpecificCalculatorPort" binding="tns:SpecificCalculatorBinding"> <soap:address location="http://ec2-67-202-9-24.compute-1.amazonaws.com:8180/calculator/services/SpecificCalculatorService" /> </port> </service> </definitions>
That wsdl generates the following APEX class
which generates the following SOAP on the request:
Unfortunately, the webservice wants:
or :
The problem is in the declaration of the Namespaces. The elements within the complex types do not have a namespace and therefore must be removed from their parent's namespace by the null namespace declaration xmlns='' or the use of the q0: specification on the tags. I cannot seem to control the generation of the soap by editing the apex_schema_type_info declaration in the apex code. All changes I make to that part of the apex code seem to be completely ignored.
WebServiceCallout.invoke(
this,
request_x,
response_map_x,
new String[]{endpoint_x,
'/calculate',
'urn:specific_calculator-services-kronos-com:specific_calculator',
'CalculateRequest',
'urn:specific_calculator-services-kronos-com:specific_calculator',
'CalculateResponse',
'specificCalculatorServicesKronosCom.CalculateResponse_element'}
);
In generated Apex it seems that you might be able to change the namespace for the type by modifying the statement highlighted below
public class CalculateRequest_element {
public DateTime start_date;
public specificCalculatorServicesKronosCom.ScheduledShiftType[] scheduled_shifts;
private String[] start_date_type_info = new String[]{'start_date','http://www.w3.org/2001/XMLSchema','dateTime','1','1','false'};
private String[] scheduled_shifts_type_info = new String[]{'scheduled_shifts','urn:specific_calculator-services-kronos-com:specific_calculator','ScheduledShiftType','0','-1','false'};
private String[] apex_schema_type_info = new String[]{'urn:specific_calculator-services-kronos-com:specific_calculator','true'};
private String[] field_order_type_info = new String[]{'start_date','end_date','now','punches','pay_code_edits','scheduled_shifts'};
}
But you can change both parameters or even remove the declaration and it makes no difference to the generated WSDL.
This is very frustrating. I would love to see some documentation about things like the WebServiceCallout class and the ability to control the namespacing to a finer degree.
service is expecting unqualified elements. Do you have control over this service? Can
you change the service schema to be qualified?: