• 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

Enterprise application setup

 
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm trying to port an application to a J2EE application architecture and am wondering what the best way to set it up is. It consists of a web front end (servlets) which I've set up as a web module, support jars (such as jdom, xerces etc) which I've added as utility jars to the enterprise application. The other parts are communication components that are plain old java classes and I'm not sure what to do with these! If I set them up as utility jars for the application I can't debug through them (at least I think this is true!) and makes their development awkward. I've been told not to set them up as client components, so the only alternatives I see are either lumping everything into the web module (I'd rather not do this as there's quite a lot of code in the comms part) or setting them up as web modules. Anyone got any ideas on the best way forward??
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic