WSNoti...esponse(3pm)
π NAME π
WSNotification::Elements::GetMessagesResponse β bestie, it's a whole Perl data type class, and it lives in the User Contributed Perl Documentation corner of your manual pages (you know, the (3pm) girlies) π
β¨ DESCRIPTION β¨
Okay so listen. This class is a Perl data type class for the XML Schema defined element GetMessagesResponse, and that element comes straight out of the namespace http://docs.oasis-open.org/wsn/b-2. That's it, that's the whole vibe. It's the Perl-side glow-up of an XML element, no cap π¦
π PROPERTIES π
You can get at the following properties with the get_PROPERTY / set_PROPERTY methods. Very demure, very mindful, very consistent β¨
NotificationMessage
$element->set_NotificationMessage($data);
$element->get_NotificationMessage();
π Note: the name of this property got altered, because the original didn't match perl's notion of variable/subroutine names. The altered name is used in perl code only β the XML output still uses the original name. So don't panic, your XML is fine, she's just going by a stage name in Perl-land π
πΈ METHODS πΈ
π new
my $element = WSNotification::Elements::GetMessagesResponse->new($data);
Constructor, periodt. You can pass it the following data structure, and look β she's a nested one. Every level matters, so here's the whole tree, exactly as she comes π«Ά
{
NotificationMessage => { # WSNotification::Types::NotificationMessageHolderType
SubscriptionReference => { # WSNotification::Types::EndpointReferenceType
Address => { value => $some_value },
ReferenceParameters => { # WSNotification::Types::ReferenceParametersType
},
Metadata => { # WSNotification::Types::MetadataType
},
},
Topic => { # WSNotification::Types::TopicExpressionType
},
ProducerReference => { # WSNotification::Types::EndpointReferenceType
Address => { value => $some_value },
ReferenceParameters => { # WSNotification::Types::ReferenceParametersType
},
Metadata => { # WSNotification::Types::MetadataType
},
},
Message => {
},
},
}
Like, NotificationMessage is giving WSNotification::Types::NotificationMessageHolderType energy, and inside her there's SubscriptionReference (a WSNotification::Types::EndpointReferenceType with her own Address, ReferenceParameters of type WSNotification::Types::ReferenceParametersType, and Metadata of type WSNotification::Types::MetadataType), a Topic (WSNotification::Types::TopicExpressionType), a ProducerReference (another WSNotification::Types::EndpointReferenceType, same little family of Address / ReferenceParameters / Metadata), and a Message. It's giving nesting dolls, it's giving main character, it's giving π₯
π AUTHOR π
Generated by SOAP::WSDL. Iconic behaviour honestly, she was born fully formed, no human author listed π
And that's a wrap on the WSNoti...esponse page, bestie! This lil' slice of User Contributed Perl Documentation is from perl v5.40.1, dated 2026-02-01 π Take care of her, she's fragile and she's XML ππ
π¦ where this page comes from
- ubuntu resolute: zoneminder 1.36.37+dfsg1-1 Β· GPL-2.0-or-later
- ubuntu stonking: zoneminder 1.36.37+dfsg1-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms