nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem with createNodeResponse

Kapil_Chaudhari

Hi all,

I am having a problem related to createNodeResponse. The structure for METADATA is as follows:

As we can see, there is no "Values" element defined under metadat -> AttributeGroups -> Values

But, I get a response which has this "Values" tag under Values which is not defined in the structure and it is causing an exception(Unmarshal exception since the defined structure doesn't have "Values" element. The response is:

<ns2:AttributeGroups>
          <ns2:DisplayName>zWorkflow Control</ns2:DisplayName>
          <ns2:Key>446232.1</ns2:Key>
          <ns2:Type>Category</ns2:Type>
                 <ns2:Values xsi:type="StringValue" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                     <Description>Workflow Activator</Description>
                     <Key>446232.1.2</Key>
                     <Values>Review</Values>
                  </ns2:Values>
</ns2:AttributeGroups>

Can you please suggest how to get around this problem.

Thanks,

Kapil

Find more posts tagged with

Comments

Kapil_Chaudhari

Hi Scott/Jason/Kyle,

Can I please get some clarification on this? Why the actual response is different than the definition in the XSD?

This is the definition in the XSD:

<xs:complexType name="ServiceDataObject2" abstract="true" />
<xs:complexType name="DataValue">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:ServiceDataObject2">
        <xs:sequence>
          <xs:element minOccurs="0" maxOccurs="1" name="Description" type="xs:string" />
          <xs:element minOccurs="0" maxOccurs="1" name="Key" type="xs:string" />
       </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>

But when we receive the response, it has extra <values> tag along with Description and Key and it fails to unmarshal.

Thanks,

Kapil

sgrasley

Hi, Kapil.

That Values element is coming from the StringValue type, which derives from DataValue. The XSD you've shown is for DataValue, not StringValue.

What tool are you using?

Thanks,

Scott

Kapil_Chaudhari

I am using SOAP UI and I can see the extra"Values" tag in the response which shouldn't be there. We use a JAVA based integration tool. It also fails to unmarshal the response on to the structure which was created from the XSD because of the extra"Values" tag.

sgrasley

Hi, Kapil.

The Value element comes from the StringValue XSD:

Perhaps SOAP UI and/or the Java-based integration tool is using the wrong XSD? It sounds like it isn't respecting the xsi:type element...

Thanks,

Scott

Kapil_Chaudhari

Hi Scott,

As per the XSD, it is referring to "DataValue" and not "StringValue". Please correct me if I am wrong.

<xs:complexType name="Metadata">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:ServiceDataObject1">
        <xs:sequence>
          <xs:element minOccurs="0" maxOccurs="unbounded" name="AttributeGroups" type="tns:AttributeGroup" />
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>
<xs:complexType name="AttributeGroup">
    <xs:complexContent mixed="false">
      <xs:extension base="tns:ServiceDataObject1">
        <xs:sequence>
          <xs:element minOccurs="0" maxOccurs="1" name="DisplayName" type="xs:string" />
          <xs:element minOccurs="0" maxOccurs="1" name="Key" type="xs:string" />
          <xs:element minOccurs="0" maxOccurs="1" name="Type" type="xs:string" />
          <xs:element xmlns:q4="urn:Core.service.livelink.opentext.com" minOccurs="0" maxOccurs="unbounded" name="Values" type="q4: DataValue" />
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
</xs:complexType>

And as shown in previous post, "DataValue" only has key and description.

Do I have to modify the XSD?

Thanks,

Kapil

sgrasley

Hi, Kapil.

StringValue extends PrimitiveValue, which in turn extends DataValue.

<xs:complexType name="StringValue">
<xs:complexContent mixed="false">
    <xs:extension base="tns:PrimitiveValue">
      <xs:sequence>
        <xs:element minOccurs="0" maxOccurs="unbounded" name="Values" type="xs:string"/>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

<xs:complexType name="PrimitiveValue">
<xs:complexContent mixed="false">
    <xs:extension base="tns:DataValue"/>
</xs:complexContent>
</xs:complexType>

<xs:complexType name="DataValue">
<xs:complexContent mixed="false">
    <xs:extension base="tns:ServiceDataObject">
      <xs:sequence>
        <xs:element minOccurs="0" maxOccurs="1" name="Description" type="xs:string"/>
        <xs:element minOccurs="0" maxOccurs="1" name="Key" type="xs:string"/>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

I think the tool you're using to unmarshal the message isn't recognizing that extension.

Thanks,

Scott

Kapil_Chaudhari

Thanks Scott. Can you think of any workaround for this? I haven't had any issues with other XSDs(non-opentext webservice XSDs).

Kapil

sgrasley

Hi, Kapil.

I haven't had to work around this at all using frameworks like JAX-WS and WCF; it works fine. What tool are you using?

Thanks,

Scott

Kapil_Chaudhari

I am using a tool called JCAPS from Oracle/SUN. When I create a JCAPS message structure from the XSD, I don't see that "Values" tag as shown in my very first post. I am not sure what approach should I take. In worst case, I will have to remove "values" tag manually from the message and then unmarshal it. I would like to fix it on the XSD level so that I can re-create JCAPS structure and don't have to manually alter the message.

Thanks,

Kapil

sgrasley

Hi, Kapil.

What version of JCAPS are you using?

Thanks,

Scott

Kapil_Chaudhari

Scott,

We are using JCAPS 6.2 right now.

Thanks,

Kapil

Kapil_Chaudhari

Hi Scott,

Are you familiar with JCAPS since you asked? Is there anyway to fix this issue?

Thanks,

Kapil

sgrasley

Hi, Kapil.

No, sorry, I'm not familiar with JCAPS. I saw a reference to an issue with extensions in XSDs, but that was an earlier version than the one you're using.

It does sound to me like an issue with JCAPS, but I have to admit my lack of familiarity with the tool...

Thanks,

Scott

Kapil_Chaudhari

It might still be there in this version. Can you tell me what steps did they take to resolve that issue?

Thanks,

Kapil

sgrasley

Hi, Kapil.

Sorry, I'm not familiar with JCAPS. I noticed a fix that sounded relevant in the release notes for version 5.1.3.

Are you creating stubs using soapUI? Or is the structure created by JCAPS? Are you able to use JAX-WS instead of JCAPS?

Thanks,

Scott

Kapil_Chaudhari

Hi Scott,

We have recently moved from JCAPS 5.1.3 to 6.2. JCAPS take XSD and create a structure called Object Type Definition (OTD) which is used to unmarshal the response of the webservice.

Can you please tell me where I can take a look at that issue with 5.1.3? I might find something useful tips from that conversation.

Thanks,

Kapil

sgrasley

Hi, Kapil.

I didn't look very closely, but there are some issues mentioned here that could be relevant:

http://wikis.sun.com/display/JavaCAPS/Java+CAPS+5.1.3+Update+Release+3

6647415, 6712457

Again, I only took a cursory glance as JCAPS is not something I'm familiar with.

Thanks,

Scott

Kapil_Chaudhari

Hi Scott,

I am still not sure if this is a problem with JCAPS or XSD. When I look at the XSD for createNodeResponse, the AttributeGroup (metadata tag) is referring to q4:DataValue which is from DocumentManagement_schema3.xsd.

In this Schema3.xsd, DataValue only has one extension which is that of ServiceDataObject2 (abstract = true).

Datavalue is not extending StringValue which is why nothing will be inherited from StringValue to DataValue. Can you please explain where am I making a mistake in understanding?

Thanks,

Kapil

Kapil_Chaudhari

Hi Scott/Jason,

Any explanation on this? I would really appreciate it.

Thanks,
Kapil

sgrasley

Hi, Kapil.

StringValue extends DataValue, not the other way around.

Since the XSD works fine in other frameworks (like JAX-WS, WCF), I suspect this is a problem with JCAPS. Furthermore, there are bugs listed in the JCAPS release notes about XSD extensions, so perhaps there is still something wrong.

Thanks,

Scott