request parameters (which are strings), parse them to Java types and store them into some kind of variable. And this is just half of the work we have to do as we must implement the inverse path (load data metadata JavaServer Pages Specification1 defines 4 scopes in which a page can create and access a variable. These scopes are: • request: variables declared in this scope can be seen only by pages processing issue let’s consider the following code (from the project StatelessPage) where the value of the variable index is used inside onclick(): 69 public class StatelessPage extends WebPage { private int

request parameters (which are strings), parse them to Java types and store them into some kind of variable. And this is just half of the work we have to do as we must implement the inverse path (load data metadata JavaServer Pages Specification1 defines 4 scopes in which a page can create and access a variable. These scopes are: • request: variables declared in this scope can be seen only by pages processing issue let’s consider the following code (from the project StatelessPage) where the value of the variable index is used inside onclick(): public class StatelessPage extends WebPage { private int index

request parameters (which are strings), parse them to Java types and store them into some kind of variable. And this is just half of the work we have to do as we must implement the inverse path (load data metadata JavaServer Pages Specification1 defines 4 scopes in which a page can create and access a variable. These scopes are: • request: variables declared in this scope can be seen only by pages processing issue let’s consider the following code (from the project StatelessPage) where the value of the variable index is used inside onclick(): public class StatelessPage extends WebPage { private int index

request parameters (which are strings), parse them to Java types and store them into some kind of variable. And this is just half of the work we have to do as we must implement the inverse path (load data metadata JavaServer Pages Specification1 defines 4 scopes in which a page can create and access a variable. These scopes are: 59 • request: variables declared in this scope can be seen only by pages processing issue let’s consider the following code (from the project StatelessPage) where the value of the variable index is used inside onclick(): 69 public class StatelessPage extends WebPage { private int