Hi David Sean Taylor-3, Thanks for your response. The “Could be caused by any number of reasons” is part of the problem in identifying the actual problem.
I must have eyeball checked my web.xml, for mistakes, a dozen times. The entry is there – there is not doubt about it. And I have also checked in the following log file – I use JBoss-5.1.0: log/server.log log/portal/jetspeed.log log/portal/jetspeed-deployment.log log/portal/jetspeed-diagnostics.log log/portal/jetspeed-digester.log log/portal/jetspeed-ojb.log log/portal/jetspeed-pluto.log log/portal/jetspeed-scheduler.log log/portal/jetspeed-velocity.log log/portal/webcontent.log log/portal/webcontent-velocity.log All the files except the server.log are either empty or does not contain that message. And server.log has no entry relating to the message – not even after changing the log level to DEBUG . My project is packaged as ear and it includes : jetspeed(-demo) j2-admin webcontent dbbrowser rss my portlet projects. I deploy the ear file to JBoss and it works. All portlets application are registered in the portlet_application and portlet_definition tables in my postgresql database. The problem only occurs when I try to run the portlet from my portlet projects. Portlet Bridge: I have tried the following portlets bridge without any changes portlet-bridge-api-2.0.0-alpha.jar portlet-bridge-impl-2.0.0-alpha.jar and portletbridge-api-2.0.0.CR1.jar portletbridge-impl-2.0.0.CR1.jar I hope someone will tell me the class where I can find the error so that I can debug the source file and identify the real cause(s) of the problem. Thanks again. David Sean Taylor-3 wrote: > > On Thu, Mar 25, 2010 at 4:45 PM, Tender Slim <[email protected]> wrote: >> >> Does anyone know which class is generating the following message: “The >> requested resource (/container) is not available”? I want to find the >> source >> of the damned problem. >> > I think it means your portlet application failed to start. Could be > caused by any number of reasons > Check the tomcat and jetspeed logs for exceptions, stack traces > Also, please verify the web.xml in your *deployed* web application has > an entry like (but not exactly): > > <servlet> > <description>MVC Servlet for Jetspeed Portlet > Applications</description> > <display-name>Jetspeed Container</display-name> > <servlet-name>JetspeedContainer</servlet-name> > <servlet-class> > > org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class> > <init-param> > <param-name>contextName</param-name> > <param-value>j2-admin</param-value> > </init-param> > <load-on-startup>100</load-on-startup> > </servlet> > > <servlet-mapping> > <servlet-name>JetspeedContainer</servlet-name> > <url-pattern>/container/*</url-pattern> > </servlet-mapping> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://old.nabble.com/The-requested-resource-%28-container%29-is-not-available-tp28036609p28042719.html Sent from the Jetspeed - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
