I agree that the way to fix SOAP::Lite is to replace it. This is not to say SOAP::Lite is not an excellent package or the people who built it didn't do us all a great service. But replacing one component with a new one, and new ideas, is a time-honored tradition that works in the Open Source world.

What should the SOAP::Lite replacement look like?

• It should make the easy things easy and the hard things possible.
• It should be as clean and satisfying for a Perl fan to use as the Ruby, Java, etc. approaches are satisfying to users of those languages.
• It should do everything the SOAP standard demands, including complex types.

If anyone wants to kick off a mailing list, or SF project, or anything else to make progress on these goals, please let me know.