Re: XMLSERVICE

[Henrik Rützou <hr@xxxxxxxxxxxx>]

Yes, it will still suffer for 15meg XML limitation because XMLSERVICE for
some reason uses
%alloc instead of terabyte support in the QC2LE memory allocation
procedures.

On Sun, Jan 29, 2012 at 10:17 PM, Richard Schoen <richard@xxxxxxxxxxxxxxx>wrote:

> Seems to work nicely.
>
> I will play with that.
>
> I suppose specifying an exit program would be nice, however no program is
> ever complete :-)
>
> Will this still suffer the same 15meg buffer limitation as the XML stream ?
>
> Not a big deal.  Just want to know my limits :-)
>
> Regards,
> Richard Schoen
> RJS Software Systems Inc.
> Where Information Meets Innovation
> Document Management, Workflow, Report Delivery, Forms and Business
> Intelligence
> Email: richard@xxxxxxxxxxxxxxx
> Web Site: http://www.rjssoftware.com
> Tel: (952) 736-5800
> Fax: (952) 736-5801
> Toll Free: (888) RJSSOFT
> ------------------------------
>
> message: 4
> date: Sun, 29 Jan 2012 16:25:04 +0100
> from: Henrik R?tzou <hr@xxxxxxxxxxxx>
> subject: Re: XMLSERVICE
>
> Richard,
>
> in basic it was simple, XMLCGI has the following code that sends the
> generated XML in the addr (pOClob( and size (szOClob) back to the browser:
>
> // output
> when status = RUN_CGI_OUTPUT;
>  // -----
>  // send header + end (LFLF)
>  respHead = 'Content-type: text/xml' + CRLF + CRLF + NULLTERM;
>  rn = writeIFS(1:%addr(respHead):strlen(%addr(respHead)));
>  // send return data
>  szOClob = strlen(pOClob);
>  rn = writeIFS(1:pOClob:szOClob);
>  status = RUN_CGI_FINISH;
>
> I added a new parameter xFMT and changed the original code to:
>
> // output
> when status = RUN_CGI_OUTPUT;
>  status = RUN_CGI_FINISH;
>  szOClob = strlen(pOClob);
>
>  if xFMT <> '*json';
>
>    // -----  ORIGINAL XML
>
>    // send header + end (LFLF)
>    respHead = 'Content-type: text/xml' + CRLF + CRLF + NULLTERM;
>    rn = writeIFS(1:%addr(respHead):strlen(%addr(respHead)));
>    // send return data
>    rn = writeIFS(1:pOClob:szOClob);
>
>  else;
>
>    // ----- OUTPUT BY EXIT PROGRAM
>    // call exit program
>    xmlcgix2(pOClob:szOClob);
>
>  endif;
>
> Then I made a little program (XMLCGIX2) that converts the XML result into
> JSON and then sends the new result to the browser:
>
>  * Standard powerEXT H-Spec's
>  /copy qsrc,pxapihdr      General H-Spec's
>
>  * powerEXT API Connectors
>  /copy qsrc,pxapicgicn    Basic HTTP connecter & Basic Services
>
> d fieldName       s             10a   varying
>
>
>  * Program Entry
> d PgmEntry        pr                  extpgm('XMLCGIX2')
> d                                 *
> d                               10i 0
>
> d PgmEntry        pi
> d  pOClob                         *
> d  szOClob                      10i 0
>
>  /free
>    clearSrvPgm();
>    setContent('text/html');
>    xmlReaderInz(pOClob:szOClob);
>    jsonNode('*object');
>    jsonNode('*boolean':'success':'true');
>    jsonNode('*array':'rows');
>    dow xmlReader = 0;
>      select;
>        when xmlGetNode = '%row';
>          jsonNode('*object');
>        when xmlGetNode = 'data' and xmlGetAttr = 'desc';
>          fieldName = xmlGetData;
>        when xmlGetNode = 'data' and xmlGetAttr = '';
>            if 0 <> %check('.-0123456789':xmlGetData)
>             or xmlGetData = '.'
>             or xmlGetData = '-'
>             or xmlGetData = '';
>              jsonNode('*string':fieldName:xmlGetData);
>            else;
>              jsonNode('*number':fieldName:xmlGetData);
>          endif;
>        when xmlGetNode = '/row';
>          jsonEndNode();
>       endsl;
>    enddo;
>    jsonEndNode();
>    jsonEndNode();
>    echoToClient();
>    return;
>  /end-free
>
> If I should make a more generic solution I would probably not chose a xFMT
> parameter and a fixed program name but pass a parameter with the exit
> program name so I could have a number of exit programs that filter and/or
> convert the result to whatever I chose without having to change the code in
> XMLCGI.
>
>
>
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.