Bug 809525

Summary:	EPP-SP: Javascript priority doesn't work
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Martin Weiler <mweiler>
Component:	Site Publisher	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.2.0.GA, 5.2.0.SP.GA	CC:	epp-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Using the priority field when creating JavaScript content in Content Explorer does not have an influence on the content ordering inside the merged JavaScript file. Changing the priority values has no impact on the generated compressed JavaScript output. A fix is currently being investigated.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Weiler 2012-04-03 15:11:51 UTC

Description of problem:
Javascript files are merged in creation order, exo:priority property is not taken into account.


Steps to Reproduce:
1. start a EPPSP 5.2.0 profile (default)
2. login and go to site explorer.
3. add a new document in js folder of classic site, name it js1
4. type in the content: var js1 = "test 1";
5. save it
6. add another document in js folder, name it js2
7. type in the content: var js2 = "test 2";
8. save it.
Open the classic site in another browser tab, or navigate directly to the merged javascript content at http://localhost:8080/ecmdemo/javascript/eXo/classic/live
There you can see by default the last content is the latest added javascript, named: js2
Accordingly to the documentation if we want to put js2 to load first, its priority needs to be higher, lets put it at 5
Edit js2 javascript and modify the priority accordinly, save it, clear cache and reloads the merged javascript content.
You can see the js order doesn't change.

Comment 2 Martin Weiler 2012-04-11 10:24:56 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Using the priority field when creating javascript content in Content Explorer does not have an influence on the conent ordering inside the merged javascript file. Changing the priority values has no impact on the generated compressed javascript output. A fix is currently being investigated.

Comment 3 Jared MORGAN 2012-04-11 23:31:28 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Using the priority field when creating javascript content in Content Explorer does not have an influence on the conent ordering inside the merged javascript file. Changing the priority values has no impact on the generated compressed javascript output. A fix is currently being investigated.+Using the priority field when creating JavaScript content in Content Explorer does not have an influence on the content ordering inside the merged JavaScript file. Changing the priority values has no impact on the generated compressed JavaScript output. A fix is currently being investigated.