DLProcessor's hard-coded into JSPs

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.1.0 CE RC1
• Fix Version/s: 6.1.0 CE GA1, --Sprint 11/12, 6.2.0 CE M2
• Component/s: DM, DM > Document Library Display
• Labels: None
• Story Points: 4
• Fix Priority: 3
• Similar Issues: Show 5 results ; ;

  LPS-2083	CommandReceivers for FCKEditor are hard coded and not injectable
  LPS-11786	Hard-coded guest groupId in the summary portlet
  LPS-13705	Permissions Registry - Replace hard coded references
  LPS-14165	Message hard-coded in English in social-networking-portlet
  LPS-18792	Expose DLProcessors to hook plugins

At present, JSPs for Document and Media portlet and Media Gallery portlets have DLProcessors hard-coded. This causes problems if somebody is trying to modify the JSPs in a hook and don't have access to the DLProcessors. Ideally, the code should be generic enough that each DLProcessor can output data necessary to produce its own custom URL's. This would mean to refactor the JSPs to just call each of the DLProcessors via its registry and grab its unique URL, if necessary.

[Alexander Chow]

Through this refactor, this should also allow the DLProcessor to have a generic API to access thumbnails and previews, as articulated in LPS-22909.

[Steven Tabesh]

PASSED Manual Testing:
Smoke Test

Fixed on:
Tomcat 7.0.23 + MySQL 5. 6.1.x Revision: c4a010cfe93a7ec891aa5ddcd740732f4adbe3b9.