× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WEB400
  3. July 2019

Re: Weird IWS Bug (?)

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.