I've never tried what you are trying, but I am wondering if you can accomplish it with a Struts Action override? I am looking at the GA6 conde base for 6.2 and I have found class called ExportImportAction.java. In the processAction method I can see --
though given the path and parameters, that looks like it might be specific to portlets? I can also see a class JournalArticleStagedModelDataHandler which aligns a bit better with what you are saying, so perhaps that is what you are looking for? If it is, then the updates might be a challenge because that class is in the portal-impl and is being referenced in the liferay-portlet.xml
One option is to use an EXT plugin -- but I hate them, as do most I think. Another option which I have used before (to avoid EXTs), though I am not sure I should sanction it
, is to tap into the *Registry class. A lot of the classes that are found in the liferay-portlet.xml are recorded in a registry when deployment occurs. The good news is that the RegistryUtil classes are almost always in the portal-service so you can access them in your code.
I have, for example, used this approach in the past to change the handler class that is registered for one of the models to change the way the item renders in the Activity Feed portlet. You could have a look at the com.liferay.portal.kernel.lar.StagedModelDataHandlerRegistryUtil and then maybe use a startup hook to register your custom StagedModelDataHandler with the logic you need?
...
}
else if (cmd.equals("publish_to_live")) {
hideDefaultSuccessMessage(actionRequest);
StagingUtil.publishToLive(actionRequest, portlet);
sendRedirect(actionRequest, actionResponse);
}
...though given the path and parameters, that looks like it might be specific to portlets? I can also see a class JournalArticleStagedModelDataHandler which aligns a bit better with what you are saying, so perhaps that is what you are looking for? If it is, then the updates might be a challenge because that class is in the portal-impl and is being referenced in the liferay-portlet.xml
<staged-model-data-handler-class>com.liferay.portlet.journal.lar.JournalArticleStagedModelDataHandler</staged-model-data-handler-class>One option is to use an EXT plugin -- but I hate them, as do most I think. Another option which I have used before (to avoid EXTs), though I am not sure I should sanction it
, is to tap into the *Registry class. A lot of the classes that are found in the liferay-portlet.xml are recorded in a registry when deployment occurs. The good news is that the RegistryUtil classes are almost always in the portal-service so you can access them in your code. I have, for example, used this approach in the past to change the handler class that is registered for one of the models to change the way the item renders in the Activity Feed portlet. You could have a look at the com.liferay.portal.kernel.lar.StagedModelDataHandlerRegistryUtil and then maybe use a startup hook to register your custom StagedModelDataHandler with the logic you need?