|
Home > Archive > WebSphere Portal Server > January 2005 > Classloader hierarchy for portal
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Classloader hierarchy for portal
|
|
| Brian J. Sayatovic 2005-01-27, 5:53 pm |
| I think I understand how the classloader hierarchy for a portal server works
now, and was hoping someone could confirm this.
My understanding is that each WAR (which can contain multiple portlets) has
its own classloader, just like a normal WAR. The parent classloader of each
WAR is the WebSphere Portal Server classloader (which is really the
classloader of the WPS EAR which I think is an EJB/dependency classloader).
Above that are the normal WebSphere extensions classloaders, WebSphere
classloader, and on up through to the bootsrap classloader of the VM.
But where do the shared/app and shared/ext libs get injected into this
hierarchy?
Regards,
Brian.
| |
| Oliver Meyer 2005-01-27, 5:53 pm |
| Brian,
you should have a look at the InfoCenter at
http://publib.boulder.ibm.com/pvc/w...nter/index.html
If you search for "classloader" you will get the chapter "creating a
simple portlet" as a result. At the bottom of this chapter there is a
diagram which shows the portal classloader hierarchy for portlets.
I hope this helps.
Oliver
| |
| Brian J. Sayatovic 2005-01-27, 5:53 pm |
| Thanks, Oliver. That was exactly what I needed!
Regards,
Brian.
"Oliver Meyer" <meyer_oliver@gmx.de> wrote in message
news:ctb3kf$6e64$1@news.boulder.ibm.com...
> Brian,
> you should have a look at the InfoCenter at
> http://publib.boulder.ibm.com/pvc/w...nter/index.html
> If you search for "classloader" you will get the chapter "creating a
> simple portlet" as a result. At the bottom of this chapter there is a
> diagram which shows the portal classloader hierarchy for portlets.
> I hope this helps.
>
> Oliver
|
|
|
|
|