kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/net/p5-XML-Compile-WSDL11/Makefile

27 lines
630 B
Makefile
Raw Normal View History

- Add p5-XML-Compile-WSDL11 3.03 XML::Compile::WSDL11 understands WSDL version 1.1. An WSDL file defines a set of messages to be send and received over (SOAP) connections. This involves encoding of the message to be send into XML, sending the message to the server, collect the answer, and finally decoding the XML to Perl. As end-user, you do not have to worry about the complex details of the messages and the way to exchange them: it's all simple Perl for you. Also, faults are handled automatically. The only complication you have to worry about is to shape a nested HASH structure to the sending message structure. XML::Compile::Schema::template() may help you. When the definitions are spread over multiple files you will need to use addWSDL() (wsdl) or importDefinitions() (additional schema's) explicitly. Usually, interreferences between those files are broken. Often they reference over networks (you should never trust). So, on purpose you must explicitly load the files you need from local disk! (of course, it is simple to find one-liners as work-arounds, but I will to tell you how!) WWW: http://search.cpan.org/dist/XML-Compile-WSDL11/
2015-01-15 17:51:50 +01:00
# Created by: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
# $FreeBSD$
PORTNAME= XML-Compile-WSDL11
- Update to 3.05 Changes: http://search.cpan.org/dist/XML-Compile-WSDL11/ChangeLog
2016-03-20 19:36:42 +01:00
PORTVERSION= 3.05
- Add p5-XML-Compile-WSDL11 3.03 XML::Compile::WSDL11 understands WSDL version 1.1. An WSDL file defines a set of messages to be send and received over (SOAP) connections. This involves encoding of the message to be send into XML, sending the message to the server, collect the answer, and finally decoding the XML to Perl. As end-user, you do not have to worry about the complex details of the messages and the way to exchange them: it's all simple Perl for you. Also, faults are handled automatically. The only complication you have to worry about is to shape a nested HASH structure to the sending message structure. XML::Compile::Schema::template() may help you. When the definitions are spread over multiple files you will need to use addWSDL() (wsdl) or importDefinitions() (additional schema's) explicitly. Usually, interreferences between those files are broken. Often they reference over networks (you should never trust). So, on purpose you must explicitly load the files you need from local disk! (of course, it is simple to find one-liners as work-arounds, but I will to tell you how!) WWW: http://search.cpan.org/dist/XML-Compile-WSDL11/
2015-01-15 17:51:50 +01:00
CATEGORIES= net www perl5
MASTER_SITES= CPAN
PKGNAMEPREFIX= p5-
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Create SOAP messages defined by WSDL 1.1
LICENSE= ART10 GPLv1
LICENSE_COMB= dual
Remove ${PORTSDIR}/ from dependencies, categories m, n, o, and p. With hat: portmgr Sponsored by: Absolight
2016-04-01 16:16:16 +02:00
BUILD_DEPENDS= p5-Log-Report>=1.05:devel/p5-Log-Report \
p5-XML-Compile>=1.48:textproc/p5-XML-Compile \
p5-XML-Compile-Cache>=1.03:textproc/p5-XML-Compile-Cache \
p5-XML-Compile-SOAP>=3.16:net/p5-XML-Compile-SOAP
- Add p5-XML-Compile-WSDL11 3.03 XML::Compile::WSDL11 understands WSDL version 1.1. An WSDL file defines a set of messages to be send and received over (SOAP) connections. This involves encoding of the message to be send into XML, sending the message to the server, collect the answer, and finally decoding the XML to Perl. As end-user, you do not have to worry about the complex details of the messages and the way to exchange them: it's all simple Perl for you. Also, faults are handled automatically. The only complication you have to worry about is to shape a nested HASH structure to the sending message structure. XML::Compile::Schema::template() may help you. When the definitions are spread over multiple files you will need to use addWSDL() (wsdl) or importDefinitions() (additional schema's) explicitly. Usually, interreferences between those files are broken. Often they reference over networks (you should never trust). So, on purpose you must explicitly load the files you need from local disk! (of course, it is simple to find one-liners as work-arounds, but I will to tell you how!) WWW: http://search.cpan.org/dist/XML-Compile-WSDL11/
2015-01-15 17:51:50 +01:00
RUN_DEPENDS:= ${BUILD_DEPENDS}
- Sort *_DEPENDS - Add NO_ARCH
2015-06-29 15:50:47 +02:00
NO_ARCH= yes
- Add p5-XML-Compile-WSDL11 3.03 XML::Compile::WSDL11 understands WSDL version 1.1. An WSDL file defines a set of messages to be send and received over (SOAP) connections. This involves encoding of the message to be send into XML, sending the message to the server, collect the answer, and finally decoding the XML to Perl. As end-user, you do not have to worry about the complex details of the messages and the way to exchange them: it's all simple Perl for you. Also, faults are handled automatically. The only complication you have to worry about is to shape a nested HASH structure to the sending message structure. XML::Compile::Schema::template() may help you. When the definitions are spread over multiple files you will need to use addWSDL() (wsdl) or importDefinitions() (additional schema's) explicitly. Usually, interreferences between those files are broken. Often they reference over networks (you should never trust). So, on purpose you must explicitly load the files you need from local disk! (of course, it is simple to find one-liners as work-arounds, but I will to tell you how!) WWW: http://search.cpan.org/dist/XML-Compile-WSDL11/
2015-01-15 17:51:50 +01:00
USE_PERL5= configure
USES= perl5
.include <bsd.port.mk>
Reference in a new issue Copy permalink