Another idea would be to have Java stick the file into a user space object
and then RPG can create/obtain a pointer for that space using system API's.
To bad the JavaToolbox didn't have an implicit type conversion from string
to pointer so this could work. The longer I program the more I like
pointers :-)
HTH,
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of i5
Sent: Monday, January 07, 2008 2:38 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Web Services wizard and SRVPGM prototypes.
"
I agree i'ts not the best solution but the messages has to be stored and
preserved as a prove of the communication so I need the encoded data in the
original envelope. Sure the only thing I can do with the binary (XML or PDF
or whatever) is to write out a stream file in ifs. The ideal thing is having
an interface like the example in the RPG Programmer manual (page 167/168) a
pointer and the length of the data but I don't think the wizard can provide
it.
Thanks anyway.
Marco
----- Original Message -----
From: Aaron Bartell <albartell@xxxxxxxxx>
To: 'Websphere Development Studio Client for iSeries' <wdsci-l@xxxxxxxxxxxx>
Cc:
Date: Monday, January 7 2008 08:09 PM
Subject: Re: [WDSCI-L] Web Services wizard and SRVPGM prototypes.
I wouldn't recommend passing binary objects in XML, but if it is a
requirement then I would program an intermediary in the Java side to decode
the base64 binary object to a file in the IFS and pass that location to the
RPG program. Someone please correct me if I am wrong, but when using base64
encoding, for every 5 bytes of data you will add two more bytes. If that
math is correct (you can test it here
http://rumkin.com/tools/compression/base64.php) then a 1MB file will end up
using around 1.4MB of bandwith. If FTP or similar "raw format" approach was
used you would only be using 1MB. This can obviously become a concern if
you are doing hundreds of file transfers a day.
If you have the option to alter the approach of sending files in XML I would
instead go the route of sending a URL to the file needing to be accessed and
then your RPG (or Java) can go and get it after the transaction (using FTP
or HTTP GET).
HTH,
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of i5
Sent: Monday, January 07, 2008 12:25 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Web Services wizard and SRVPGM prototypes.
"
Yes, the XML part will be (99,99%) shorter than 64 kb but PDF and Images
(JPG and DWG) basicly are bigger than 64Kb.
Thanks
Marco
----- Original Message -----
From: Aaron Bartell <albartell@xxxxxxxxx>
To: 'Websphere Development Studio Client for iSeries' <wdsci-l@xxxxxxxxxxxx>
Cc:
Date: Monday, January 7 2008 07:15 PM
Subject: Re: [WDSCI-L] Web Services wizard and SRVPGM prototypes.
What is the scenario for the data that is potentially over 65535? That
might help us better assist you. I have found 65535 for a single element or
attribute value is plenty 99% of the time.
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of i5
Sent: Monday, January 07, 2008 11:24 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Web Services wizard and SRVPGM prototypes.
"
I'm testing the Web Service wizard to generate services from a service
program, it's working fine but what if one of the parameters I need to
receve (or send) is longer then 65535?
Thanks in advance
MarcoF
midrange.com
