[mashup-dev] [jira] Commented: (MASHUP-729) Add Hashing to make sure the mashup js file has actually changed before updating the registry.

[Tyrell Perera (JIRA)]

    [ https://wso2.org/jira/browse/MASHUP-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001#action_16001 ] 

Tyrell Perera commented on MASHUP-729:
--------------------------------------

There are at least three areas to be addressed;

  1. Unnecessary addition of mashups to the registry during a server startup.
  2. during service re-deployment (ie from the UI)
  3. during saving and edited service (sometimes there might not be changes at all between to 'save mashup' invocations)

I have addressed 1 in revision 14945.

2 and 3 however requires more information on how the registry handles versioning. My idea is to rollback to the latest revision in both cases instead of adding the mashup again as we do at the moment.

> Add Hashing to make sure the mashup js file has actually changed before updating the registry.
> ----------------------------------------------------------------------------------------------
>
>                 Key: MASHUP-729
>                 URL: https://wso2.org/jira/browse/MASHUP-729
>             Project: WSO2 Mashup Server
>          Issue Type: New Feature
>            Reporter: Tyrell Perera
>            Assignee: Tyrell Perera
>             Fix For: 1.1
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira