When doing XML/XSL stuff that applies to just about any scripting language as Java has always been the reference implementation for this. When leaving the XML space the same is not true. But yes, we have a bit of catching up to do when it comes to XML/XSL/XSLT.
-Rasmus On Mon, 1 Oct 2001, Chris Bailey wrote: > Check out this page of SOAP implementations: > > http://www.soapware.org/directory/4/implementations > > It lists several for PHP, so those may give you a solution. > > This is an interesting issue though, especially in light of you bringing up > Tomcat. I don't mean to start a big flame war over languages, but this is > one thing I struggle with in PHP land too. I've been doing Java stuff for > years, and am just starting to develop a few things in PHP. PHP is fast and > easy to use, and a lot easier to setup than Tomcat (or worse, Apache+Tomcat, > and further, if you have a non-standard directory structure). But, what > I've found so far, is that if I need to do pretty much anything beyond a > simple web app that is mostly a database client, Java just has so many more > libraries and resources available, from SOAP, to XML, XSL, and more. While > it's not true that PHP doesn't have any of this, it just seems there is more > momentum and solidity behind these types of things for Java. > > For example, I'm working on a web app that does a lot of XSL processing, and > immediately I can just grab the various Apache XML and XSL toolkits and get > rolling. On PHP I can look into Sablotron and some stuff, but I don't get a > feeling that I'd have near the level of functionality, and quality (or > solidity/maturity of code) as I would with the various Java based tools. > > > -----Original Message----- > From: Dahnke, Eric [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 01, 2001 10:46 AM > To: 'Chris Bailey' > Cc: '[EMAIL PROTECTED]' > Subject: RE: [PHP] SOAP Tool Kit for PHP > > > > Thanks. That's what I'm doing, and it is working, but it doesn't seem like > it will be very robust, and I don't know if my roll your own will be > compliant with MS SOAP messages and Apache SOAP messages. > > I'm reading the Soap:Envelope and Body XML via the $HTTP_RAW_DATA_POST > variable. It comes as a string. I parse that XML to determine the method to > invode (create, edit whatever). It works, but just seems sketch. Especially > the ack back to the poster. It says 200 OK, because the host and file I'm > posting to are found, but if there is an error in the method or anywhere > else, I'm supposed build the SOAP:Fault XML and send that back. > > I mean all the IP functions in PHP are so nice, and SOAP is an IP service as > well. Why no love for SOAP? > > > > -----Original Message----- > From: Chris Bailey [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 01, 2001 1:30 PM > To: Dahnke, Eric; [EMAIL PROTECTED] > Subject: RE: [PHP] SOAP Tool Kit for PHP > > > You could also consider possibly the reverse of what you're doing. I'm not > sure if it would actually work well, nor can I give you real details on how > to do it, but you can always use Java classes from PHP. Depending on how > much SOAP is needed/used across your site, you could continue with PHP for > the bulk of your site, and just use Java classes to handle the SOAP stuff > when needed. The primary issue I don't know about since I haven't looked > into it, is whether it's reasonable to have PHP receive the initial SOAP > request and how you would then hand it off to the Java classes for > processing, etc. Anyway, just a thought... > > -----Original Message----- > From: Dahnke, Eric [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 01, 2001 8:15 AM > To: [EMAIL PROTECTED] > Subject: [PHP] SOAP Tool Kit for PHP > > > > My god does PHP need one. Or a library of functions to use. > > Yes, I have built in CURL support and am reading the $HTTP_RAW_DATA_POST > variable and rolling my own as they say, but it sure would be nice. I've > seen Manual Lemos' soap classes, and they are cool, but aren't really what I > need. > > PHP is fast, has beautiful syntax and I love it, but I think it needs to > grow up a bit. I don't mean to start a war, but it is true, php needs to > evolve into something beyond a newbie language great for producing db driven > web-sites. > > I wish I could help, and after a few more C classes I will be able to, but > until then, I can only hope some C wizard is producing something like this. > Web-services are going to be big. Independent of .net (*uck MS), but the > messaging (SOAP) paradigm over http is going to be big. How does php fit in > there? > > It looks as though we're headed over to tomcat, and I'm probably going to > bring a bunch of php developers with me. And that sucks, because tomcat is > slow, and it takes twice as long to produce an application w/ non masters > level or big time CS people. > > The first thing I'm going to try though is running php as a servlet under > tomcat, but it's only to get at the apache soap tools. See what I mean. > > Thanks to all the php developers. 'gards - Eric > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > To contact the list administrators, e-mail: [EMAIL PROTECTED] > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > To contact the list administrators, e-mail: [EMAIL PROTECTED] > > > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
