Help coderanch get a
new server
by contributing to the fundraiser
  • 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

XML as communication format between SERVLET tier & EJB tier - Pros and Cons ?

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I wonder if XML is the right choice between webserver/servlet-container &
ejb-tier (ejb-container only).

The reason to chose XML for me is:
a) it is very flexible to future extensions. Imagine we want to change web
server in the future, and the server doesnt support servlets. It is a
php-based framework, which can only access web services to integrate J2EE
applications. So, now, we have 2 choices: the first solution is to have a
free web server with servlet container, and to publish web services with
the servlets. The other choice we have is not to use the free
servlet-enabled web server, but to use web services which are directly
provided by the ejb-container. What would you say is a better choice ? I
think directly using web services from the ejb-container is a better
choice from the start. What would you say ? The only I thing I am not sure
about is whether Sun has clerly made it a requirement for ejb-containers
to support webservices. Have they ? If yes, web services directly provided
from the ejb container are the right choice for the most flexible
framework !! And in this case, I think XML is the right choice right away,
for communication between webserver/servletcontainer and ejb-container.
What would you say ? Would you use XML ? XML is so flexible, we can do the
whole use cases with one XML type of document. If the requirements change,
in the future, we will most likely only have to modify this document, if
at all - because it is very flexible from the start.
I know it is not part of the requirements to think that far, but :
- using this XML approach is simplifying so many things, and even sequence
diagrams, that I want to use it.

Regards,

Jay
 
author and deputy
Posts: 3150
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Jay Sam:
I know it is not part of the requirements to think that far, but :
- using this XML approach is simplifying so many things, and even sequence
diagrams, that I want to use it.
Regards,
Jay


Hi Jay,
I am interested in knowing how XML can simplify sequence diagram ?? Do you have text or weblinks to share for this. ??
Thanks.
 
He puts the "turd" in "saturday". Speaking of which, have you smelled this tiny ad?
We need your help - Coderanch server fundraiser
https://coderanch.com/t/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic