{"id":829,"date":"2006-08-01T01:52:06","date_gmt":"2006-08-01T05:52:06","guid":{"rendered":"http:\/\/cephas.net\/blog\/2006\/08\/01\/webwork-and-meaningful-urls\/"},"modified":"2006-08-08T12:52:19","modified_gmt":"2006-08-08T20:52:19","slug":"webwork-and-meaningful-urls","status":"publish","type":"post","link":"https:\/\/cephas.net\/blog\/2006\/08\/01\/webwork-and-meaningful-urls\/","title":{"rendered":"WebWork and meaningful URLs"},"content":{"rendered":"

Personal pet peeve: meaningful URLs<\/a> (which tonight I found out go by many names: pretty URLs<\/a>, RESTian URLs<\/a>, SES URLs<\/a>, hackable URLs<\/a>, etc…). At work<\/a>, we use WebWork<\/a> extensively but up until this point we haven’t made an effort to create meaningful URL’s. As with any well designed framework, it turns out that there are a couple of ways you can create meaningful URL’s, with different levels of meaningfulness. <\/p>\n

Version 2.2 of WebWork introduced the ActionMapper<\/a> interface and a class called RestfulActionMapper<\/a>, which gives you the ability to create URLs that might look something like this:
\n
\nhttp:\/\/bookstore.com\/books\/category\/java\/keyword\/webwork
\n<\/code>
\ninstead of the more common:
\n
\nhttp:\/\/bookstore.com\/books.jspa?category=java&keyword=webwork
\n<\/code>
\nThe nice thing about the RestfulActionMapper implementation is that you don’t have to write any code to parse the URL: you set up your WebWork actions with the appropriate setters and the RestfulActionMapper handles the rest. The downside is that this still isn’t really a truly hackable URL. For example, although this URL:
\n
\nhttp:\/\/bookstore.com\/books\/category\/java\/keyword
\n<\/code>
\nand this URL:
\n
\nhttp:\/\/bookstore.com\/books\/category
\n<\/code>
\nwould probably work, they don’t really make sense. Why are ‘keyword’ and ‘category’ hanging around at the end? Both of the words are extra information required by the implementation that don’t add any value to the user. <\/p>\n

The second way you can create meaningful URLs is by creating your own ActionMapper. You can get a good start by checking out the source code for the DefaultActionMapper<\/a> and the RestfulActionMapper. To set properties on your action instances, you’ll want to create a HashMap,<\/a>, add the appropriate properties from your URL to the map and then either create and return a new ActionMapping<\/a> using the action name and map or call the setParams() method<\/a> on an existing mapping. The end result is that you should be able to create and use meaningful URL that looks like this:
\n
\nhttp:\/\/bookstore.com\/books\/java\/webwork
\n<\/code>
\nAlso of note:<\/p>\n