• 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

Different views of J2EE application ?

 
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Main reason for using MVC design pattern as wriiten in books generally is :

" If application is being used by different types of client i.e browser, PDA,cell phones,desktop application etc. Data access logic cannot be mixed with view as every cleint type has differnt data access logic ,so we need to write different versions of application of every client type ,thats why MVC pattern is used in such cases to separate view from data access logic."

I just want to know what format of view is used by PDA or cell phones clients for a J2EE application,for example clients using browser will have HTML or JSP page,client using desktop application will see SWING pages probably jar file.What format is used by other clients?

Also,how come data access logic for cliens using BROWSER (JSP Page) or DESKTOP application is not same?

Trying to write a J2EE application using MVC design pattern,so these basic comes in mind.

Thanks.
 
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Think about it, when you are using a Desktop application you dont have a container which comes in between the client and the model.

If its a web based solution then you can actually provide security features before getting to the modal using container but not the same for Desktop application.
 
Mishaal Khan
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ok that makes sense,but two more question ,

- data access and mofify logic reamins the same for all client types?

- as between desktop and web application container is the major difference.So whats the major difference between web app client and PDA /Cell phones clients?
 
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Mishaal,

On the first question, yes! If it done properly.

Second one, web client talks HTTP where as cellphone/PDA (WAP) may not be using the same exact communication as IE. There are server or containers which are capable handling both protocols.
 
Mishaal Khan
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Joe.

So when any kind of client once get connected to application server using different protocols, the logic used in model is same for any type of client for data access and modification as Data access logic is independent of client type ?
 
reply
    Bookmark Topic Watch Topic
  • New Topic