Thanks for the feedback - you're right, Transport::TCP didn't get
packaged up. I'll address these issues shortly with 1.04.
UDDI::Lite, XML::Parser::Lite, and XMLRPC::Lite were moved to separate
modules and are available on CPAN. They are dependent on SOAP
The complicated Makefile.PL was refactored after multiple reports of
build toolchain issues for SOAP::Lite. You're correct in that now it
is more of a 'SOAP::Heavy' distribution, but I'm in the process of
refactoring that (hence the move to the 1.0x unstable version).
This wasn't a decision I made lightly, but I felt it was necessary to
keep SOAP::Lite compatible with existing toolchains. For advanced
SOAP::Lite implementations using UDDI::Lite, this will require a bit
more work in that you have to install the specific transport/service
modules. However, this makes it easier for normal SOAP::Lite
installations.
Continued feedback is very welcome here :)
On Wed, Aug 14, 2013 at 4:39 AM, hsk@fli-leibniz.de via RT
<bug-SOAP-Lite@rt.cpan.org> wrote:
Show quoted text> Wed Aug 14 07:39:18 2013: Request 87848 was acted upon.
> Transaction: Ticket created by hsk@fli-leibniz.de
> Queue: SOAP-Lite
> Subject: some weirdnesses regarding SOAP-Lite versions 1.0 and up
> Broken in: 1.04
> Severity: (no value)
> Owner: Nobody
> Requestors: hsk@fli-leibniz.de
> Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=87848 >
>
>
> - the 1.0-part of 'HTTP/1.0' in line 609 of lib/SOAP/Transport/HTTP.pm
> must not be incremented during version change of the module :-)
>
> - the changelog says (at 1.0)
> "Merge SOAP::Transport::TCP back into SOAP::Lite"
> and lib/SOAP/Transport/TCP.pm is there on github, but it is not in
> either distributed module SOAP-Lite-1.0x
>
> - without XMLRPC::Lite, installation of bin/XMLRPCsh.pl makes no sense
>
> - t/38-packager.t should be skipped instead of failing if MIME::Parser
> is not installed (see also next item). btw, this test was not used
> at all in 0.71x.
>
> - versions 1.0 and up "require" half-a-dozen additional modules compared
> to 0.71x, shouldn't these be "recommend" at most:
>
> during build of module, 0.71x displayed a list of possible transports /
> services, generated by a sophisticated and maybe not pause / distro /
> whatever automatopatible (the reason it was dropped?) Makefile.PL,
> so "only modules you need for your configuration" would be used.
> with 1.0, almost *all* modules needed for *any* of these proposed
> transports / services are made required modules. otoh, the formerly
> installed by default XMLRPC::Lite, UDDI::Lite, XML::Parser::Lite are
> silently dropped.
>
