• 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 ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
  • Piet Souris
  • Himai Minh

Application Development Structure

Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am trying to create standard way of storing software objects when using servlets and applets.

When I use the following structure, things work o.k. in that, my applet will be successfully loaded, which in turn calls the servlet successfully:
[my execution call is http://localhost:8080/myapplications/temp (index.html calls callapplet.html)].

HOWEVER, when I move the applet.class file down to temp under WEB-INF, it does not work. I tried various combinations of CODEBASE parameters in the callapplet.html file, but maybe I am missing something - the applet just does not get loaded.

Is there a solution that I am missing or is this a limitation that one has to live with? The reason I am wanting to move the applet.class file down under WEB-INF/classes/temp is to keep all the class files in one place.

Is there an alternative arrangement of directory structure?

Thanks in advance.

[BSouther Edit: added code tags]
[ April 18, 2006: Message edited by: Ben Souther ]
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Anything you put under the WEB-INF directory will not be directly accessible to the end user, you can only put there "helper-stuff" like your server side classes, libs,...

I guess that an applet needs to be directly available to the end user because, from the server point of view, this is just file that the user agent wants to download. As far as the server is concerned, there is nothing special in the fact that the browser will then execute it. So the root of the web app sounds like a correct place, although I agree it looks messy.

Maybe is there a way to map a ressource from some WEB-INF/applet-ressources/ directory to a public name thanks to the DD ?
If I had asked people what they wanted, they would have said faster horses - Ford. Tiny ad:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth
    Bookmark Topic Watch Topic
  • New Topic