Menu
▾
▴
soaplite-devel — SOAP::Lite developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(7) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
(1) |
Apr
(23) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(2) |
| 2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2006 |
Jan
(1) |
Feb
(6) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(4) |
Sep
(4) |
Oct
(4) |
Nov
(6) |
Dec
(3) |
| 2007 |
Jan
(1) |
Feb
(6) |
Mar
|
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
(12) |
Oct
(19) |
Nov
(7) |
Dec
(7) |
| 2008 |
Jan
(14) |
Feb
(27) |
Mar
(23) |
Apr
(5) |
May
|
Jun
(1) |
Jul
|
Aug
(9) |
Sep
(22) |
Oct
|
Nov
(5) |
Dec
(7) |
| 2009 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(3) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(8) |
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
(4) |
Aug
(2) |
Sep
(5) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(1) |
Mar
(3) |
Apr
|
May
(7) |
Jun
(3) |
Jul
(8) |
Aug
(9) |
Sep
(5) |
Oct
(4) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(6) |
Oct
(20) |
Nov
(15) |
Dec
(11) |
| 2013 |
Jan
(1) |
Feb
(40) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Mark F. <mar...@ea...> - 2004-04-14 02:56:00
|
Before I get too far into my own UDDI implementation, I'd like to know if there is a way to make the existing UDDI::Lite accomodate UDDI v2, or what significant drawbacks you've found with it. I've looked at the code and it's so brief that I don't understand what it's doing or how. What I'm working on will be significantly larger -- but I'll understand it. :) However, this makes me wonder if I'm on the wrong track. Maybe I'm not taking advantage of something in SOAP::Lite the way the existing UDDI::Lite does? Mark |
|
From: Byrne R. <by...@ma...> - 2004-04-13 20:12:25
|
Keep in mind, I can package and distribute a UDDI::Lite with SOAP::Lite... which is probably better than SOAP::UDDI. As for your last comment - this is perfect feedback for the SOAP::Lite API... to be able to proxy options passed to the 'use SOAP::Lite' call... I think there are a number of ways to do this, so let's chat about it when you have a chance. Let's also move this thread to the soaplite-devel mailing list as sourceforge... Mark Fuller wrote: > Hi Byrne, > > I'm pleased you would like UDDI to be part of the SOAP distribution. I > didn't want to do my own distribution. > > I agree with you that "WS::" conveys the natural hierarchy. It may not > be easy to change after the current hierarchy has been widely used. > > You can plan on hearing from me in around 2 weeks. I'll need someone's > time to review it. There are a couple of things I need someone > experienced with SOAP::Lite to consider. For example, > > - I put the SOAP::Lite instantiation in SOAP::UDDI. I like the idea > of making it easier to use (don't have to think about SOAP::LIte). > But, it makes it harder to alter the "use SOAP::Lite" options. For > example the trace options if someone needs to debug what is happening. > > Until then, > Mark > > > ------------------------------------------------------------------------ > Do you Yahoo!? > Yahoo! Tax Center - File online by April 15th > <http://taxes.yahoo.com/filing.html> |
|
From: Andrew P. <an...@pi...> - 2004-03-31 23:55:11
|
I am using SOAP::Lite to access a Windows 2003 server with NTLM authentication required. I've looked at the hacks in the cookbook, but I don't think they will suffice, because I need to use NTLM not just for the SOAP calls, but for accessing the WSDL file. Generally, I would really like to be able to pass in my own LWP::UserAgent to use for all web requests. This allows for both great flexibility and better use of resources. Would it be hard to add this? Can anyone suggest an approach? In this case, I think I can work-around the problem by downloading the WSDL file by hand, and giving it SOAP::Lite as a file: URL; then using the SOAP::Transport::HTTP::Client::get_basic_credentials (or another) trick for the SOAP requests. But I hope I can come up with a better solution in the end. Andrew |
|
From: Byrne R. <by...@ma...> - 2003-12-12 09:49:51
|
Remember - this is a development mailing list for developers working on SOAP::Lite. Please use the SOAP Lite users group hosted by Yahoo Groups... Anyway - be sure you have openssl installed and CryptSSLeay. If you have those installed, let me know, and we will try the next thing. > > > I cannot get the HTTPS.pm module to create or install on Redhat Linux 9.0 > or > FreeBSD 4.9. > > > > I am using the following version SOAP-Lite-0.55.tar.gz > <http://prdownloads.sourceforge.net/soaplite/SOAP-Lite-0.55.tar.gz?download> > for Unix/Linux. > > > > All the pre-requisites have been installed and I get no warning errors > when > performing > > > > Make Makefile.PL > > Make > > > > I have said no to the default menu option so that I could enable the > HTTPS > module. > > > > Everything builds fine, but there is not an HTTPS.pm module in the > SOAP/Transport directory. > > > > > > When I run my SOAP server using the SOAP::Transport::HTTPS::Daemon line, I > get > > > > Can't locate SOAP::Transport::HTTPS.pm in @INC ..... > > > > Suggestions? > > ^byrne :/ |
|
From: Machuca, A. <Ada...@gd...> - 2003-12-10 16:15:00
|
I cannot get the HTTPS.pm module to create or install on Redhat Linux 9.0 or FreeBSD 4.9. I am using the following version SOAP-Lite-0.55.tar.gz <http://prdownloads.sourceforge.net/soaplite/SOAP-Lite-0.55.tar.gz?download> for Unix/Linux. All the pre-requisites have been installed and I get no warning errors when performing Make Makefile.PL Make I have said no to the default menu option so that I could enable the HTTPS module. Everything builds fine, but there is not an HTTPS.pm module in the SOAP/Transport directory. When I run my SOAP server using the SOAP::Transport::HTTPS::Daemon line, I get Can't locate SOAP::Transport::HTTPS.pm in @INC ..... Suggestions? |
|
From: Kandidates.com <in...@ka...> - 2003-12-04 19:50:55
|
Perl Programmer with SOAP:Lite Experience (telecommute) We are looking for someone who know SOAP and SOAP::Lite very well and can spend a few hours getting my team up to speed. This is the type of question we are looking for the answer to: http://www.kandidates.com/misc/soap.htm Please send resume and rate to jo...@ka... |
|
From: Byrne R. <by...@ma...> - 2003-12-01 15:37:47
|
wsdl2perl is coming along (see last email)... here are some of the changes you will see in the upcoming release of SOAP::Lite 0.65: + Made SOAP::Serializer->readable actually produce readable XML! + Made XML Schema 2001 the default schema + Added support for [almost] all XML Schema 2001 built-in datatypes + Added necessary subroutinues to support wsdl2perl project + Added format_datetime to SOAP::Utils + Added register_ns subroutine to SOAP::Serializer + Added find_prefix subroutine to SOAP::Serializer + Added use_prefix subroutine to SOAP::Serializer The last three subroutines are to better support wsdl2perl - the very last subroutine (use_prefix) has the added benefit of helping .NET compatibility by allowing users to produce XML that looks like this: <foo xmlns="urn:bar" /> as opposed to this: <namesp1:foo xmlns:namesp1="urn:bar" /> ^byrne :/ |
|
From: Byrne R. <by...@ma...> - 2003-12-01 15:34:18
|
There is a huge need for this tool in the SOAP::Lite community - if not functionally, then educationally. I am gearing up for the first alpha release of the wsdl2perl tool. It includes support for RPC encoded servers only, and produces client-side code only. Major tasks to see this thing progress to a beta are as follows, and I really need help testing this: * testing, testing, and more testing * support doc/literal style encoding (this may mean writing a whole new serializer and deserializer) * development of a more robust set of unit tests In the meantime, I just checked in the latest code into CVS. You will need to get a nightly build of SOAP::Lite (soon to be released as 0.65) as well as wsdl2perl obviously. ^byrne :/ |
|
From: Byrne R. <by...@ma...> - 2003-11-25 15:12:49
|
I have checked in the latest round of updates to WSDL2PERL. I am focusing on RPC style encoding and decoding for now. This round of updates also requires that the latest version of SOAP::Lite also be checked out an installed. Changes include: * new format_datetime subroutine * new use_prefix subroutine - for .NET compatibility WSDL2PERL is at a point right now where it is beginning to pass a first set of basic unit tests. What remains you ask? Simple... * figure out a way to have all the namespaces used in an envelope collected and serialized in the Envelope element. * produce a find_nsprefix subroutine which when given a URI will return the corresponding NS prefix. This will help in automatic type resolution ^byrne :/ |
|
From: Byrne R. <by...@ma...> - 2003-11-19 00:07:57
|
The wsdl2perl module is now available... it sometimes takes a while for the code to be distributed out to the CVS servers for distribution... Its there now. > Alasdair Allan writes: > > > > > cvs server: cannot find module `wsdl2perl' - ignored > > > cvs [checkout aborted]: cannot expand modules > > > > Same here... > > It's appeared now. Looking forward to seeing what it can do. > > -- > Michael Brader mic...@nt... > Senior Software Developer (Unix) ntl:ipd > Hook 01256 75(3413) > > > > ------------------------------------------------------- > This SF. Net email is sponsored by: GoToMyPC > GoToMyPC is the fast, easy and secure way to access your computer from > any Web browser or wireless device. Click here to Try it Free! > https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl > _______________________________________________ > Soaplite-devel mailing list > Soa...@li... > https://lists.sourceforge.net/lists/listinfo/soaplite-devel > > ^byrne :/ |
|
From: Michael B. <mic...@nt...> - 2003-11-17 19:26:30
|
Alasdair Allan writes: > > > cvs server: cannot find module `wsdl2perl' - ignored > > cvs [checkout aborted]: cannot expand modules > > Same here... It's appeared now. Looking forward to seeing what it can do. -- Michael Brader mic...@nt... Senior Software Developer (Unix) ntl:ipd Hook 01256 75(3413) |
|
From: Alasdair A. <aa...@as...> - 2003-11-17 16:32:49
|
> > cvs -z3 -d:pserver:ano...@cv...:/cvsroot/soaplite co > > wsdl2perl > > $ /usr/bin/cvs -z3 -d:pserver:ano...@cv...:/cvsroot/soaplite co wsdl2perl > > cvs server: cannot find module `wsdl2perl' - ignored > cvs [checkout aborted]: cannot expand modules Same here... Al. -- Dr. A. Allan, School of Physics, University of Exeter |
|
From: Michael B. <mic...@nt...> - 2003-11-17 15:55:21
|
Byrne Reese writes: > cvs -z3 -d:pserver:ano...@cv...:/cvsroot/soaplite co > wsdl2perl $ /usr/bin/cvs -z3 -d:pserver:ano...@cv...:/cvsroot/soaplite co wsdl2perl cvs server: cannot find module `wsdl2perl' - ignored cvs [checkout aborted]: cannot expand modules :-( -- Michael Brader mic...@nt... Senior Software Developer (Unix) ntl:ipd Hook 01256 75(3413) |
|
From: Byrne R. <by...@ma...> - 2003-11-17 15:40:18
|
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/soaplite co wsdl2perl ^byrne :/ |
|
From: Byrne R. <by...@ma...> - 2003-11-17 15:17:48
|
I wanted to inform the SOAP::Lite community, that the first checkin of the wsdl2perl utility has been made. It has not been packaged for distribution yet, as it is still in a pre-alpha phase... and will most likely not work for most people - if not all. The utility uses Perl's Template module to generate client side (and ultimately server side as well) code stubs for call a SOAP based Web service using SOAP::Lite. This effort is serving as major point of feedback to SOAP::Lite itself and will be informing future development efforts. Until the module stablizes, all future discussion should take place on the SOAP::Lite developer mailing list: soa...@li... I checked in the module to CVS on sourceforge. To retrieve it, run the following cvs command: > export CVS_RSH=ssh; > cvs -d:ext:ano...@cv...:/cvsroot/soaplite co wsdl2perl The code has not yet appeared in the browsable CVS repos. online, but I imagine it just takes a little time. Anyway, that's it. I am just pleased to let the community know that development continues. ^byrne :/ |
|
From: Byrne R. <by...@ma...> - 2003-10-28 19:17:13
|
I will try and get things checked in this weekend. I am doing a presentation in November on SOAP::Lite for the Salesforce.com conference here in the SF Bay Area... and it needs to be working by then. But anyway - there are a number of people tackling this problem, from a number of different perspectives - I hope we can corral them all before we have to many divergent implementations. What I will be checking into CVS will be the ISupplier perl module, which will serve as the base reference for the code generated by the wsdl2perl utility. I have gotten the format for all custom deserializers - which is quite useful, and for all the complex types. What is left is to create a new serializer for SOAP::Lite which encodes arrays and other basic data types in a more standards-compliant and friendly way. Things are looking good though - with any luck I will have the whole thing done by this weekend. Then it is just a matter of testing the implementation, and adding some features that might help differentiate SOAP::Lite from other toolkits - like WS-Security support or something to that effect. Thoughts? > > Byrne, > >> 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. > > Thats good news, do you a rough date when you think you'll have something > you're willing to share? > > I'm just about to sit down and try and fix WSDL::Generator, or rather > Class::Hook which is what seems to be what the problem is, to work with > Perl 5.8.1. > > The AUTOLOAD bug has gone away now we're post-5.8.0, but Class::Hook now > SEGV's. It looks vaguely fixable, so I'm going to poke around in the > internals at the weekend and see if I can get it going again... > > Cheers, > Al. > > > ^byrne :/ |
|
From: Byrne R. <by...@ma...> - 2003-10-28 14:52:21
|
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 :/ |
|
From: Roland M. <ro...@mo...> - 2003-07-29 17:56:30
|
with kind regards, Mit freundlichen Gruessen, Roland Moriz -- Muenchen/Germany - http://www.roland-moriz.de/ |
113 messages has been excluded from this view by a project administrator.
