This week's giveaway is in the Spring forum.
We're giving away four copies of Microservices Testing (Live Project) and have Chris Love & Andres Sacco on-line!
See this thread for details.
Win a copy of Microservices Testing (Live Project) this week in the Spring forum!
  • 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Integration of web service

 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I have a doubt regarding the integration of web service to J2EE application. Where should the code to invoke the web service go? Should it be some EJB client? If we call the service asynchronously, then we can go for some MDB(Message Driven Bean). But when the call has to be by synchronous, what option do we have?

The option of creating a EJB as a client to a web services doesn't make much sense to me. I'm thinking of creating a utility class that takes care of calling the web services and use that utility calls in my Stateless session bean that contains the business logic. I'm might name utility class as XZXDAO. Is it a good idea?

Appreciate your time.

Thanks & Regards,
Anil Chowdary K
 
Anil Chowdary
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In the above message, By Utility class I mean a "DII"(Dynamic Invocation Interface) client.
1. Which layer will this class go? I assume it as Integration later.
2. What kind of naming convention we should use for such classes? I'm not sure if I can call it as DAO?

Thanks & Regards,
Anil Chowdary K
 
Anil Chowdary
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can someone please answer this question?
 
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Anil Chowdary wrote:In the above message, By Utility class I mean a "DII"(Dynamic Invocation Interface) client.
1. Which layer will this class go? I assume it as Integration later.
2. What kind of naming convention we should use for such classes? I'm not sure if I can call it as DAO?

Thanks & Regards,
Anil Chowdary K



1. Yes it is integration layer
2. This class kind of acts as a proxy.
 
Anil Chowdary
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the reply Dinesh.

-Anil
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic