Discussion Locked

The poor man's Web services

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us what you think about the poor man's Web services, featured in this week's Web services e-newsletter.

10 replies

by jim.hubbard

Implementing webservices "with UDDI, WSDL, and SOAP" is so simple with .Net as to be laughable.

While JAVA was first to implement many of the designs that .Net has incorporated, JAVA falls far behind in web services.

In .Net, if you can write a class, you can publish a web service. And, with freely available SOAP translators for JAVA, even if the office is stuck with JAVA they can still take advantage of the web services produced by .Net.

Give it a go. It is far faster to develop anddistribute than the old DCOM days....and much more reliable.

by rhoobler

This is a non-standard solution. Which may fit for this particular client. I did a couple of XML / socket solutions before web services came out. Now, web services offer a much better and standard solution whether in Java or .NET.

.NET is a little easier but most good programmers could do a Java web service in the same amount of time, it just takes a little more reading (it is really easy).

In the end, having a non-standard solution will probably cost more as well as create more headaches for developers and future partners that need the same functionality.

by ttheobald

It's just as simple to whip up a Web Service using modern Java IDEs as it is with .NET, and more than a few of them did it before VS hit shrink-wrap. JBuilder, Cape Clear, Silverstream, just do a google search on "Java" and "Web Services". I'm nota Java-ite myself, but I think you're doing yourself a disservice by failing to look around a little. If .NET floats your boat, rock on - but don't pretend the others don't exist.

T

by gungh

Brian, It seems that there are number of companies who have recognised the need to reduce the expense and manage the complexity of creating and deploying web services, and are building solutions. One of them is based in Dallas - XBridge Software. They market a device that is relatively cheap, simple to configure and administrate, and is in production with clients.
I'd be interested in comments about their approach.

Fred

by rob

Wouldn't it make more sense to process the
POST to the home office using HTTPS, rather
than unsecurely through HTTP? Especially
since this is accounting data....

by nhannon

The problem of moving accounting data from remote divisions to a central office is common across many types of businesses. With over 100 workable accounting systems on the market, information can be difficult to discover, package and send to the consolidating office.

Fortunately, the extensible business reporting language (XBRL) is fully capable of providing the XML "packaging" required for the data transfer. With over 150 contributors to the development of XBRL, the markup language provides the means for translating disparate financial system information into tagged data ready for transport.

Grabbing the right data, applying the correct XBRL tags (or creating custom XBRL tags), creating XML documents and transferring same to a centralized location can supplement your "poor man's web services" scenario. BTW, XBRL is freely available for download at www.xbrl.org.

Neal

by bill

Your article demonstrates, at least in the written word, how important it is for businesses to research their problems properly. Unfortunately, we all know that most don't and suffer the consequences with larger bills!! You have shown us at RAMODEM, a 2-partner company with a little office, that when we grow, and we will grow, we will need to read your article again. Obviosly you cannot guarantee suucess with every appliacation, or can you?

Thanks for a great article

Bill Tottle

by kevin bosch

Having been there done that over 2 years ago, I can say that this architecture is implementing only part of SOAP. Yes it is effective however because there is no contract with the applications API (SOAP?s WSDL) the maintenance of the application will become a nightmare. The costs that you save up front implementing a SOAP solution, will be spent 1000?s of time over in maintenance of the application. Just think about when you need to take on a new developer to extend the application?

In factwith Microsoft .NET framework all the SOAP plumbing has already been done for you..

I totally disagree that this is the poor mans web service.. this poor man better have some serious resource to back the ongoing development of this application. Of course you could deliver everything in the first edition of the application and you won?t have these problems.

by ttheobald

When you said "Yes it is effective however because there is no contract with the applications API (SOAP?s WSDL)" you've referred to an identical situation that can occur with .NET - if your programmers change the WSDL (effectively the interface) of your service, anyone relying on it will lose it. This is independent of the vendor of your toolset, whether you've built it with Delphi, JBuider, C#, whatever.

The point of using Web Services is simply to handle the communication layer - the "pipe" over which your data travels. What you do with, and what is contained in, that pipe, is what you have to relate with WSDL in order to let people use the service. GIGO applies everywhere you go.

T

This discussion is closed to new replies.