I have a set of EJBs that use legacy code outside the Jboss container. The jar files containing the legacy code are listed in a tag in jboss-service.xml file, so the EJB code can see the required legacy classes. My question is this: Is there a way to tell Jboss to load non-archived classes from a directory and to make sure that this directory is searched first? I am trying to preserve a patching policy where the new classes are stored into '../classes' directory and that directory is in the classpath before the jar files which contain the released application code.
Probably not the best way to package this application, but I can't do anything about that right now. Should I look into writing an Mbean to load the patch classes into UnifiedLoaderRepository before the extension jars (released app code) get loaded, or is there a simple configuration setting to do this kind of class loading control?