Some time ago, Paul has argued against moving the SOAP::Lite modules
into the SOAP::Lite namespace. After some sleep on the issue, there's
some point in it: Paul wrote a book about SOAP::Lite (and other
modules), and the book would become useless if we changed every name.
However, I think that using alien namespaces is one of the rather
misfortunate design choices in SOAP::Lite. I think we should move
everything we can, but leave the stuff documented in the book.
The list of modules from the book is here:
SOAP::Client
SOAP::Constants
SOAP::Data
SOAP::Header
SOAP::Lite
SOAP::SOM
SOAP::Fault
SOAP::Transport (and all below)
SOAP::Schema
SOAP::Schema::WSDL
SOAP::Serializer - namespace clash with SOAP package
SOAP::Server (and below)
SOAP::Trace
Apache::SOAP
UDDI::Lite
UDDI::Data
UDDI::SOM
UDDI::Serializer
UDDI::Deserializer
As you might have noted, theres one module in the list -
SOAP::Serializer - which causes a conflict with the SOAP distribution
(and effectively prevents using SOAP and SOAP::Lite in the same program
- the one loaded later breaks the other). I think this one should be
moved as well, but a dummy package adde in SOAP::Lite, which does
nothing else than loading SOAP::Lite::Serializer
Martin
|
