Seems like I erred when I said 2.1-dev did not work. I simply forgot to war:install, so it kept deploying my old 2.0-based custom portal.
I can see the default login page now. Thanks for all the suggestions! AC On 2/14/06, Alan Chiang <[EMAIL PROTECTED]> wrote: > > Thanks Jacek, > > Seems like I just had to wait a bit, the VelocityTwoColumns error does > not appear anymore. What does appear now is: Failed to find the Window > Access on portlet initialization, with nothing more. > > I should note that I have not deployed any kind of custom portlets > whatsoever. I'm simply attempting to deploy the vanilla jetspeed portal > from a j2:portal.genapp, with 0 changes to the files (or some minimal ones > to kick start it to work). > > Looking through the jetspeed.log, a lot of problems seem to come from > j2-admin::<some_fragment>. It could possibly be that these fragments are > not being registered properly in the database for whatever reason. I > strongly believe this is reason, only because the VelocityTwoColumns error > no longer appeared once the entry appeared in the PORTLET_ENTITY table. I > am new to J2, so I'm not sure of the mechanism to load portlets and/or their > fragments into the DB. I may also note that my connection to MySQL 4.x is > present and working. > > I have also retried using 2.1-dev, no luck. > > Thanks! > > AC > > PS: > > DEBUG org.apache.jetspeed.portalsite.impl.PortalSiteSessionContextImpl - > Selected folder historical page: path=/default-page.psml > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-3 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for j2-admin::LocaleSelector > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-3 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-12 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for j2-admin::LoginPortlet > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-12 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-22 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for > j2-admin::ForgottenPasswordPortlet > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-22 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-23 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for > j2-admin::UserRegistrationPortlet > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-23 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-7 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for demo::PickANumberPortlet > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-7 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-16 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for demo::RoleSecurityTest > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-16 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-9 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for demo::IFramePortlet > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-9 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-17 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for demo::UserInfoTest > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-17 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-18 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for demo::BookmarkPortlet > WARN org.apache.jetspeed.decoration.DecorationValve - Unable to initalize > actions for fragment dp-18 > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-1 attempting to > auto-generate... > DEBUG org.apache.jetspeed.aggregator.impl.PageAggregatorImpl - Rendering > portlet fragment: [[name, j2-admin::LocaleSelector], [id, dp-3]] > INFO org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl- No > portlet entity defined for fragment ID dp-3 attempting to > auto-generate... > WARN > org.apache.jetspeed.components.portletentity.PersistenceBrokerPortletEntityAccess- > Failed to retrieve Portlet Definition for j2-admin::LocaleSelector > ERROR org.apache.jetspeed.aggregator.impl.PortletRendererImpl - > java.lang.IllegalArgumentException: Cannot pass a null PortletDefinition > to a PortletEntity. > > On 2/14/06, Jacek Wiślicki <[EMAIL PROTECTED]> wrote: > > > > Wiadomosc od Alan Chiang z 2006-02-14 20:56 brzmiala: > > > > > Will keep looking for a solution, but if anyone can provide some > > insight > > > that would be wonderful. > > If a deployment process was correct and the portlet is registered in > > database, there might be also an error in portlet name in the PSML > > document (page) and the deployment descriptor (portlet.xml). In > > portlet.xml portlel "id" attribute and "portlet-name" element should be > > the same (as far as I remember). Furthermore, the webapp referred to in > > the .psml (webapp::portlet_id) file should be spelled exactly the same > > as it is in portlet.xml (case-sensitive). > > > > -- > > pozdrawiam, > > Jacek Wislicki > > > > [EMAIL PROTECTED] > > tel.: +48 502 408 444 > > gg: 2540358 > > skype: jacek_wislicki > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
