Sample Expando Hook

Hi guys!

Last week I created the sample expando hook, a simple example to show how easy is to extend portal entities on startup without using the UI. 
 
The main goal of this work method is to allow Liferay users to extend portal entities from a plugin, so that they don't need to repeat the same action (the creation of new fields for their entities) in every installation they do. 
 
You can find it ready to use in the plugins' hooks svn ( http://svn.liferay.com/browse/plugins/trunk/hooks)
 
I have based this development in this Ray's blog entry ( http://www.liferay.com/web/raymond.auge/blog/-/blogs/adding-expandos-from-a-startup-hook) and here's the explaination so that you can adapt it to your concrete use case:
 
In portal.properties you declare your class so that it is launched on startup:
 
application.startup.events=com.liferay.sampleexpando.hook.events.StartupAction
 
In StartupAction, in doRun, you do the main things:
 
 
1.- We get a reference of (or create) the table ExpandoTableConstants.DEFAULT_TABLE_NAME, determining the portal entity we are working with (in this case it'll be the calendar events - CalEvent)
 
                try { expandoTable = ExpandoTableLocalServiceUtil.addTable( CalEvent.class.getName(), ExpandoTableConstants.DEFAULT_TABLE_NAME); } catch (Exception e) { expandoTable = ExpandoTableLocalServiceUtil.getTable( CalEvent.class.getName(), ExpandoTableConstants.DEFAULT_TABLE_NAME); }
 
2.- We add the new column using a custom name ("sampleColumn") and its type (ExpandoColumnConstants.STRING in this case):
 
     ExpandoColumnLocalServiceUtil.addColumn(
   expandoTable.getTableId(), "sampleColumn",
                   ExpandoColumnConstants.STRING);
 
And that's all!
I hope it'll be useful
Regards
Juan Fernández

 

Blogs
The explained aproach lacks one thing - schema incremental update. If you add/drop some column, you need to drop whole table, or create DML migration scripts for expando tables (which is entertaining task for one entity, but if you have a lot of entities it could take whole day, if not more)
Why? A simple

ExpandoColumnLocalServiceUtil.deleteColumn(ong companyId, long classNameId, String tableName, String columnName);

will remove the column from the table as well as all values associated with it!
Hm, so your approach is to pollute code with such statements? So for every added/removed column some precondition should exist? What if I add 50 columns in a row.
Also I don't understand how it will work if I want to change type of column, for example from ExpandoColumnConstants.STRING to ExpandoColumnConstants.DATE.
Hi Pavel:

1.- The idea is to avoid doing this by hand in every installation of the product. If you have a plugin you can deploy it in the server and it'll do all that tasks.

2.- The number of columns is not important: just add it in the hook code.

3.- You can use the type you need for your field using ExpandoColumnConstants and it shouldn't be a problem

Regards
Juan
I've tried to run this code in LR6, but it seems that addTable and getTable are deprecated. If I'm not wrong, what is the right way to add expandos in LR6? Thanks.

Podrías darme una manito u orientarme con esto. Gracias!
Sorry, I didn't look so well. The method is deprecated but it still exists. the new method has a new added companyId parameter. So I'm going to see what happen if I pass the companyId param.
Hi Francisco:
thanks for the update. I didn't realize this has changed. If you add the companyId to the method it'll be ok.
Tell me if you achieve this and everything works ok
Saludos,
Juan
Here is how I did it in LR6. Some extra comments in http://www.liferay.com/community/forums/-/message_boards/message/5165696

protected void setupExpandos(long companyId) throws Exception {
ExpandoTable table = null;
try {
table = ExpandoTableLocalServiceUtil.addTable(
companyId, User.class.getName(), ExpandoTableConstants.DEFAULT_TABLE_NAME);
}
catch (DuplicateTableNameException dtne) {
table = ExpandoTableLocalServiceUtil.getTable(companyId, User.class.getName(), ExpandoTableConstants.DEFAULT_TABLE_NAME);
}
String column = "";
column = "alternativeEmail";
try { ExpandoColumnLocalServiceUtil.addColumn(table.getTableId(),column, ExpandoColumnConstants.STRING);
} catch (DuplicateColumnNameException dcne) { System.out.println(column+" already exists!"); }


try {
ExpandoColumn ecolumn = ExpandoColumnLocalServiceUtil.getColumn(companyId, User.class.getName(),ExpandoTableConstants.DEFAULT_TABLE_NAME,column);

//I had to add UPDATE perms to GUEST in order to set column values from the hook.
Permissions.setRolePermissions(companyId,ExpandoColumn.class.getName() ,ecolumn.getPrimaryKey(), RoleConstants.GUEST, new String[] { ActionKeys.VIEW, ActionKeys.UPDATE});

} catch(Exception e) { }
}
This example is no longer available, can anyone tell me where to get this sample ?
[...] Super ! Merci beaucoup pour ces précisions qui me seront très utiles ! Je vais partir sur les Expandos donc, d'autant plus que le nombre de documents dans le système ne sera pas très élevé (pas plus... [...] Read More
Hi Juan!

This article was really helpful, thanks. But I have a doubt: How do you set the length of a string column?

Thanks,
Flor.
Hi Juan,
I wonder if I can use this approch to add custom fields to any entity,
because from GUI Control Pannel/Custom fields only few entities are listed.

Thanks,
Nabil