less reusable). Let’s consider for example the main page of a mail service where users can see a list of received mails. Suppose that this page shows a notification box where user can see if new messages email to let users confirm important actions like password changing or the subscription to a mailing list. This kind of page usually expects to receive a query string parameter containing the id of the action page instances and to retrieve static URL segments used to build and parse page URLs. Here is the list of these segments: • Namespace: it’s the first URL segment of non-mounted pages. By default its value

less reusable). Let’s consider for example the main page of a mail service where users can see a list of received mails. Suppose that this page shows a notification box where user can see if new messages email to let users confirm important actions like password changing or the subscription to a mailing list. This kind of page usually expects to receive a query string parameter containing the id of the action page instances and to retrieve static URL segments used to build and parse page URLs. Here is the list of these segments: • Namespace: it’s the first URL segment of non-mounted pages. By default its value

less reusable). Let’s consider for example the main page of a mail service where users can see a list of received mails. Suppose that this page shows a notification box where user can see if new messages email to let users confirm important actions like password changing or the subscription to a mailing list. This kind of page usually expects to receive a query string parameter containing the id of the action page instances and to retrieve static URL segments used to build and parse page URLs. Here is the list of these segments: • Namespace: it’s the first URL segment of non-mounted pages. By default its value

less reusable). Let’s consider for example the main page of a mail service where users can see a list of received mails. Suppose that this page shows a notification box where user can see if new messages email to let users confirm important actions like password changing or the subscription to a mailing list. This kind of page usually expects to receive a query string parameter containing the id of the action page instances and to retrieve static URL segments used to build and parse page URLs. Here is the list of these segments: • Namespace: it’s the first URL segment of non-mounted pages. By default its value

js"); UrlResourceReference jqueryuiRef = new UrlResourceReference(jqueyuiUrl){ @Override public List getDependencies() { Application application = Application.get(); ResourceReference "class", "myClass"); assertEquals("span", tagTester.getName()); List tagTesterList = TagTester.createTagsByAttribute(responseTxt, "class", "myClass",