Search: Go


>>
 APLDN Home

>>
 Events

>>
 Trainings

>>
 APL Books

>>
 APLDN Links

>>
 Discussion Groups

>>
 Downloads

>>
 Articles

>>
 Library

>>
 Learning Tools

>>
 APLDN User IO

>>
 APL2000.com




APLDN Home > Discussion Groups > APL Web Services > Problem Resolution
Problem Resolution

Author Thread: APL Web Services and .NET
E'Kong.Tse
APL Web Services and .NET
Posted: Wednesday, July 20, 2005 9:46 AM (EST)
Hi, I'm new at trying to get APL+Web Services to work with .NET and I'm running into problems. I have a simple 'Hello World' function in APL and I have specified in the server configuration xml file that the function result type is of 'apl2soapwrapl'. I have also created the WSDL for it so that a web reference can be added in .NET. However, when I tried calling that function in .NET, the return value throws an exception because the result is wrapped in the correct SOAP envelope tags, but the HTTP response that should wrap around the SOAP envelope tags is expected to be of type 'text/xml' but it is currently of type 'application/octet-stream-soap'. How can I specify in the configuration file that after wrapping the result in SOAP tags, the HTTP response type should be 'text/xml'? I don't want to create the XML and SOAP tags inside the APL function that I'm calling if this is something I can set in the configuration file. Can someone please point me in the correct direction if they've gotten this to work in the past? Thanks! E'Kong


Comments:

Author Thread:
davin.church
APL Web Services and .NET
Posted: Thursday, July 21, 2005 5:27 PM (EST)
If you don't find a way to alter the tags, I've got some routines that can help you build (and parse) those SOAP wrappers (and XML in general).

     

Jairo.Lopez
APL Web Services and .NET
Posted: Tuesday, July 26, 2005 1:04 PM (EST)

When the result type is 'apl2soapwrapl' what the APL+WebServices uses the System.Runtime.Serialization.Formatters.Soap.SoapFormatter class to serialize the data using SOAP. This is the reason the content-type is set to 'application/octet-stream-soap' and cannot be changed.

There is no automatic way to 'wrap' data using SOAP headers in APL+WebServices, however you can accomplish this creating the tags in APL+Win and using the result types 'document' and 'content-type'.

 

     

davin.church
APL Web Services and .NET
Posted: Tuesday, July 26, 2005 5:24 PM (EST)

Jairo,

 

If you'll save me some time and point me to the definition of that standard SOAP-data structure that you're using, I'll write a utility to turn APL objects into SOAP and back again using my (pure-APL) XML tool library.  With any luck it should then be able to produce and use the identical form that you've included there.

     

E'Kong.Tse
APL Web Services and .NET
Posted: Wednesday, July 27, 2005 3:04 PM (EST)
Hi Davin, If you don't mind sending me your XML routines that would be great! Thanks!

     

davin.church
APL Web Services and .NET
Posted: Wednesday, July 27, 2005 10:44 PM (EST)

Sure - I've been meaning to publish the whole thing out here for some time now.  It's about time I did that.  Give me a little time to package things up for uploading.  (I'll also see if I can find the specs for that SOAP data encoding and do something about that, too, if it's quick to do.)

 

(Remind me if I don't get it done soon.)

     



APL2000 Official Web Site

Most good judgment comes from experience. Most experience comes from bad judgment.
--- Anonymous

APLDN Home   |    |  Events   |  Trainings   |  APL Books   |  APLDN Links   |    |  Discussion Groups   |    |  Downloads   |  Articles   |  Library   |  Learning Tools   |  APLDN User IO   |  APL2000.com   |