As far as I understand, the repository is a sort of hierarchical namespace for the classes dynamically loaded at runtime. There is one default-repository, and each application can define an app-specific one to isolate the classes it uses.
I didn't find a 'precise' definition, but there is some article in the JBoss wiki which explains how JBoss class loading works: I think my problem was that the first app did not specify a loader repository, so the classes were inserted in the default repository. When the second app was deployed, it had its own repo declared, but by default JBoss always looks up classes in the default repo. So the class was already there in an older version - and this crashed. By adding: <loader-repository-config> java2ParentDelegation=false </loader-repository-config> to the <loader-repository> entry, it should be possible to override the classes in the default-repository - but I haven't tried that yet. So we just escaped the Dll-hell to find ourselves in the classloader-hell ;-) Matthias _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=284#284 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
