By default in IBM Websphere Application server the PARENT_FIRST option is selected for
class loading.
Classloadingdelegation Model.
As mentioned in the diagram
if delegation model is set to PARENT_FIRST it will try to load from the application jars which are present in WEB-INF/lib or WEB-INF/classes or included in shared library references.
If the class expected is not present in the application loader it will look up to it parent until Bootstrap.
So in PARENT_FIRST the look up for classes is always upwards .If a class referenced by Ext loader is present in application level then that class will not be visible and throw exception.
PARENT_LAST is just opposite to PARENT_FIRST it look for classes downwards from root classloader.
class loading.
Classloadingdelegation Model.
As mentioned in the diagramif delegation model is set to PARENT_FIRST it will try to load from the application jars which are present in WEB-INF/lib or WEB-INF/classes or included in shared library references.
If the class expected is not present in the application loader it will look up to it parent until Bootstrap.
So in PARENT_FIRST the look up for classes is always upwards .If a class referenced by Ext loader is present in application level then that class will not be visible and throw exception.
PARENT_LAST is just opposite to PARENT_FIRST it look for classes downwards from root classloader.
No comments:
Post a Comment
Your suggestions please