System and method to convert a webpage built on a legacy framework to a webpage compatible with a target framework
A computerized system converts a webpage built on a legacy framework to a target framework. The system allows a user to identify and download one or more webpages for conversion. The system converts the webpage to XML and outputs in a data store, such as an XML file. The system parses and converts the XML file into big object file. The system, through conversion logic, converts the big object file into a target component market. The system then reports the conversion, including any processing logs and error files, to a user. The system report include highlighted errors from any step of the conversion along with automatically generated recommendations for error corrections.
1. A method for converting a webpage, the method comprising:
retrieving an artifact bundle comprising a webpage;
converting the webpage into extensible markup language (XML) as a converted XML webpage, wherein the converted XML webpage is contained in an output XML file and wherein the converted XML webpage comprises an XML tag;
identifying an attribute of the XML tag;
adjusting a complexity level to be at a higher level upon identifying said attribute of said XML tag to be one or more predefined types;
converting the XML tag to a target component markup based on said complexity level; and
reporting a result metric related to the XML tag that is converted to the target component markup.
2. The method of claim 1 , further comprising parsing the output XML file into a hierarchical tree structure.
3. The method of claim 2 , wherein the identifying the attribute of the XML tag further comprises:
identifying the attribute as an identification comprising a parameter or an event; and
storing the identification of the attribute in the output XML file.
4. The method of claim 3 , wherein the converting the XML tag to a target component markup further comprises:
converting the output XML file to a big object file; and
converting the big object file to the target component markup.
5. The method of claim 1 , further comprising:
scanning the artifact bundle; and
identifying at least one dependency between a first artifact and a second artifact of the artifact bundle.
6. The method of claim 1 , wherein the reporting the result metric further comprises:
reporting a conversion error related to converting the webpage into XML or converting the XML tag to the target component markup;
marking the conversion error; and
recommending, to a user, a solution to resolving the conversion error.
7. A system for converting a webpage, the system comprising:
a computer comprising a processor and a memory;
a connector module stored in the memory of the computer which, when executed by the processor, is configured to retrieve an artifact bundle comprising a webpage;
a transformer module stored in the memory of the computer which, when executed by the processor, is configured to convert the webpage into extensible markup language (XML) as a converted XML webpage, wherein the converted XML webpage is contained in an output XML file and comprises an XML tag;
an XML to target artifact bundle module stored in the memory of the computer which, when executed by the processor, is configured to:
identify an attribute of the XML tag;
adjust a complexity level to be at a higher level upon identifying said attribute of said XML tag to be one or more predefined types; and
convert the XML tag to a target component markup based on said complexity level; and
a reporter module stored in the memory of the computer which, when executed by the processor, is configured to report a result metric related to the XML tag that is converted to the target component markup.
8. The system of claim 7 , wherein the XML to target artifact bundle module is further configured to parse the output XML file into a hierarchical tree structure.
9. The system of claim 8 , wherein the XML to target artifact bundle module is further configured to:
identify the attribute as an identification comprising as a parameter or an event; and
store the identification of the attribute in the output XML file.
10. The system of claim 9 , wherein the XML to target artifact bundle module is further configured to:
convert the output XML file to a big object file; and
convert the big object file to a bundle of files respective to the target component markup, wherein the bundle of files comprises: a .cmp file, a JavaScript controller file, a JavaScript helper file, a scalable vector graphics file, a style file, a documentation file, and an events file.
11. The system of claim 10 , wherein said connector module is further configured to:
(i) scan the artifact bundle; and
(ii) identify at least one dependency between a first artifact and a second artifact of the artifact bundle.
12. The system of claim 7 , wherein the reporter module is further configured to:
report a conversion error related to converting the webpage into XML or converting the XML tag to the target component markup;
mark the conversion error; and
recommend a solution to resolving the conversion error.
13. A method for converting a webpage according to a first framework to a webpage according to a second framework, the method comprising:
retrieving an artifact bundle from a server comprising a first webpage according to the first framework;
converting the first webpage into extensible markup language (XML) as a converted XML webpage, wherein the converted XML webpage is contained in an output XML file and wherein the XML webpage comprises an XML tag;
identifying an attribute of the XML tag;
adjusting a complexity level to be at a higher level upon identifying said attribute of said XML tag to be one or more predefined types;
converting the XML tag to a component markup according to the second framework and based on the complexity level; and
reporting a result metric related to the XML tag that is converted to the component markup of the second framework.
14. The method of claim 13 , the method further comprising:
parsing the output XML file into a hierarchical tree structure.
15. The method of claim 14 , wherein the identifying the attribute of the XML tag further comprises:
identifying the attribute as an identification comprising a parameter or an event; and
storing the identification of the attribute in the output XML file.
16. The method of claim 15 , wherein the converting the XML tag to the component markup further comprises:
converting the output XML file to a big object file; and
converting the big object file to a bundle of files respective to the component markup of the second framework, wherein the bundle of files comprises: a .cmp file, a JavaScript controller file, a JavaScript helper file, a scalable vector graphics file, a style file, a documentation file, and an events file.
17. The method of claim 13 , the method further comprising:
scanning the artifact bundle; and
identifying at least one dependencies between a first artifact and a second artifact of the artifact bundle.
18. The method of claim 13 , wherein the reporting the result metric further comprising:
reporting a conversion error related to converting the first webpage into XML or converting the XML tag to the component markup of the second framework;
marking the conversion error in a report; and
recommending, to a user in the report, a solution to resolving the conversion error.