• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
Bartenders:
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

Which is correct paradigm in integrating two application? Servlets / Mule ESB used

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

I am working on an application, if you could help out which paradigm is correct for implementing:

Client Side: Web Application (HTML/JSP/Servlets)
Intergration: Mule ESB

Client will call Mule ESB flow using HTTP URL and get response from the same

I have two way outs

1) We call Mule ESB from HTML directly and Mule ESB send response back to another JSP page. Then, I need to mention page name inside, Mule ESB flows.

2) Or We call Mule ESB from controller(servlets) and Mule ESB send response back to servlets and then servlets redirect to correct page with manipulated data.

Which of above two is considered as good?

Regards
 
Ranch Hand
Posts: 49
Python Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Depends really on your application. However Mule ESB has fantastic inbuilt implementation and connectors to databases.
It would be good for client to directly call the MuleESB hosted URL.

Basic validation and data processing (changing the data into different structure say JSON in Mule) and if required for further validation to Servlet controller (in async or sync way)

However if your business is okie with MULE directly interacting with DB then i would suggest you can add your business validation and saving part in mule directly this is avoid any sever hopping and creating of different sessions.

on a whole ESB has loads of features which you would want to use before forwarding the request to your webserver.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic