cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X

Different out when using the XMLAPI with Java and CLI

ptc-6557619
1-Newbie

Different out when using the XMLAPI with Java and CLI

Hi,

I have an issue regarding the xmlapi option.

My problem is that using the option --xmlapi with the CLI or using com.mks.connect.AbstractCmdRunner.executeWithXML(String[] cmd) with the java API gives different output for the node Response//WorkItems//WorkItem//Field//Value

While the CLI has an additional node TokenValue containing the value of the "Value", the java API gives the value as part of the Value node.

Example:

<Field name="projectType">
<Value dataType="string">
<TokenValue>Variant</TokenValue>
</Value>
</Field>

vs.

<Field name="projectType"> 
<Value dataType="string">Variant</Value>
</Field>

I wonder if one of you has an explanation - or even better a solution to align both outputs to whatever version.

This example is part of result from si sandboxinfo --xmlapi

Veikko

1 REPLY 1
KaelLizak
14-Alexandrite
(To:ptc-6557619)

Hello Veikko,

The --xmlapi option is not published and not supported, and so not guaranteed to match with anything else or remain consistent from one release to the next. It is not recommended for use.

Regards,

Kael


Kind Regards,
Kael Lizak

Senior Technical Support Engineer
PTC Integrity Lifecycle Manager
Top Tags