ONVIF:...sponse(3pm)

πŸ“¦
version 1.36.37 Β· 5 versions
, in ubuntu resolute, ubuntu stonking

✨ NAME ✨

Okay bestie, gather round, because today we're talking about ONVIF::Device::Elements::CreateCertificateResponse β€” yes, that whole mouthful, and yes, the manual page for it is the one you're reading right now, filed under ONVIF::Device::Elements::CreateCertificateResponse(3pm) in the perl section of your man pages. πŸŽ€


πŸ’… DESCRIPTION πŸ’…

So here's the tea: this is a Perl data type class for the XML Schema defined element CreateCertificateResponse, and it lives in the namespace http://www.onvif.org/ver10/device/wsdl. That's it, that's the whole vibe β€” it's a little Perl object that stands in for one specific XML element so you don't have to wrestle raw XML with your bare hands. Iconic, honestly. ✨


🌸 PROPERTIES 🌸

These are the properties you can reach with the get_PROPERTY / set_PROPERTY methods. (Yes, the method names are literally built from the property names. It's giving ✨automation✨.)

  • NvtCertificate β€” the one and only property on this element, and you poke at it like so:
$element->set_NvtCertificate($data);
$element->get_NvtCertificate();

πŸ¦‹ METHODS πŸ¦‹

new

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

It's the constructor, bestie. You hand it $data and it builds you the element. πŸ’–

Here's the data structure you may pass to new() β€” every key, every nested type, all of it, no cap:

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

πŸ‘‘ AUTHOR πŸ‘‘

Generated by SOAP::WSDL. Machine-made, but make it fashion. πŸ’…


And that's a wrap, babe 🫢 β€” this page was served fresh by perl v5.40.1 and stamped 2026-02-01. Go forth and create those certificate responses, main character. πŸŒˆπŸ’œ
πŸ“¦ where this page comes from