Hi Aaron, Thanks for sharing your experience.
I have tried assessing the application using Tomcat without the portlet stuff incorporated and it works absolutely fine. With the portlet stuff using the bridge when I try to access using J2 (http://localhost:8080/<appcontext>/file, I get the exception - javax.faces.FacesException: Unsupported context type org.apache.catalina.core.ApplicationContextFacade org.apache.portals.bridges.jsf.FacesContextFactoryImpl .getFacesContext(FacesContextFactoryImpl.java:58) javax.faces.webapp.FacesServlet.service(FacesServlet.java:102) org.apache.myfaces.component.html.util.ExtensionsFilter .doFilter(ExtensionsFilter.java:119) As rightly stated by you in the mail with subject - "[J2] Issues/Findings with JSF Portlets" I also double checked my application - 'portlet.xml and web.xml' with the demo application, don't seem to have done anything wrong out there. Currently, my portlet (jsf based) is getting initialized properly and is started fine. But in the page I just see the title and not the body of the portlet. I also tried setting the "ViewPage" as a simple html but still no result. Any more suggestions? Please apprise. Many thanks - Priya - -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 08, 2005 5:31 PM To: [email protected] Subject: Re: FW: Portlet application not available (Exception) <priya.aiyer <at> polaris.co.in> writes: > > > Hello - > > Thanks for your reply Geo John. > > I actually did not write a portlet myself as I am trying to use > Portlet-jsf bridge (portals-bridges-jsf-0.3.jar) provided by apache. It > contains FacesPortlet (extends GenericServletPortlet), which is what I > am referring in "portlet.xml". > > Please refer to this link - > http://portals.apache.org/jetspeed-2/multiproject/jsf-demo/ > I have based my implementation as suggested here. > > Your suggestions please!! > > thanks > - Priya - > Hi Priya, can you access the application outside of jetspeed? Try hitting the application using http://<host>:<port>/<context-name>. You might get a more meaningful stack trace written to your browser (especially if you use FireFox or Mozilla) and/or to the logs. Make sure you check the whole thing too, there may be a "root cause" one at the bottom. This will tell you if there is a problem with the application itself or if the problem lies in how you have deployed it to jetspeed and/or are referring to it. If the app seems to be broken even outside jetspeed, you could try stripping the jetspeed/portlet components from it to debug that first. My other suggestion would be to use the *exact* same contents of WEB-INF/lib and to base your web.xml and portlet.xml on one of the demo apps. I ran into a similar problem that I could not figure out, but when I did this, it fixed my problem. The only other think you might need in your lib is commons-fileupload.jar. I seemed to need this while the demo apps did not for some reason. hope this helps. aaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-Mail may contain proprietary and confidential information and is sent for the intended recipient(s) only. If by an addressing or transmission error this mail has been misdirected to you, you are requested to delete this mail immediately. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment other than by its intended recipient/s is strictly prohibited. Visit Us at http://www.polaris.co.in --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
