Re: PortletFragment and PortletFragmentHeader.jsp

[Michael Blum <bl...@apache.org>]

I have just changed PortletInfo, PortletModeInfo and 
PortletWindowStateInfo to be static nested classes. I think this changes
should make Pluto's portal run in your Weblogic server.

Michael

Wakida, Reid M. wrote:
> Hi,
> 
> I noticed something peculiar with Pluto's default portal while getting pluto
> to run in Weblogic 8.1.  The PortletFragmentHeader.jsp declares:
> 
> <jsp:useBean id="portletInfo"
> type="org.apache.pluto.portalImpl.aggregation.PortletFragment.PortletInfo"
> scope="request" />
> 
> What's weird is that the PortletInfo inner class cannot be created without
> first creating an instance of the outer PortletFragment class.  However, the
> PortletFragment class doesn't have an empty constructor so I'm not sure how
> the tablib can instantiate an instance of the outer PortletFragment class
> (and therefore the PortletInfo class).  In any case, for some reason this
> implementation works fine on Tomcat.  Perhaps their jsp compiler does
> something special (please excuse me if I missed something in the spec that
> allows this to happen).  However, the Weblogic jsp compiler throws a
> compilation error saying the PortletInfo "class cannot be loaded" (which
> sounds correct). 
> 
> Because the 3 inner classes, PortletInfo, PortletModeInfo, and
> PortletWindowStateInfo, don't access variables in the outer class, I
> extracted the inner classes to top level classes.  I then updated the jsp
> file with the corrected package name, and everything ran fine.
> 
> Is Tomcat's compilation faulty? or is it Weblogic?
> 
> Thanks
> 
> 
> ==============================================
> Reid M. Wakida
> Software Engineer, SAIC
> (858) 826-5174
> 
> 
>