• 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
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Devaka Cooray
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
Bartenders:
  • Carey Brown
  • Roland Mueller

Class Loader - Applet

 
Ranch Hand
Posts: 395
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
In JVM specification its been mentioned, that if I am using different classloaders ( custom class loaders ) then I cannot reference the classes loaded in another class loader. This way it creates logical grouping like "namespace" for the class loaders.
An example is provided, which considers the applet getting loaded in the client side plug-in. If the package and class name of the applet is same but the server IP is different then for each server IP a difference class loader is instantiated and it takes care of loading the classes for the applet.
My question is does the JVM on the client ( java plug-in )use different class loaders for different IP address or different browser windows ?
What happens If I open the same page having applet in two different windows? Does it load two class loaders or just a single class loader for the server IP is used?
Thanks for the time.
Cheers.
 
But how did the elephant get like that? What did you do? I think all we can do now is read this tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic