If you want to try, a soap packet looks like this:

<?xml version="1.0"?>
<!--
A SOAP message MUST be encoded using XML
A SOAP message MUST have a SOAP Envelope
A SOAP message CAN have a SOAP header
A SOAP message MUST have a SOAP Body
A SOAP message MUST use the SOAP Envelope namespace
A SOAP message MUST use the SOAP Encoding namespace
A SOAP message must NOT contain a DTD reference
A SOAP message must NOT contain XML Processing Instructions
-->

<soap:Envelope
        xmlns:soap="http://www.w3.org/2001/12/soap-envelope";
        soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding";
>
<soap:Header>
        <!-- optional: contains additional, application
         specific information about the SOAP message -->
</soap:Header>

<soap:Body>
        <!-- mandatory: contains the actual SOAP message
         i.e.regweb data -->
        <soap:Fault>
        <!-- optional: used to provide information about errors that
         occurred while processing the message. By nature this element
         can only appear in answers (response messages) -->
                <faultcode>A code identifying the error
                 <!-- VersionMismatch: Invalid namespace for the SOAP
                 Envelope element -->
                 <!-- MustUnderstand: A child element of the Header
                 element, with the mustUnderstand attribute set to "1",
                 was not understood -->
                 <!-- Client: The message was incorrectly formed or
                 contained incorrect information -->
                 <!-- Server: There was a problem with the server so the
                 message could not proceed -->
                </faultcode>
                <faultstring>The error as a string</faultstring>
                <faultactor>Who caused the error</faultactor>
                <detail>Specific error information</detail>
        </soap:Fault>
</soap:Body>

</soap:Envelope>


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:ksuh@;shaw.ca]
Sent: Tuesday, November 12, 2002 10:41 AM
To: CF-Talk
Subject: Re: RE: CFOBJECT and conversion from ASP


Yes, you can.

However, using a web service via something like SOAP is a pain, because
you'd have to build the SOAP packets yourself.  *shudder*

----- Original Message -----
From: Joshua O'Connor-Rose <[EMAIL PROTECTED]>
Date: Tuesday, November 12, 2002 11:27 am
Subject: RE: CFOBJECT and conversion from ASP

> I'm using ColdFusion 5
>
> I've heard of these web service things in seminars and meetings
> discussing
> net and other development environments. I haven't realy explored
> using them
>
> Can I implement a web service into my application now?
> (Like that Doc to HTML web service) Where can I learn about that.
>
> -From the desk of Joshua O'Connor-Rose
> (aka Whifflebat)
> -All is Good
>
>
> >From: "Adrocknaphobia Jones" <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: CF-Talk <[EMAIL PROTECTED]>
> >Subject: RE: CFOBJECT and conversion from ASP
> >Date: Tue, 12 Nov 2002 13:18:17 -0500
> >
> >Well, I'll agree with you halfway. COM is definitely not dead,
> although>MM acts like it is. However, webservices may be able to
> replace basic
> >COM functions like using Office to convert a word doc to html.
> But it's
> >not going to be able to replace the sophistication COM offers
> >developers.
> >
> >Josh: What version of CF are you using?
> >
> >Adam Wayne Lehman
> >Web Systems Developer
> >Johns Hopkins Bloomberg School of Public Health
> >Distance Education Division
> >
> >
> >-----Original Message-----
> >From: Jason Lees (National Express)
> >[mailto:Jason.Lees@;NationalExpress.Co.uk]
> >Sent: Tuesday, November 12, 2002 12:03 PM
> >To: CF-Talk
> >Subject: RE: CFOBJECT and conversion from ASP
> >
> >Coms not dead yet as you say theres too many older applications using
> >it,
> >but the way forward is webservices, which is basically a newer
> version>of
> >Com without the all the hassles.
> >
> >With reagrd the problem try
> >
> >myMethod = myObject.item("title");
> >myMethod = "title";
> >
> >
> >
> >Jason Lees
> >Systems Developer
> >National Express Coaches Ltd.
> >
> >
> >
> >-----Original Message-----
> >From: Joshua O'Connor-Rose [mailto:whifflebat@;hotmail.com]
> >Sent: 12 November 2002 15:57
> >To: CF-Talk
> >Subject: CFOBJECT and conversion from ASP
> >
> >
> >OK so COM is dead, I would like to see the thread. Do you have a
> link.>That would also imply that no one uses it anymore.
> >
> >Anyway the office I'm developing for is using all that dead stuff.
> >
> >I have been advocating replacing what they have with Verity and
> >hopefully
> >that is what the system will convert to. But right now . . . I'm
> a slave
> >to
> >a contract.
> >
> >In response to your suggestion (thanks for the post)
> >
> >myObject = myObject.item("title");
> >myObject = "title";
> >
> >This throws an error "the parameter is incorrect" on this line:
> >myObject = myObject.item("title");
> >which I assume is coming from the object itself.
> >
> >So that doesn't work either. (It as if the object won't accept
> the name
> >of
> >the option without an assignment operator).
> >
> >Any other ideas? or am I going to have to use asp?
> >
> >-Joshua O'Connor-Rose
> >-All is Good
> >
> >
> >
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Get the mailserver that powers this list at http://www.coolfusion.com

Reply via email to