This did not do it..
Mansour Al Akeel wrote: > > If you look into assembley/prefs.xml > > <bean id="PreferencesProviderImpl" > class="org.apache.jetspeed.prefs.impl.PersistenceBrokerPreferencesProvider" > name="prefsPersistenceBroker" init-method="init"> > <constructor-arg index="0"> > <value>JETSPEED-INF/ojb/prefs_repository.xml</value> > </constructor-arg> > <constructor-arg index="1"> > <ref bean="preferencesCache" /> > </constructor-arg> > <!-- list of portlet applications default preferences to preload, > leave list empty to not preload --> > <constructor-arg index='2'> > <list> > <value>j2-admin</value> > </list> > </constructor-arg> > <!-- preload ALL Entities: warning this can chew up lots of memory --> > <constructor-arg index='3'> > <value type="boolean">false</value> > </constructor-arg> > </bean> > > > I am talking about the comments that says : > <!-- list of portlet applications default preferences to preload, > leave list empty to not preload --> > This means that j2-admin has to be available during jetspeed load. I am > not sure how you have implmeneted your own login screen, but if you > don't want to use j2-admin, remove the referece to it, and replace any > reference in jetspeed to the new portlets you have developed. If I am > not wrong, jetspeed comes with jsp pages for logins without using the > login portlet. > > I am not sure about 2.0 (I am newbie too), so I can not provide an advice > about old > functionality. > > I hope this helps. > > > > > On Fri Apr 24,2009 07:45 am, brunp wrote: >> >> >> Mansour Al Akeel wrote: >> > >> > Do you have j2-admin.war deployed in the server context path ? >> > >> > Is't being extracted ? >> > The login portlet is part of the j2-admin application. This is a >> portlet >> > application that contains portlets to assist in managing jetspeed. >> > >> >> Looked into it, never had the j2-admin.war deployed at all.....in our >> prior >> deployment. We had >> our own LoginPortlet definition. That being said, has anything changed >> much >> between Jetspeed >> 2.0 to 2.1.3 that would require the j2-admin.war having to be deployed >> into >> our environment to >> assist in creating those portlet's? >> >> Paul >> >> -- >> View this message in context: >> http://www.nabble.com/So%2C-now-I-hav-a-%22Entity-Access%22-issue-tp23039513p23217902.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] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/So%2C-now-I-hav-a-%22Entity-Access%22-issue-tp23039513p23257946.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]
