Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

[ Writing Webservices in COBOL ] url attached  RSS feed

 
Ranch Hand
Posts: 67
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If I understand this article correctly, I think the real point they are making is that COBOL is supported in the .NET environment. Indirectly, this allows you to expose COBOL programs as web services - by virtue of the fact that a .NET program can use any other .NET component. Despite the regular hammering of .NET by the J2EE community - this is actually a pretty cool thing.
However, this is not saying that your entire Web Services architecture is defined in COBOL (XML parser et al) as was implied in some other threads. You still use the .NET framework to handle the services infrastructure part - delegating to COBOL for the service implementation.
Of course, this is a perfectly good way of integrating legacy environments into a WS model. Use the right tool for the job - C++, Java etc for the XML and services infrastructure; COBOL for legacy data access etc. However, there are already a number of alternatives for accessing COBOL programs from OO environments. For example, IBM have an entire connector framework for doing this. J2EE has its connector architecture as well.
So...in principle it should be simple to wrap any COBOL code with a Java decorator, so it can be used in a Web Services. Not necessarily as clean as the .NET solution, and certainly a different philiosophy - but probably just as effective.
I would invite any comments on this. Perhaps someone has a COBOL web service?
regards,
paul.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!