Re: Weird IWS Bug (?)

I guess no one is understanding me regarding detect field lengths support
in iws. Please read the section entitled "Support nested output arrays" in
the following article:

https://www.ibm.com/developerworks/ibmi/library/i-integrated-web-services-server/index.html




Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote on 07/18/2019 01:48:22 AM:

From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"

<web400@xxxxxxxxxxxxxxxxxx>

Cc: amra@xxxxxxxxxx
Date: 07/18/2019 01:48 AM
Subject: [EXTERNAL] Re: [WEB400] Weird IWS Bug (?)

Booth - I don't know how many more times I have to say this - I KNOW
THIS. I mentioned in the video that I had done it but that it
wasn't worth going back and correcting.

I have a working version and in that (and every version I have
produced other than the one in the video) it was correctly specified
as input - is received correctly by the program and produces the right

output.

It is possible that adding const to the definition might cause the
wizard to _default_ to input - but you have always been able to
manually change the setting in the wizard - which is what I do
because in my case having the parm defined as const is not acceptable.

It is "purring" BUT the fact remains that there are two issues with
the tool/documents that remain unexplained.

1) The does say that you must _select_ detect field lengths in order
to control the output length. This is WRONG - the opposite is true.

2) The docs say that the length will not be included in the output -
this is also not true - it is included.

As requested by Nadir I have now applied the latest PTFs and it does
not change anything (apart from adding the interesting "Deploy SQL
as web service" option) the results are as stated above.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 17, 2019, at 4:58 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

When using the IWS wizard, in the URL path template(Step 3 of 9)

you list an input parm of /cat/{cat}. Yet in Step 4 of 9 all of the
fields are defined as output. My bet (up to 42 cents!) is that your
troubles lay somewhere within that incongruity. Pure guess, but
my guess is that "cat" and "requestedcat" are the same field? If
so, changing {cat} to {requstedcat} and adding *const option to
requestedcat in RESTSVR4x should make it purr.

My understanding is that the way the wizard knows if a parm is

input or output is from the *const option? or something.

On 7/17/2019 2:31 PM, Jon Paris wrote:

As to *Const - I have no idea why you had problems with it - it

should have zero bearing on IWS - it is just used by the compiler -
it may affect the PCML (not sure about that) but the only thing that
would do is make the wizard only show you Input as an option instead
of Input and Output.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)

mailing list

To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://urldefense.proofpoint.com/v2/url?

u=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwIFAg&c=jf_iaSHvJObTbx-

siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-

ew&m=g49rN3Sgx5wDcfEaku4tkkXeb_mF6EETuPtPudTANEQ&s=F8UKASjpVi6T0a0jy8pYcSxq48YcwGW5BmRgZ_QwjN4&e=

or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://urldefense.proofpoint.com/v2/url?

u=https-3A__archive.midrange.com_web400&d=DwIFAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-

ew&m=g49rN3Sgx5wDcfEaku4tkkXeb_mF6EETuPtPudTANEQ&s=vHO9OY5sLD3dbon0iOpOfjjqJH2c_hfp_mgSFPcpA6o&e=

.