Oh I see now what you meant. Apologies, I misunderstood -- I thought you were overriding the action completely. I ran into this issue recently actually and I found a solution, though I wasn't sure it was the best option at the time. In my case I had to distinguish between the ADD and the UPDATE methods. The reason being that in the case of an UPDATE scenario there is actually a fileEntryId in the request, otherwise I used the fields that we passed when the item was added to retrieve the file object that was just added. This works for our case, but we're no in an environment that is under a lot of load or one that contains files with the same names, etc. Here is a stub of the process action that we used.
... again, I don't want to advocate this as the best solution because I can think of a few scenarios where this might not stand up, but for our solution, given our constraints, it was an acceptable solution.
Ideally you would be able to access the updateFileEntry on the originalStrutsAction, but it's protected so no dice. I suppose another alternative is to use an EXT plugin and then create you custom action such that it EXTENDS the EditFileEntryAction ... then you could access the protected method and use something cleaner like this --
.. personally though I try to avoid EXT plugins like they are the plague. If you already have one in your solution though, then you might as well get the most of out it. I am curious to know which option you go with so let me know
public void processAction(StrutsPortletAction originalStrutsPortletAction, PortletConfig portletConfig, ActionRequest actionRequest, ActionResponse actionResponse) throws Exception
{
// perform original action first
originalStrutsPortletAction.processAction(originalStrutsPortletAction, portletConfig, actionRequest, actionResponse);
// get the command
String cmd = ParamUtil.getString(actionRequest, Constants.CMD);
FileEntry fileEntry = null;
// if the command is add or update grab the publish date and set the expando value
if ( cmd.equals(Constants.UPDATE) )
{
long fileEntryId = ParamUtil.getLong(actionRequest, "fileEntryId", 0);
if ( fileEntryId > 0 )
{
// do something here
}
}
else if ( cmd.equals(Constants.ADD) )
{
String title = ParamUtil.getString(actionRequest, "title", null);
long folderId = ParamUtil.getLong(actionRequest, "folderId", -1);
long groupId = PortalUtil.getScopeGroupId(actionRequest);
fileEntry = DLAppLocalServiceUtil.getFileEntry(groupId, folderId, title);
if ( fileEntry != null )
{
// do something here
}
}
if ( Validator.isNotNull(fileEntry) )
{
Indexer indexer = IndexerRegistryUtil.getIndexer(DLFileEntry.class);
if ( _log.isDebugEnabled())
_log.debug(LogUtil.format("indexer retrieved: " + indexer.getClass().getName()));
indexer.reindex(fileEntry);
}
}... again, I don't want to advocate this as the best solution because I can think of a few scenarios where this might not stand up, but for our solution, given our constraints, it was an acceptable solution.
Ideally you would be able to access the updateFileEntry on the originalStrutsAction, but it's protected so no dice. I suppose another alternative is to use an EXT plugin and then create you custom action such that it EXTENDS the EditFileEntryAction ... then you could access the protected method and use something cleaner like this --
public class MyEditFileEntryAction extends BaseStrutsPortletAction {
public void processAction(StrutsPortletAction originalStrutsPortletAction, PortletConfig portletConfig, ActionRequest actionRequest, ActionResponse actionResponse) throws Exception {
String cmd = ParamUtil.getString(actionRequest, Constants.CMD);
try {
if (cmd.equals(Constants.ADD) ||
cmd.equals(Constants.UPDATE) ||
cmd.equals(Constants.UPDATE_AND_CHECKIN)) {
UploadPortletRequest uploadPortletRequest =
PortalUtil.getUploadPortletRequest(actionRequest);
ServiceContext serviceContext = ServiceContextFactory.getInstance(
DLFileEntry.class.getName(), uploadPortletRequest);
fileEntry = updateFileEntry(portletConfig, actionRequest, actionResponse);
}
else {
originalStrutsPortletAction.processAction(originalStrutsPortletAction, portletConfig, actionRequest,actionResponse);
}
}
} catch (Exception e){
e.printStackTrace();
}
}
public String render(StrutsPortletAction originalStrutsPortletAction, PortletConfig portletConfig, RenderRequest renderRequest, RenderResponse renderResponse) throws Exception {
//System.out.println("My Custom Render Method is Called");
return originalStrutsPortletAction.render(null, portletConfig, renderRequest, renderResponse);
}
}.. personally though I try to avoid EXT plugins like they are the plague. If you already have one in your solution though, then you might as well get the most of out it. I am curious to know which option you go with so let me know