I received error message: Unsupported parameter type: 1, if parameter type
oxf:xmlFragment was used for an XML element ApplicationDetails that maps to
MS SQL Server table column Application_Data which is configured as XML type.
On the other hand, if xs:string was used as an substitute, then execution
would be done, but with some side-effect: a) what has been stored into DB is
just space-separated XML content (values), rather than full XML structure,
and b) an error message: Processor execution did not return content, which I
have described in the other post.
Is there any pitfall I should avoid in using oxf:xmlFragment?
FYI, I am using OPS 3.5 M1, and please see associated SQL Processor code as
attached.
Regards,
Spenser
<p:processor name="oxf:sql">
<p:input name="data" href="#instance" debug="true"/>
<p:input name="datasource" href="datasource.xml"/>
<p:input name="config" debug="true">
<sql:config>
<sql:connection>
<sql:execute>
<sql:update>
insert into OPS_PoC (Application_ID, Application_Data)
values (
<sql:param type="xs:string" select="/*/ApplicationID"/>,
<sql:param type="oxf:xmlFragment"
select="/*/ApplicationDetails"/>
)
</sql:update>
</sql:execute>
</sql:connection>
</sql:config>
</p:input>
<p:output name="data" id="data" ref="data"/>
</p:processor>
--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws
Locked
