DSP - how to use Function Library

Question

hi all,
ALDSP is returning the following error code:
*weblogic.xml.query.exceptions.XQueryDynamicException: ld:br/com/DSL.ds, line 59, column 274: {err}XP0002 [{bea-err}XP0002a]: Current node needed, but not defined (or $ missing preceding a variable name)*
I created a physical data source(DSP) based on a oracle function.
In my Logical data source (DSL), I have the following code:
for $bla in proc:BLABLA_MYFUNCTION($endereco/COD_COMPL1,$endereco/TXT_COMPL1,$endereco/COD_COMPL2,$endereco/TXT_COMPL2,$endereco/COD_COMPL3,$endereco/TXT_COMPL3,$endereco/COD_COMPL4,$endereco/TXT_COMPL4,null,null,null,null,null)
return
<ns1:Address>
<ns1:tipoEndereco?>a constant string</ns1:tipoEndereco>
<ns1:endereco?>
<end:numeroEndereco?>{fn:data($endereco/NUM_ENDERECO)}</end:numeroEndereco>
          *<end:complemento?>{fn:data($bla)}</end:complemento>*
<end:referencia?>{fn:data($imovel/TXT_REFERENCIA)}</end:referencia>
</ns1:endereco>
</ns1:Address>
i tried to use
+<complemento>+
+                    {+
+                    for $x in fun:FNTH_OBTEM_ENDER_PRINCIPAL($EQUIPAMENTO/ID_EQUIPAMENTO)+
+                    return $x+
+               }+
+                    </complemento>+
instead, but i got the same error.
does anyone can help me?
Edited by: virgulino on Jul 6, 2009 5:44 PM
Edited by: virgulino on Jul 6, 2009 6:01 PM

Answer 1

A variant is a very specific LabVIEW datatype (really a C++ type object internally) and trying to pass that to a function, which excepts a flat memory pointer there, for sure will crash very quickly.
As to endianess, yes Unflatten will be able to adjust for endianess, which in this case however is most likely exectly NOT what you want. So make sure that the you select native type for the endianess input on Unflatten from String. LabVIEW internally works with whatever is the native endianess, as will most likely your C++ DLL. The platform independent big endian format does only come into play when you receive data streams over some streaming interface like a network connection. Here it is desirable to use an endian format that is independent from the actual platform that generates and consumes the data stream. LabVIEWs default endianes is big endian here.
But as long as you pass data directly to native components like DLLs there is no difference in endianess between what LabVIEW uses and what those components use.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions