[Soaplite-devel] RE: SOAP::Lite development

[Byrne R. <by...@ma...>]

I am happy to hear you are coding away.

I too am working on a new WSDL2Perl utility. I will check what I have into
CVS soon, but it is all based upon the WS-I interoperability
demonstration.

http://www.xmethods.net/wsid/

As I stated in my previous email, I think it is important to build
consensus on what the generated code should look like - especially
considering the fact that there are a million and one ways to do anything
in Perl.

I am very curious to see what your perl code looks like given a WSDL that
looks like:

http://www.xmethods.net/wsid-08-2002/wsdl/ISupplier.wsdl

That is the WSDL I am working off of.

By all means, send me what you have!

> Thanks for the assistance. I think that I can be of some help. I have been
> very busy implementing a SOAP::Lite server that would accept and dispatch
> complex types to and from a .NET SOAP server at my job, but we are through
> the worst of it so I am looking forward to spending more time taking some
> of
> the work that I've already done and porting it to the trunk of the
> SOAP::Lite tree (and get some class credit for this too :) ).
>
> I've spent a little time creating a framework where the elements and
> attributes of the wsdl complex types could be laid out similarly to the
> way
> the current stubmaker lays out the endpoint connections. Hooks would be
> created for the message objects and the code will properly serialize the
> data as elements or attributes from a hash that is passed in. It doesn't
> automatically parse the WSDL to generate the array, but it's laid out in a
> way where that would be quite possible. Hopefully, this could be helpful
> in
> the format that we finalize on.
>
> How should we stay in contact? Do you use IM or IRC or should we stick to
> email for now? Speaking of which, use cal...@ya... in the
> future, since that is my personal e-mail address. I also use the same name
> under YIM.
>
> I'm anxious to continue with this and I'm looking forward to continuing
> this
> work. In the meantimes I'll continue working on extending the stubmaker to
> generate that code that I described above.
>
> -Calvin
>
>
> -----Original Message-----
> From: Byrne Reese [mailto:by...@ma...]
> Sent: Wednesday, October 08, 2003 11:38 PM
> To: calvin_g_smith
> Subject: Re: SOAP::Lite development
>
>
> We are in desparate need of this help. In fact, some folks at ActiveState
> have volunteered to donate an XSL script that could be used to generate
> SOAP::Lite stub-code.
>
> There is still some planning work that needs to be done, and in all
> honesty, it is the most important work to do.
>
> What we need to do is create the reference code that will serve as a basis
> for what all SOAP::Lite code SHOULD look like. In other words, given a
> very standard WSDL - in this case, the WSDL for the WSI Interoperability
> Demonstration - we need to author the canonical perl code for it. Using
> that as a template, we would modify the XSL stylesheet to create stubs
> given any WSDL.
>
> If this is something you would still like to embark on, your help would be
> hugely appreciated! I would be happy to work with you and collaborate - it
> is indeed something that is on my plate to do... I could act as a
> reviewer, or co-developer, or whatever. Just let me know how you would
> like to proceed.
>
>> I am interested in getting involved with the development of SOAP::Lite
>> potentially as part of a school project. I was looking at the lack of
>> complexType support in the stubmaker.pl script and maybe adding
>> support for that. Please let me know whether that's already done or in
>> progress and I don't know about it yet or if it's available as a
>> project that can be done.
>>
>> Thanks in advance,
>>
>> -Calvin
>>
>> PS Whether I can do this as a school project is dependent of course on
>> approval from my teacher but I would find out fairly quickly.
>>
>>
>
>
> ^byrne :/
>
>


^byrne :/