[Openoss-discuss] FW: SOAP request - PM Collection Job - createMeasurementCollectionJobRequest

[Flauw, M. <Mar...@hp...>]

Dear all,

Can you help with the problem below?

One of the attribute of the Collection Job is MonitoredObjectsCriteria which is an empty abstract class. It has 2 subclasses MonitoredObjectClass and MonitoredObjectCriteria.

When trying to create a CollectionJob, one of the input arguments is a MonitoredObjectCriteria, but for the real creation of an instance, a monitoredObjectClass needs to be provided and this fails.

This can be extended to a more general question of polymorphism on attributes.

Can you help?

Best regards

Marc

From: Stein, Yuval [mailto:Yuv...@te...]
Sent: Monday, April 08, 2013 10:54 AM
To: sam...@wi...; pga...@tm...; Flauw, Marc
Cc: yoa...@my...; vin...@wi...; san...@wi...
Subject: RE: SOAP request - PM Collection Job - createMeasurementCollectionJobRequest

Hi Sam,

You are right. I just sent a post, as we tackled the same issue while trying to test with MYCOM.
Additionally, the same issue exists for the SchedulDefinition.

Best Regards,
Yuval

From: sam...@wi...<mailto:sam...@wi...> [mailto:sam...@wi...]
Sent: Monday, April 08, 2013 11:48 AM
To: pga...@tm...<mailto:pga...@tm...>; Mar...@hp...<mailto:Mar...@hp...>; Stein, Yuval
Cc: yoa...@my...<mailto:yoa...@my...>; vin...@wi...<mailto:vin...@wi...>; san...@wi...<mailto:san...@wi...>
Subject: SOAP request - PM Collection Job - createMeasurementCollectionJobRequest

Hi Pierre/Yuval/Mark,
I am trying to generate a SOAP request for measurementcollectionjobservice#createMeasurementCollectionJobRequest. In which one of the input parameter monitoredObjectsCriteria (Type MonitoredObjectsCriteria) is defined as abstract without any methods.

Although the implementation (MonitoredClassCriteria, MonitoredInstancesCriteria) has the details like monitoredObjectClass, I am not able to pass it in SOAP request as it expects the super class (abstract) with no parameters. Please let me know the details of sample SOAP structure, also let me know if you are able successfully test the web-services interfaces at your end.

pm_cbe_perf_mon.xsd
   <xsd:complexType name="MonitoredObjectsCriteria" abstract="true">
      <xsd:annotation>
         <xsd:documentation>
            <p>A criteria for specifying what monitored objects are referenced by a PM query, both scheduled or ad-hoc.</p>
            <p>This datatype  is  abstract</p>
         </xsd:documentation>
      </xsd:annotation>
      <xsd:sequence/>
   </xsd:complexType>


Should it be as follows having the definitions in the abstract class instead of a marker abstract class?

   <xsd:complexType name="MonitoredObjectsCriteria" abstract="true">
      <xsd:annotation>
         <xsd:documentation>
            <p>A criteria for specifying what monitored objects are referenced by a PM query, both scheduled or ad-hoc.</p>
            <p>This datatype  is  abstract</p>
         </xsd:documentation>
      </xsd:annotation>
      <xsd:sequence>
               <xsd:element name="monitoredObjectClass" type="xsd:string" minOccurs="0" maxOccurs="1">
                  <xsd:annotation>
                     <xsd:documentation>
                        <p>A monitored object class for specifying the set of instances that are referenced by a PM query.</p>
                        <p>This element is generated from an attribute.</p>
                        <p>This attribute  is  optional</p>
                     </xsd:documentation>
                  </xsd:annotation>
               </xsd:element>
    <xsd:sequence/>
   </xsd:complexType>


Current SOAP:

   <soapenv:Body>
      <coll:createMeasurementCollectionJobRequest>
          <coll:createData>
........
........
<coll:monitoredObjectsCriteria/>....Not able to pass the sub-class here.
          </coll:createData>
      </coll:createMeasurementCollectionJobRequest>
   </soapenv:Body>

Regards
Sam

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com<http://www.wipro.com>
Information in this e-mail and its attachments is confidential and privileged under the TEOCO confidentiality terms that can be reviewed here<http://www.teoco.com/email-disclaimer>.