• 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:
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

Looking up a webservice

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi ,

My existing application consists of many utility WAR's packed into a EAR. We are adding/ modifying functionality of this application, this requires communication to the Backend (Main Frame) via web services.

==========================================
The platform : wsad 5.1.2 and was 5.1
==========================================
Our development task starts with a WSDL generated based on the
mainframe copy book. Using this WSDL we generate the Webservice Client
Automatically, Thanks to WSAD.

But the drawback with this approach is the need to dump the entire existing application code and the code generated by WSAD into the same WAR. It is a version control nightmare (especially webservicesclient.xml).

We have 20+ people working simultaneously on the project.

I was experimenting with options available.

--> I generated EJB service end point using the same WSDL. The output can
be packaged into a ejb-jar. This makes packaging my application very
Simple and clean ( n number of WAR's and n number of ejb-jars
Packaged together in an EAR)

However, the ejb jar created via WSAD does not hold any JNDI lookup
for the service (<service-ref> tag). The xml files packaged along with
the jar (ejb-jar.xml, webservices.xml,GetServiceInfo_mapping.xml )
talks only about the binding and mapping between EJB and the WSDL.

How and where do I incorporate the lookup information, such that any
servlet in a WAR at the same level as the jar can access the EJB
Service end points.

Anupam
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!