Multi-lingual tag extension mechanism
First Claim
1. A method of processing a custom action tag in a Web Page to provide a tag library extension that can be used to implement a tag library supporting multiple scripting languages, said custom action tag providing textual instructions for performing actions in said Web Page, said custom action tag being capable of customization to perform customized actions and including a start-tag and an end-tag, said custom action tag being further capable of having a body between said start-tag and said end-tag, said method comprising;
- providing, for said custom action tag, a tag-handler object that represents a run-time representation of said custom action tag, said tag-handler object including;
a do-start method for processing said start-tag of said custom action tag,a do-body method for processing said body of said custom action tag, anda do-end method for processing of said end-tag of said custom action tag;
invoking said do-start method of said tag-handler object to process said start-tag of said custom action tag, wherein said do-start method determines;
whether the custom action tag has a body, andwhether there is a need to process said body when said do-start method determines that said custom action tag has a body;
invoking said do-body method of said tag-handler object when said invoking of said do-start method determines that there is a need to process said body of said custom action tag;
processing, by said do-body method of said tag-handler object, said body of said custom action tag, to translate said body from a first scripting language to platform independent code that can be executed to perform actions intended by said custom action tag;
determining by said do-body method of said tag-handler object whether further processing is required to translate the body from a first scripting language to platform independent code that can be executed to perform the actions intended by said custom action tag when said processing has been performed by said do-body method of said tag-handler object,repeating said processing, by said do-body method of said tag-handler object, when said do-body method of said tag-handler object determines that further processing is required; and
invoking said do-end method of said tag-handler object when said do-body method determines that no further processing is required, wherein said do-end method processes said end-tag of said custom action tag.
3 Assignments
0 Petitions
Accused Products
Abstract
A multi-lingual tag extension mechanism suitable for use with the JAVASERVER computer software Pages platform. Rather than creating a closure abstraction, the present invention “in-lines” a body evaluation for the tags. A doStart ( ) method processes a start tag and determines if a body needs to be evaluated. If so, a body evaluation buffer is passed to a doBody ( ) method for body evaluation. Once the body evaluation is complete, a doEnd ( ) method completes the processing by synchronizing the variables. The scripting details of the present invention match any nesting of the tag, so the at the structure corresponding to the original scripting is preserved. Furthermore, the present invention is not dependent on the specifics of the scripting language used to form the Web page.
25 Citations
16 Claims
-
1. A method of processing a custom action tag in a Web Page to provide a tag library extension that can be used to implement a tag library supporting multiple scripting languages, said custom action tag providing textual instructions for performing actions in said Web Page, said custom action tag being capable of customization to perform customized actions and including a start-tag and an end-tag, said custom action tag being further capable of having a body between said start-tag and said end-tag, said method comprising;
-
providing, for said custom action tag, a tag-handler object that represents a run-time representation of said custom action tag, said tag-handler object including; a do-start method for processing said start-tag of said custom action tag, a do-body method for processing said body of said custom action tag, and a do-end method for processing of said end-tag of said custom action tag; invoking said do-start method of said tag-handler object to process said start-tag of said custom action tag, wherein said do-start method determines; whether the custom action tag has a body, and whether there is a need to process said body when said do-start method determines that said custom action tag has a body; invoking said do-body method of said tag-handler object when said invoking of said do-start method determines that there is a need to process said body of said custom action tag; processing, by said do-body method of said tag-handler object, said body of said custom action tag, to translate said body from a first scripting language to platform independent code that can be executed to perform actions intended by said custom action tag; determining by said do-body method of said tag-handler object whether further processing is required to translate the body from a first scripting language to platform independent code that can be executed to perform the actions intended by said custom action tag when said processing has been performed by said do-body method of said tag-handler object, repeating said processing, by said do-body method of said tag-handler object, when said do-body method of said tag-handler object determines that further processing is required; and invoking said do-end method of said tag-handler object when said do-body method determines that no further processing is required, wherein said do-end method processes said end-tag of said custom action tag. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer readable storage medium including computer program code for processing a custom action tag in a Web Page to provide a tag library extension that can be used to implement a tag library supporting multiple scripting languages, said custom action tag providing textual instructions for performing actions in said Web Page, said custom action tag being capable of customization to perform customized actions and including a start-tag and an end-tag, said custom action tag being further capable of having a body between said start-tag and said end-tag, said readable media comprising;
-
computer program code for providing, for said custom action tag, a tag-handler object that represents a run-time representation of said custom action tag, said tag-handler object including; a do-start method for processing said start-tag of said custom action tag, a do-body method for processing said body of said custom action tag, and a do-end method for processing of said end-tag of said custom action tag; computer program code for invoking said do-start method of said tag-handler object to process said start-tag of said custom action tag, wherein said do-start method determines; whether the custom action tag has a body, and whether there is a need to process said body when said do-start method determines that said custom action tag has a body; computer program code for invoking said do-body method of said tag-handler object when said invoking of said do-start method determines that there is a need to process said body of said custom action tag; computer program code for processing, by said do-body method of said tag-handler object, said body of said custom action tag, to translate said body from a first scripting language to platform independent code that can be executed to perform actions intended by said custom action tag; computer program code for determining by said do-body method of said tag-handler object whether her processing is required to translate the body from a first scripting language to platform independent code that can be executed to perform the actions intended by said custom action tag when said processing has been performed by said do-body method of said tag-handler object, computer program code for repeating said processing, by said do-body method of said tag-handler object, when said do-body method of said tag-handler object determines that further processing is required; and computer program code for invoking said do-end method of said tag-handler object when said do-body method determines that no further processing is required, wherein said do-end method processes said end-tag of said custom action tag. - View Dependent Claims (11, 12, 13, 14)
-
-
15. A computer system for processing a custom action tag in a Web Page to provide a tag library extension that can be used to implement a tag library supporting multiple scripting languages, said custom action tag providing textual instructions for performing actions in said Web Page, said custom action tag being capable of customization to perform customized actions and including a start-tag and an end-tag, said custom action tag being further capable of having a body between said start-tag and said end-tag, said computer system comprising;
-
at least one central processing unit; memory; and a computer program operating on said at least one central processing unit, wherein said computer program is capable of; providing, for said custom action tag, a tag-handler object that represents a run-time representation of said custom action tag, said tag-handler object including; a do-start method for processing said start-tag of said custom action tag, a do-body method for processing said body of said custom action tag, and a do-end method for processing of said end-tag of said custom action tag; invoking said do-start method of said tag-handler object to process said start-tag of said custom action tag, wherein said do-start method determines; whether the custom action tag has a body; and whether there is a need to process said body when said do-start method determines that said custom action tag has a body; invoking said do-body method of said tag-handler object when said invoking of said do-start method determines that there is a need to process said body of said custom action tag; processing, by said do-body method of said tag-handler object, said body of said custom action tag, to translate said body from a first scripting language to platform independent code that can be executed to perform actions intended by said custom action tag; determining by said do-body method of said tag-handler object whether further processing is required to translate the body from a first scripting language to platform independent code that can be executed to perform the actions intended by said custom action tag when said processing has been performed by said do-body method of said tag-handler object; repeating said processing, by said do-body method of said tag-handler object, when said do-body method of said tag-handler object determines that further processing is required; and invoking said do-end method of said tag-handler object when said do-body method determines that no further processing is required, wherein said do-end method processes said end-tag of said custom action tag. - View Dependent Claims (16)
-
Specification