xmlns:tns="http://www.OneOutBox.com/wsdl/FreeFaxService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<part name="Sender" type="xsd:string">[EMAIL PROTECTED]
<documentation>Your email address, so that delivery notifices
can be forwarded to your attention.
Not used for other purposes.
</documentation></part>
<documentation>The international dialing code of the recipient
FAX machine. e.g. USA dial 1+areacode+number.
Non-numerics within the string are ignored.
</documentation></part>
<documentation>Delivery information at the destination, such as
name and mailstop. May include spaces (or _) and RETURN (or /)
</documentation></part>
<documentation>The contents of the FAX to be delivered. Will
be formatted roughly 80 characters wide on the page. No limit.
</documentation></part>
<part name="return" type="xsd:string">
<documentation>The return code is a tracking number.
Not used within the Free FAX service, but available for
tracking purposes in the commercial ProFAX.
</documentation></part>
</message>
<operation name="SendFreeFAX">
<input message="tns:freeFaxRequest"/>
<output message="tns:freeFaxResponse"/>
</operation>
</portType>
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="SendFreeFAX">
<soap:operation soapAction="urn:OneOutBox#SendFreeFAX"/>
<input>
<soap:body use="encoded" namespace="urn:OneOutBox"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="urn:OneOutBox"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<documentation>Provides a Web Services interface to free worldwide FAX transmission service, provided by
1outbox (www.1outbox.com).</documentation>
<port name="FreeFaxPort" binding="tns:FreeFaxBinding">
<soap:address location="http://www.OneOutBox.com:80/cgi-bin/soap/outbox.cgi"/>
</port>
</service>
</definitions>
-----Original Message-----
From: Stefan Henke [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 1:39 PM
To: [EMAIL PROTECTED]
Subject: AW: FAX / SMS Web Services...Do you want to define a soap interface which takes all necessary data required for sending (text, receipient and so on) and the message will be sent by the service itself?What is your problem? Sending the message on the server or creating the soap interface for the service?Stefan-----Ursprüngliche Nachricht-----
Von: Kumaresan, Karikalan [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 18. Februar 2002 11:16
An: '[EMAIL PROTECTED]'
Betreff: FAX / SMS Web Services...Hi All,
It would be great if somebody provide some assistance to create FAX / SMS SOAP web service? Has anyone developed FAX/SMS SOAP web service?
regards,
Kari...-----Original Message-----
From: Thomas Börkel [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 11:11 AM
To: [EMAIL PROTECTED]
Subject: RE: Off topic .NET question
HI!
We do not use an Axis AuthHandler. We have our own transport (our own HTTP server), so that's no problem for us.
Regards,
Thomas> -----Original Message-----
> From: Adam.Leggett [mailto:[EMAIL PROTECTED]]
> Sent: Montag, 18. Februar 2002 10:54
> To: '[EMAIL PROTECTED]'
> Subject: RE: Off topic .NET question
>
>
> Thomas,
>
> Thanks for the feedback. We have the exact same problem i.e
> PreAuthenticate=true does not appear to work for us either.
> In the meantime on the Java side I have created a version of
> my AuthHandler
> that parses the SOAP header instead for auth details. At this
> point we are
> at the stage of trying to create an .NET 'acceptable' WSDL
> with the correct
> <soap:header> element described in the operation. We are
> having some trouble
> with this so far.
>
> Im curious as to how you would make a handler force a 401 to
> be returned.
> What would be your approach to this?
>
> Adam
>
> -----Original Message-----
> From: Thomas Börkel [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 18, 2002 9:38 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Off topic .NET question
>
>
> HI!
>
> All proxy classes derive from WebClientProtocol in .NET. And
> this class has
> a property named "PreAuthenticate" which should exactly do
> that. But it does
> not work here. Maybe it CANNOT work, because how should .NET
> know that you
> want basic authentication and not, for example, NTLM authentication?
>
> If you find out how to get this to work, I would be very
> interested. If not,
> Axis has to return 401 to make it work.
>
> Regards,
> Thomas
>
> > -----Original Message-----
> > From: Adam.Leggett [mailto:[EMAIL PROTECTED]]
> > Sent: Freitag, 15. Februar 2002 14:46
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: Off topic .NET question
> >
> >
> > Thanks thomas,
> >
> > But im slightly confused here. To authenticate to my AXIS
> > service(s) I have
> > a handler sitting in the request flow, that returns a SOAP
> > Fault in the SOAP
> > response if user cannot be authenticated. The AxisFault
> > generated in the
> > Handler is rethrown as ServletException so a 500 server error
> > is returned as
> > well.
> >
> > Can you not force the .NET to send basic auth 1st time
> > round..surely u can?
> > In my scenario, developers will know at design time that the
> > service is
> > password protected.
> >
> > Cheers
> >
> > Adam
> >
> > -----Original Message-----
> > From: Thomas Börkel [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, February 15, 2002 1:04 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Off topic .NET question
> >
> >
> > HI!
> >
> > This (basic HTTP authentication) works here. .NET does not send the
> > authorization info with the first attempt, but it sends it with the
> > second attempt if the first attempt has been refused with HTTP error
> > 401 and the
> > correct challenge. It does the second attempt automatically,
> > if the first
> > one failed correctly. From then on, it sends the
> > authorization always at the
> > first attempt. This is normal HTTP client behavior AFAIK.
> > Your are doing it
> > correctly in your example, so it *should* work.
> >
> > Regards,
> > Thomas
> >
> > > -----Original Message-----
> > > From: Adam.Leggett [mailto:[EMAIL PROTECTED]]
> > > Sent: Freitag, 15. Februar 2002 13:05
> > > To: Axis User ([EMAIL PROTECTED])
> > > Subject: Off topic .NET question
> > >
> > >
> > > Currently, I am working to interop with an MS colleague
> using .NET
> > > client with my AXIS service. I have a handler chain that
> uses LDAP
> > > to authenticate/authorize access to my deployed service. Works
> > > fine with my
> > > AXIS client. Trouble is, we cant seem to be able to get .NET
> > > to send the
> > > required Authorization: Basic pair in the HTTP header. When
> > looking at
> > > tcpmon it doesn't appear.
> > >
> > > Heres the c# client code we think should set the basic
> auth, but it
> > > doesn't.
> > >
> > > ICredentials credentials = new
> > > NetworkCredential("username","password","mydomain");
> > > serviceInstance.Credentials = credentials;
> > >
> > > serviceResponse response =
> > > serviceInstance.serviceMethod(serviceRequest);
> > >
> > > I know this is off topic, so any effort in answering this will be
> > > even more appreciated here than usual.
> > >
> > > TIA
> > >
> > > Adam Leggett
> > > UPCO
> > > Direct Line: 0113 20 10 631
> > > Fax: 0113 20 10 666
> > > <http://www.upco.co.uk>
> > > The contents of this email are intended for the named
> addressees and
> > > may contain confidential and / or privileged material. If
> > > received in error,
> > > please contact UPCO on +44 (0)113 20 10 600 and then delete
> > > the entire email
> > > from your system. Unauthorised review, distribution,
> > > disclosure or other use
> > > of this information could constitute a breach of confidence. Your
> > > co-operation in this matter is greatly appreciated.
> > >
> > >
> > >
> >
>
