Frank, forgot to mention that you need to remove the refrence to that portlet from the PSML file that uses it. For example, If you remvoed the portlet definition for the "page customizer" from j2-admin, and if you have any reference to it in your psml, then you need to remove that.
If your intention is only to not allow users to customize the pages then that's different story. Let me know if that helped. On Fri Mar 13,2009 07:50 pm, Mansour Al Akeel wrote: > Frank, read my comments. > > > On Fri Mar 13,2009 09:25 pm, Frank Otto wrote: > > Thanks for your answer, but I think, you don't understand me. I know how to > > write a portlet and deploy in jetspeed 2. I have write some portlets. > The reason I suggested this because, I thought you need to customize > portlet.xml for the j2-admin, and remove/disable some portlets. For > example in j2-admin you can find the portlet description: > > <portlet id="GroupDetailsPortlet"> > <description> > The Group Details portlet displays a groups details in a tabbed view. > From here you can add, edit, and delete Group information. Place this > portlet on the same page as the Group Browser > portlet. > </description> > <portlet-name>GroupDetailsPortlet</portlet-name> > <display-name>Group Details</display-name> > > <portlet-class>org.apache.jetspeed.portlets.security.groups.GroupDetails</portlet-class> > <init-param> > <description>This parameter sets the template used in view > mode.</description> > <name>ViewPage</name> > <value>/WEB-INF/security/groups/group-details.vm</value> > </init-param> > <init-param> > <name>portlet-icon</name> > <value>network-workgroup.png</value> > </init-param> > <expiration-cache>-1</expiration-cache> > <supports> > <mime-type>text/html</mime-type> > <portlet-mode>VIEW</portlet-mode> > <!-- not implemented yet > <portlet-mode>EDIT</portlet-mode> > <portlet-mode>HELP</portlet-mode> > --> > </supports> > <supported-locale>en</supported-locale> > > <resource-bundle>org.apache.jetspeed.portlets.security.resources.GroupDetailsResources</resource-bundle> > <portlet-info> > <title>Group Detail Information</title> > <short-title>Group</short-title> > <keywords>admin,security,group</keywords> > </portlet-info> > </portlet> > > One way you can disable this, is by removing/commenting-out this > section. Another way is to remove the code in the ViewPage. In other > words, put an empty file for the view. GroupDetailsPortlet supports only > ONE mode (VIEW, other portlets support EDIT and HELP). If youa have > written portlets, you know that for every mode, there's a template file > in velocity or jsp that specifies how the portlet has to appear. > > Usually we do customize portlets, in the themes. So this will apply to > all the portlets. I am imaging you need to replace an existing > control(ie. check box with drop down) , or add/remove a filed, In this > case, yes, the view of the portlet is the place to modify. > > > > > My goal is it, to customize the j2-admin portlets. I want to disable some > > one and change layout of this (f.e.: page customizer). In this, I have > > modified the portlet.xml in j2-admin, but it doesn't work together with my > > custom portal (from tutorial: > > http://portals.apache.org/tutorials/jetspeed-2/01/first-steps.html). I > > can't modify j2-admin with this project like jetspeed 2. I have to > > substitute the portlet.xml after build (mvn -P tomcat,min) manually. I want > > to change j2-admin like my jetspeed 2 project --> substitute standard files > > with my modifications. > > I don't understand what you mean here, but guessing: when you modify the > file, j2-admin doesn't work? If this is the case? did you restart the > server ? Did you try to clean the work dir or the previous dir from > j2-admin ? > > The page you pointed to doesn't > show anything about the build. Where is't failing, and what message are > you getting (if that's the case). > > Can you please be more specific here ? > > > > > > > > > Mansour Al Akeel schrieb: > >> Fank in this case I will direct you to the docs and to follow the > >> tutorial to write a hello world application. Once you are done, you will > >> understand the defference between a portlet application and a portlet > >> and how they interact. Then you can enbale/disable/add portlets to you > >> j2-admin. > >> To change the portlet layout you need to copy any of the existing > >> layout, study it quickly and modify it as you like. > >> On Fri Mar 13,2009 05:08 pm, Frank Otto wrote: > >>> I want to disable some portlets and change layout for the portlets. > >>> > >>> And I want to build j2-admin like my custom portal. > >>> > >>> Mansour Al Akeel schrieb: > >>>> Frank, I didn't understand the challenge you are facing. What do you > >>>> mean by > >>>> "cusomize j2-admin and jetspeed2 together" ? Do you want to disable some > >>>> portlets from j2-admin ? Or do you want to > >>>> change the layout for the portlets from j2-admin ? or you have some > >>>> other requirements. > >>>> My guess is that you want to see the code for the j2-admin and find out > >>>> how it works, right? if that is the case, then it will help you to know > >>>> that j2-admin is nothing but a portlets application. JS2 has two > >>>> portlet applications that are their by default, and they are needed for > >>>> a correct functionality. j2-admin is one of them, the other one is the > >>>> layout portlet. > >>>> Mainly, j2-admin makes it easy to edit the database for users, contents, > >>>> groups, add/remove portlets. If you don't want to use the j2-admin (and > >>>> you don't have to) you can remove it from the default preload list in: > >>>> assembly/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> > >>>> <constructor-arg index='2'> > >>>> <list> > >>>> > >>>> <value>j2-admin</value> > >>>> </list> > >>>> </constructor-arg> > >>>> <constructor-arg index='3'> <value type="boolean">false</value> > >>>> </constructor-arg> > >>>> </bean> > >>>> You can disable it here, but then you are making your life harder at > >>>> this point because you need to edit everything manually. > >>>> I hope this helps. > >>>> On Tue Mar 10,2009 03:15 pm, Frank Otto wrote: > >>>>> I have build my custom portal so, but I can't change j2-admin. I don't > >>>>> unterstand how I customize j2-admin and jetspeed2 together? > >>>>> > >>>>> Vivek Kumar schrieb: > >>>>>> http://portals.apache.org/jetspeed-2.1.3/tutorials/stepbystep/guide-building-custom-portal-maven2.html > >>>>>> > >>>>>> Frank Otto wrote: > >>>>>>> how do I make a custem j2-admin application? > >>>>>>> > >>>>>>> Vivek Kumar schrieb: > >>>>>>>> Hi > >>>>>>>> > >>>>>>>> Use the following configuration in custom j2-admin application. > >>>>>>>> This will take base as j2-admin and will override all the files > >>>>>>>> provide in your custom application. > >>>>>>>> > >>>>>>>> <build> > >>>>>>>> <plugins> > >>>>>>>> <plugin> > >>>>>>>> <groupId>org.apache.maven.plugins</groupId> > >>>>>>>> <artifactId>maven-war-plugin</artifactId> > >>>>>>>> <configuration> > >>>>>>>> <warName>${pom.artifactId}</warName> > >>>>>>>> <overlays> > >>>>>>>> <overlay> > >>>>>>>> <id>jetspeed2</id> > >>>>>>>> <groupId>org.apache.portals.jetspeed-2</groupId> > >>>>>>>> <artifactId>j2-admin</artifactId> > >>>>>>>> </overlay> > >>>>>>>> </overlays> > >>>>>>>> </configuration> > >>>>>>>> </plugin> > >>>>>>>> </plugins> > >>>>>>>> </build> > >>>>>>>> > >>>>>>>> > >>>>>>>> Frank Otto wrote: > >>>>>>>>> can you explain this please? how should I overlay? > >>>>>>>>> > >>>>>>>>> Vivek Kumar schrieb: > >>>>>>>>>> Hi > >>>>>>>>>> > >>>>>>>>>> Jetspeed by default does not provide way to customize J2-admin. > >>>>>>>>>> However you can create another custom portal application and then > >>>>>>>>>> over-lay it with j2-admin application. > >>>>>>>>>> > >>>>>>>>>> Frank Otto wrote: > >>>>>>>>>>> that works, but I can't modify the j2-admin app. I search a way > >>>>>>>>>>> to modify j2-admin. > >>>>>>>>>>> > >>>>>>>>>>> Vivek Kumar schrieb: > >>>>>>>>>>>> Hi > >>>>>>>>>>>> > >>>>>>>>>>>> *mvn -P tomcat,min > >>>>>>>>>>>> > >>>>>>>>>>>> This command will build the custom jetspeed portal and include > >>>>>>>>>>>> the j2-admin. > >>>>>>>>>>>> > >>>>>>>>>>>> for more go here > >>>>>>>>>>>> > >>>>>>>>>>>> http://portals.apache.org/tutorials/jetspeed-2/build-commands.html > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> *Frank Otto wrote: > >>>>>>>>>>>>> hi, > >>>>>>>>>>>>> > >>>>>>>>>>>>> I build a custom jetspeed portal. What is the best way to build > >>>>>>>>>>>>> custom jetspeed2 (2.1.3) with custom j2-admin included? > >>>>>>>>>>>>> > >>>>>>>>>>>>> The tutorial on http://portals.apache.org/tutorials/jetspeed-2/ > >>>>>>>>>>>>> shows only a custom jetspeed 2 build, but not j2-admin. > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> kind regards, > >>>>>>>>>>>>> > >>>>>>>>>>>>> frank > >>>>>>>>>>>>> > >>>>>>>>>>>>> --------------------------------------------------------------------- > >>>>>>>>>>>>> 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] > >>>>>>>>>>> > >>>>>>>>>> --------------------------------------------------------------------- > >>>>>>>>>> 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] > >>>>>>>>> > >>>>>>>> --------------------------------------------------------------------- > >>>>>>>> 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] > >>>>>>> > >>>>>> --------------------------------------------------------------------- > >>>>>> 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] > >>>>> > >>>> --------------------------------------------------------------------- > >>>> 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] > >>> > >> --------------------------------------------------------------------- > >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
