• 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
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

PartII: jsp and swing clients

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am thinking to use business delegate and service locator for swing client. My question is: should the swing connect to web servers or directly to the app server. If connecting the web server, swing can re-use the same delegates and service locator created for jsp/servlet, but there might be performance overhead incurred. If connecting the app server directly, the code for delegate and service locator will be somehow duplicated.

Here I am assuming the swing program will be run within the company's intranet. Any comment is very much appreciated.
 
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Robin,

You can consider to make your swing application connect int the application server directly using business delegates and an service locator.

For the assignment pourpouses, you have to define in your solution that you will use 'an business delegate' and 'an service locator'. This is not redudance because at the real world, thare are techniques to avoid the repetition, using common jars for example.

If you care about how your architecture will be evaluated about redundant components, try to use some package diagrams and put the commons components (business delegate, service locators, pojo entities), at packages there are accessible at all the major packages, such as the business package, the controller package and so on.

Even the assignment did not ask for an package diagram, provide one could be a very good idea because your architecture will mitigate two main things: redundance and component dependency.

Best Regards,
 
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, Ricardo is right. You should design an architecture that works for both kinds of clients (Web and Swing), and by using common Jars you can achieve that.
 
Robin ng
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for your great advice.
reply
    Bookmark Topic Watch Topic
  • New Topic