title: Glassfish 3.1.2 reload needed jars after application deployment
body: <p>I have an ebj using some external libraries (in this case, those libraries are written by myself). I have included them in my EJB.</p>
  
  <p>The problem is that glassfish seems to load the needed jars only once (at first deployment) and consider he already has the jars for further deployment. It's only an assumption but if i do any changes in one of the library used by the EJB, redeploy the EJB, the changes made will not be applied... Glassfish still use the old jars he might keep in cache or something like that (i can find any mark of the jars in the the glassfish repositories).</p>
  
  <p>The only solution i have found so far is restarting the server... not really suitable for development/test session where you have to wait for glassfish to restart every little change you make.</p>
  
  <p>My question is: Is there a way to avoid this behavior and force glassfish to reload needed jars at each deployment?</p>
  
  <p>Thanks for reading me.</p>
  
  <p>Note: I'm working on local using netbeans to deploy but doing it straight from the glassfish admin console lead to the same result.</p>