|Home > Guides > Core Developers Guide > Configuration Elements > Namespace Configuration|
The namespace attribute subdivides action configurations into logical modules, each with its own identifying prefix. Namespaces avoid conflicts between action names. Each namespace can have its own "menu" or "help" action, each with its own implementation. While the prefix appears in the browser URI, the tags are "namespace aware", so the namespace prefix does not need to be embedded in forms and links.
The default namespace is
"" - an empty string. The default namespace is used as a "catch-all" namespace. If an action configuration is not found in a specified namespace, the default namespace is also be searched. The local/global strategy allows an application to have global action configurations outside of the action element "extends" hierarchy.
The namespace prefix can be registered with Java declarative security, to ensure only authorized users can access the actions in a given namespace.
A root namespace ("/") is also supported. The root is the namespace when a request directly under the context path is received. As with other namespaces, it will fall back to the default ("") namespace if a local action is not found.
If a request for
/barspace/bar.action is made, the
/barspace namespace is searched for the
bar action. If found, the
bar action is executed, else it will fall back to the default namespace. In the Namespace Example, the
bar action does exist in the
/barspace namespace, so the
bar action will be executed, and if "success" is returned, the request will be forwarded to
In the Namespace Example, if a request for
moo.action is made, the root namespace ('/') is searched for a
moo action; if a root action is not found, the default namespace is checked. In this case, the
moo action does exist and will be executed. Upon success, the request would be forwarded to