ONVIF:...sponse(3pm)

💖 NAME 💖

ONVIF::Device::Elements::GetCACertificatesResponse — bestie, it's a whole Perl class, and it's here to hold your XML. Periodt.

This one's from the User Contributed Perl Documentation corner of the manual-verse, so you know it's community-made with love. 🫶

---

✨ DESCRIPTION ✨

Okay so listen. This is a Perl data type class for the XML Schema element called GetCACertificatesResponse, and that element lives in the namespace http://www.onvif.org/ver10/device/wsdl. That's it, that's the job. It's giving glorified container and honestly? Iconic. 👑

---

🌸 PROPERTIES 🌸

The way that you don't touch these directly, you use the get_PROPERTY / set_PROPERTY methods. Very demure, very mindful. 💅

• CACertificate — the one and only property, no cap.

$element->set_CACertificate($data);
$element->get_CACertificate();

---

🦋 METHODS 🦋

💫 new

my $element = ONVIF::Device::Elements::GetCACertificatesResponse->new($data);

It's the constructor, babes. It builds you the whole element. 🧚

The following data structure may be passed to new():

{
  CACertificate =>  { # ONVIF::Device::Types::Certificate
    CertificateID =>  $some_value, # token
    Certificate =>  { # ONVIF::Device::Types::BinaryData
      Data =>  $some_value, # base64Binary
    },
  },
},

Look at that nesting. It's giving structural elegance, fr fr. Nest carefully, bestie — CACertificate is a ONVIF::Device::Types::Certificate, inside it you got CertificateID (that's a token) and Certificate, which is a ONVIF::Device::Types::BinaryData, and that holds Data (a base64Binary). 😭 So much commitment to the bit and I respect it.

---

👑 AUTHOR 👑

Generated by SOAP::WSDL. No human author, just vibes and codegen. 🤖✨

---

And that's the whole page, bestie! 💖 This lil' manual moment was brought to you by perl v5.40.1, dated 2026-02-01, and it's page ONVIF:...sponse(3pm) in the 3pm section — slay, go forth and set your CACertificate. 🎀🌈⭐