🚀 go-pugleaf

Hello Sig,

Whether you can interop with the service using BCB depends on how the
Service exposes the file. There are many options for exposing the contents
of a file:

1. As a string
2. As an array of bytes
3. As an attachment

CBuilder supports the first two approaches. Item #3 will not work with
CBuilder as attachment support was added after BCB6. And even if you do use
a later version, it probably won't work with WSE as CBuilder's support for
attachment is based on the MIME attachment which is not what WSE supports
(WSE probably supports DIME or MTOM??).

If you have a WSDL for the service it's possible to infer how the service
exposes the file from that document. If you can point me to (or email a copy
of) the WSDL, I'd be happy to look at it and provide more information.

Cheers,

Bruneau.

Jean-Marie Babet wrote:
> Hello Sig,
> 
> Whether you can interop with the service using BCB depends on how the
> Service exposes the file. There are many options for exposing the contents
> of a file:
> 
> 1. As a string
> 2. As an array of bytes
> 3. As an attachment
> 
> CBuilder supports the first two approaches. Item #3 will not work with
> CBuilder as attachment support was added after BCB6. And even if you do use
> a later version, it probably won't work with WSE as CBuilder's support for
> attachment is based on the MIME attachment which is not what WSE supports
> (WSE probably supports DIME or MTOM??).
> 
> If you have a WSDL for the service it's possible to infer how the service
> exposes the file from that document. If you can point me to (or email a copy
> of) the WSDL, I'd be happy to look at it and provide more information.
> 
> Cheers,
> 
> Bruneau.
> 
> 


Hello Bruneau,

Thank you for your reply. WSDL Importer generates code to use the 
service functions as an array of bytes. It works very nicely with 
BDS2006 but fails with BCB6. I sent you an e-mail with WSDL attached. It 
would be nice to get it work with BCB6 as we still use it in production.

The code generated by WSDL imported looks like this:

__interface INTERFACE_UUID("{CFE467D4-A39E-2BD2-5836-7685A9E27F8D}") 
Service1Soap : public IInvokable
{
public:
   virtual AnsiString      SayHello() = 0;
   virtual TByteDynArray   ReceiveFile(const AnsiString fileName) = 0;
   virtual void            SendFile(const TByteDynArray data, const 
AnsiString FileName) = 0;
};
typedef DelphiInterface<Service1Soap> _di_Service1Soap;

_di_Service1Soap GetService1Soap(bool useWSDL=false, AnsiString addr="");



Thank you,
Sig

BTW, there're example links I used to build the service:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wse3.0/html/4344d43e-ceb4-43a9-8f8c-6a3f89f786bd.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wse3.0/html/b4b19453-e4e4-4056-906d-72504ed8c0df.asp

Hello,

I have received the email. Thank you. I'll make some time to investigate
this today. Unfortunately, it's probably something we've fixed in the
runtime. Hopefully I can identify the change you'll need to move over.

Cheers,

Bruneau.