Hi Eranda, Thank you for the feedback and the explanation. I did an analysis of the use cases related. As you suggested, will do the analysis furthermore and will prepare a separate document.
Thanks, Sithumini On Mon, Nov 24, 2014 at 10:33 AM, Eranda Sooriyabandara <[email protected]> wrote: > Hi Sithumini, > I think you should analyse the use cases related to do, what is the > expectation of comparing two Service, WSDLs, Schemas or a policy. > > Service - Whether there is a change in the service version + need to > highlight the WSDL if there is a definition change between two versions > WSDL - What are the changes in the service definition + need to highlight > WSDL if there is a change in imported WSDL + need to highlight Schema or > Policy if there is a message format change or policy change > Schema - What are the changes in message formats + need to highlight > Schema if there is a change in imported Schema > Policies - What are the change in policies > > The above comparison should be done in order to see a change in service. > Comparing just service content which is in the registry is not complete. > > Let me give you an example, > > There is a service EchoService version 1.0.0 and there is > In the next version 2.0.0 > > Consider the following changes to the service in 2.0.0 version, > > 1. A new method has been introduced - Now when we comparing two WSDLs > related to EchoService version 1.0.0 and 2.0.0 the user should be able to > clearly see that there is a method has been added (showing the added > elements is not good enough). > 2. Input message body changed - Now the schema related to the WSDL is > changed in EchoService 2.0.0 compared to 1.0.0. Now user should be able to > clearly see the change of message formats when comparing schemas. Not only > that but when comparing WSDLs this change should be notified by > highlighting the methods which uses that schema and schema import. > 3. Policy has been changed related to service. Now the policy related > to a WSDL changed in EchoService 2.0.0 compared to 1.0.0. Now user should > be able to clearly see the policy changes when comparing policies. Not only > that but when comparing WSDLs this change should be notified by > highlighting the policy import. > > The same model can be applied to WADL as well. > > Hope you understood what should be the end goal. Please raise if there is > any doubt or thought. > > > thanks > Eranda > > > >> *Usage * >> >> - Can use to examine the structure of the resource. >> - Compare the different versions of the same resource. For example >> get the comparison between two version of the same service, WSDL, WADL >> etc.., TestService_1.0.0 and TestService_1.1.0 >> - Compare and differentiate completely different resources of same >> type. For example get the comparison between two resources, TestService1 >> and TestService2. >> - Discover which elements were added, changed or removed. >> - Understand how changes effect the contract of the resource. >> >> >> *Advantages* >> >> - User-friendly rich GUI. >> - Easy to understand. >> - More attractive to non technical people. >> >> >> *Background* >> I did an initial background research on areas such as existing >> tools/libraries which has been used in similar scenarios, design overview >> of the feature, implementation mechanism etc.. . >> >> Document [2] contains the findings on free open source tools and >> libraries for compare XML related documents. >> Document [3] contains mock up design for WSDL comparison. >> >> Please be kind enough to provide feedbacks on anything need to be added >> or removed from the above. >> >> [1] https://redmine.wso2.com/issues/3403 >> [2] >> https://docs.google.com/a/wso2.com/spreadsheets/d/1RiTf-izMhHKOv386RPeOhfFX897aHfDJaUWiB8VaXjI/edit?usp=sharing >> [3] >> https://docs.google.com/a/wso2.com/document/d/1dDbrSU5GmrTypSgZP6gbd76pudnKHsJTPpd_u2vD8LE/edit?usp=sharing >> >> Thank you, >> Regards, >> Sithumini >> >> -- >> -- >> Sithumini Senevirathne >> Software Engineer >> WSO2 Inc. - lean . enterprise . middleware | wso2.com >> >> email: [email protected], mobile: +94 756977999 >> > > > > -- > > *Eranda Sooriyabandara*Senior Software Engineer; > Integration Technologies Team; > WSO2 Inc.; http://wso2.com > Lean . Enterprise . Middleware > > E-mail: eranda AT wso2.com > Mobile: (812) 964-9032 > Linked-In: http://www.linkedin.com/in/erandasooriyabandara > Blog: http://emsooriyabandara.blogspot.com/ > > > > > -- -- Sithumini Senevirathne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com email: [email protected], mobile: +94 756977999
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
