Hi all,
I'm considering writing a module to allow our web services developers
embed WSDL fragments in POD. I'm envisioning something like this:
=head1 METHODS
=over 4
=item methodname()
some regular documentation
=for wsdl
<xsd:element name="methodname">
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="1" maxOccurs="1" name="result" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
=end
=cut
sub methodname() {
codecodecode;
}
etc.
I have three goals in mind, but only one is a requirement. The
requirement is that I end up with a module that will extract the WSDL
fragments in the =for commands and compose a well-formed WSDL doc from it.
The two optional but highly desirable goals are:
1) to extend perldoc with a formatter that will actually display the =for
wsdl sections when you do 'perldoc SomeModule,' where SomeModule.pm
contains WSDL fragments
2) to write an Apache content handler module that will generate WSDL from
the module, so the WSDL files do not need to be maintained separately from
the perl modules.
So, does anyone out there already have something I can build on? If not,
am I correct in assuming (from what I've read) that subclassing
Pod::Simple is the preferred way to go?
--
Craig Dunigan
Middleware - DoIT
University of Wisconsin, Madison
