Null Date Issue

Question

Hi,
I am trying to assign a Null Date to PartnerLink Variable element. The partnerlink is to a Websphere Web Service. In my assignment, I simply do not create a copy operation to the variable element. At runtime this then has the <warrantyDate/> in element. However, the partnerlink errors at runtime with String exception error. It appears as if it is treating the null date element as a string and I am gettting a type mismatch error.
Is there any way of passing a null date and not getting a string error?
Thanks
Error Details below:
<messages><input><Equipment_Create_Input><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="parameters"><create xmlns="http://equipment.ellipse.enterpriseservice.mincom.com">
<connectionId>
<id xmlns="http://ellipse.enterpriseservice.mincom.com">20ceb39a9a0495e1:6587b9ea:11406107bf7:-7ff1</id>
</connectionId>
<requestParameters>
<location>UPRN100061</location>
<equipmentNo/>
<districtCode>0001</districtCode>
<equipmentRef/>
<serialNumber/>
<partNo/>
<ctaxCode/>
<equipmentNoDescription2>Iain Testing 27072007</equipmentNoDescription2>
<equipmentNoDescription1>BPEL SPID Creation</equipmentNoDescription1>
<equipmentClassif16/>
<drawingNo/>
<equipmentTypeDescription/>
<equipmentLocation/>
<plantNo/>
<equipmentClassif3/>
<poNo/>
<operatorId/>
<equipmentClassif/>
<equipmentStatus>OP</equipmentStatus>
<traceableFlg>false</traceableFlg>
<stockCode/>
<compCode/>
<equipmentClass>20</equipmentClass>
<plantNames/>
<shutdownEquipment/>
<equipmentClassif13/>
<equipmentClassif14/>
<taxCode/>
<purchasePrice>0</purchasePrice>
<purchaseDate>2007-07-27T10:41:47+00:00</purchaseDate>
<equipmentType/>
<equipmentClassif18/>
<custodian/>
<equipmentClassif17/>
<costSegLgth>0</costSegLgth>
<warrantyDate/>
<equipmentClassif19/>
<equipmentGrpId/>
<equipmentClassif0/>
<equipmentClassif15/>
<mnemonic/>
<equipmentClassif1/>
<equipmentClassif8/>
<activeFlag>true</activeFlag>
<accountCode>SWA013093000</accountCode>
<equipmentClassif11/>
<equipmentClassif9/>
<parentEquipmentRef/>
<equipmentClassif10/>
<warrStatVal>0</warrStatVal>
<prodUnitItem>false</prodUnitItem>
<equipmentClassif12/>
<plantCodes/>
<originalDoc/>
<segmentUom/>
<colloqName/>
<equipmentClassif2/>
<inputBy>INTEG</inputBy>
<conAstSegEn>0</conAstSegEn>
<warrStatType/>
<equipmentClassif7/>
<equipmentClassif4/>
<parentEquipment/>
<equipmentClassif5/>
<costingFlag>A</costingFlag>
<equipmentClassif6/>
<itemNameCode/>
<conAstSegSt>0</conAstSegSt>
<expElement/>
<plantCode4/>
<plantCode2>22</plantCode2>
<plantCode1>01</plantCode1>
<plantCode0>22222222</plantCode0>
<plantCode5/>
<copyEquipment/>
<plantCode3/>
</requestParameters>
<returnWarnings>0</returnWarnings>
</create>
</part></Equipment_Create_Input></input><fault><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>Server.generalException</code>
</part><part name="summary"><summary>java.lang.StringIndexOutOfBoundsException: String index out of range: 0 To see the message containing the parsing error in the log, either enable web service engine tracing or set MessageContext.setHighFidelity(true).</summary>
</part><part name="detail"><detail><detail/>
</detail>
</part></remoteFault></fault></messages>

Answer 1

We had the same problem. To solve it you need to do the following:
1. 'break' the graphical design option of the xslt by removing the processing instruction from the xslt. ( <?oracle-xsl-mapper ..... ?>). After removing and saving the xslt, restart JDeveloper to prevent it from opening the xslt in design mode.
2. Add the namespace xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" if it's not already there..
3. for all elements that you need to send without content ( <element/> ), add an attribute xsi:nil="1" ( <element xsi:nil="1" /> ).
HTH,
Bas