Re: Microsoft .NET frontending IBM i

The majority of .NET webservices I run into go the route of having a
single .NET method call that passes the XML as a string in/out of that
method. This of course means that the full payload of that XML will
go through additional processing to be escaped (i.e. convert < to
&lt;).

There are so many better lightweight ways to do cross platform
communication, I just don't get why so many adopt the over-architected
approach. There's nothing wrong with passing XML like this as an HTTP
POST the endpoint:

<root>
<parm1>value</parm1>
<parm2>value</parm2>
</root>

I will get off my web service soap box - I just have seen so many bad
implementations of technology in that space.
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/



On Fri, Oct 8, 2010 at 4:08 PM, <TAllen@xxxxxxxxxxxx> wrote:

Generated WSDL and XML?
That sounds like the code first approach.  Ugh.  Always use the contract
first approach where you create the WDL and schemas and generate the code
stubs from that.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx




            Aaron Bartell
            <aaronbartell@gma
            il.com>                                                    To
            Sent by:                  "Web Enabling the AS400 / iSeries"
            web400-bounces@mi         <web400@xxxxxxxxxxxx>
            drange.com                                                 cc

                                                                  Subject
            2010-10-08 17:05          Re: [WEB400] Microsoft .NET
                                      frontending IBM i

            Please respond to
            Web Enabling the
             AS400 / iSeries
            <web400@midrange.
                  com>






It depends on what version of WCF you are using.  I had a customer
with the latest version and we learned quickly that Microsoft was
making up their own rules and waiting for everybody else to catch up.
It is probably rectified by now, but the web service stack that
Microsoft and IBM are purporting is horribly complex.  Just take a
look at the generated WSDL and XML.

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/



On Fri, Oct 8, 2010 at 3:47 PM, Dean, Robert <rdean@xxxxxxxxxxxx> wrote:

JAX-WS on the Java side and WCF on the .Net side work very, very well

together.  The introduction of those APIs on each side makes
interoperability nearly trivial.

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On

Behalf Of Richard Schoen

Sent: Friday, October 08, 2010 4:24 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Microsoft .NET frontending IBM i

It's actually pretty easy to expose RPG code as a web service with the

new IWS Server on the iSeries.

I've done some IWS samples where I sent back parms and datasets as well.

Web services in general can be finicky if you don't know how to tickle

them correctly.  We've had lots of fun writing Java web services and
calling from .Net.

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: 8
date: Fri, 8 Oct 2010 16:04:41 -0400
from: TAllen@xxxxxxxxxxxx
subject: Re: [WEB400]

Writing a web service in RPG?  I'm sure it can be done.  Good luck with

that...

Generating a web service client in VStudio is easy if there are no

wrinkles at all.  If there is anything outside the box of generated code
then we see finger pointing back to our web service that it does not work.
Well, it does work.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx

This communication and any transmitted documents are intended to be confidential. If there is a problem with this transmission, please contact the sender. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.