ONVIF:...ficates(3pm)

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

✨ NAME ✨

ONVIF::Device::Elements::LoadCertificates β€” bestie, that's the whole name, and yes it's a mouthful. It's a Perl data type class, and the page you're reading is ONVIF:...ficates(3pm) from the User Contributed Perl Documentation crew. πŸ’…


🌸 DESCRIPTION 🌸

Okay so picture this: it's a Perl data type class for the XML Schema defined element LoadCertificates, and it lives in the namespace http://www.onvif.org/ver10/device/wsdl. That's it. That's the whole job. It exists to represent that one element, and it does it beautifully. No cap. πŸ¦‹


πŸŽ€ PROPERTIES πŸŽ€

These are the properties you can reach with get_PROPERTY / set_PROPERTY methods:

  • NVTCertificate β€” the one and only. Get it, set it, live your truth. πŸ‘‘

Here's how you'd poke at it:

$element->set_NVTCertificate($data);
$element->get_NVTCertificate();

πŸ”₯ METHODS πŸ”₯

πŸ’– new

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

Constructor, babes. It's giving "make me an object." The following data structure may be passed to new():

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

Look at that nesting. She's structured. She's iconic. The CertificateID is a token, the inner Certificate is an ONVIF::Device::Types::BinaryData, and the Data inside that is base64Binary. Chef's kiss, no notes. 😭✨


πŸ‘‘ AUTHOR πŸ‘‘

Generated by SOAP::WSDL. Not by a human hand, just pure machine-made slay. πŸ€–πŸ’œ


That's the whole page, bestie. Go forth and LoadCertificates. 🌈

This gem of a page came from perl v5.40.1, dated 2026-02-01 β€” so it's fresh, it's current, and it said everything it needed to say. Periodt. πŸŽ€πŸ’…

πŸ“¦ where this page comes from