2 Replies Latest reply on Feb 7, 2010 1:32 PM by 843798

    Class loader

      after long reading about class loaders and complex situation where two objects might have the same name and such, I wonder if would it be right to assume that I should have a class loader for each defined task, for example importing plugins, importing classes from server, and others?
        • 1. Re: Class loader
          Since "task" can be defined as wide and as narrow as you wish, that doesn't really mean a lot.

          You rarely need to define any classloaders at all. Just use what the environment provides.

          The exception here are systems such as modular plugin systems (OSGi for example), where you'll do lots of classloader magic.
          • 2. Re: Class loader
            well, actually I do make a plugin system for my application, and I found some nice examples on the net, that once combined together should perform pretty nicely.