Hook:
Hooks is a feature to catch hold of the properties and JSP files into an instance of the portal as if catching them with a hook. Hook plugins are more powerful plugins that come to complement portlets, themes, layout templates, and web modules. A hook plugin is always combined with a portlet plugin. For instance, the portlet social-portlet is a portlet plugin for Social Office with hooks. In general, hooks would be very helpful tools to customize the portal without touching the code part of the portal. In addition, you would use hooks to provide patches for the portal systems or social office products.
source:Liferay Portal 6 Enterprise Intranets
Hooks is a feature to catch hold of the properties and JSP files into an instance of the portal as if catching them with a hook. Hook plugins are more powerful plugins that come to complement portlets, themes, layout templates, and web modules. A hook plugin is always combined with a portlet plugin. For instance, the portlet social-portlet is a portlet plugin for Social Office with hooks. In general, hooks would be very helpful tools to customize the portal without touching the code part of the portal. In addition, you would use hooks to provide patches for the portal systems or social office products.
source:Liferay Portal 6 Enterprise Intranets
EXT:
EXT is used to customize and extend the Liferay portal. EXT builds a new ROOT webapp and replaces by a huge build mechanism your existing Liferay portal.
The Liferay EXT Environment is where you would ideally make changes to the portal itself. In other words, this is where you customize or “extend” the portal. You may ask, “Why can’t we just make the changes to the portal source directly?” The answer is that you technically CAN, but if and when you have to upgrade, you will have a tough time sorting out what is out-of-the-box and what is customized. EXT Environment keeps things separate.
EXT is used to customize and extend the Liferay portal. EXT builds a new ROOT webapp and replaces by a huge build mechanism your existing Liferay portal.
The Liferay EXT Environment is where you would ideally make changes to the portal itself. In other words, this is where you customize or “extend” the portal. You may ask, “Why can’t we just make the changes to the portal source directly?” The answer is that you technically CAN, but if and when you have to upgrade, you will have a tough time sorting out what is out-of-the-box and what is customized. EXT Environment keeps things separate.
Hooks Plugins
|
Ext Plugins
|
Hook Plugins are used to customize or
override the default behavior of liferay in the form of properties and jsp
files.
|
Ext Plugins are used to customize and
extend the Liferay Portal.i.e almost customize everything.
Nothing but we can create new Root Web
app.
|
Using Hooks we can override
a).Event Handlers(Application startup
events,Login events,Service Events).
b).Language Bundles.
c).Jsp files(either portal or portlet
folder).
d).Model Listners.
e).Services.
|
Using Exts we can customize
a).portal-impl as ext-portal-impl.
b).portal-service as
ext-portal-service.
c).util-bridges as
ext-portal-utilbridges..
d).util-java as ext-util-java.
e).util-taglib as ext-taglib.
f).web as ext-portal-web.
|
These are recommended way of extension
and maintaince easy.
|
These are recommended when there is no
way of implementing required functionality
using hooks.
|
Hot deployable
|
Not hot deployable and server must
restart
|
Combine with other plugins like
portlets.
|
These are some difficulty and
customize almost everything.
|
for more reference click http://liferay6.blogspot.in/2012/07/differences-between-hooks-plugin-and.html
No comments:
Post a Comment