Comments on: Common Reference Data in Spring MVC http://developingdeveloper.wordpress.com/2008/02/28/common-reference-data-in-spring-mvc/ java - spring - ddd - ria - remoting Thu, 11 Jun 2009 01:04:38 +0000 http://wordpress.com/ hourly 1 By: Soongy webOS http://developingdeveloper.wordpress.com/2008/02/28/common-reference-data-in-spring-mvc/#comment-57 Soongy webOS Mon, 04 May 2009 07:44:07 +0000 http://developingdeveloper.wordpress.com/?p=8#comment-57 thanks :) thanks :)

]]> By: Jonas http://developingdeveloper.wordpress.com/2008/02/28/common-reference-data-in-spring-mvc/#comment-33 Jonas Thu, 24 Apr 2008 13:28:46 +0000 http://developingdeveloper.wordpress.com/?p=8#comment-33 Post data can also be read, just launch up firebug and you will see :). Exposing the model in the url should not be considered a security risk, instead you should design the security layers with this in mind. Jonas Post data can also be read, just launch up firebug and you will see :) .
Exposing the model in the url should not be considered a security risk, instead you should design the security layers with this in mind.

Jonas

]]> By: Josh Kalderimis http://developingdeveloper.wordpress.com/2008/02/28/common-reference-data-in-spring-mvc/#comment-23 Josh Kalderimis Thu, 13 Mar 2008 20:11:52 +0000 http://developingdeveloper.wordpress.com/?p=8#comment-23 Hi Carl, You are absolutely right, there is no doubt that using an interceptor can be over kill, but in some cases it can be the best solution. Maybe the reference data being added to every page is from the database or maybe you have different properties files for different deployments and would like the information in the properties files be added to every page. In any case, an interceptor is not a perfect solution. On another note, I am a big fan of sitemesh and agree that templating can be a great substitute. Thank you also for the link to SemaCodeFix, sadly I can't use it as I'm using wordpress.com as my blog host, but I will remember it if in case I move my post in the future. Josh Hi Carl,

You are absolutely right, there is no doubt that using an interceptor can be over kill, but in some cases it can be the best solution. Maybe the reference data being added to every page is from the database or maybe you have different properties files for different deployments and would like the information in the properties files be added to every page. In any case, an interceptor is not a perfect solution.

On another note, I am a big fan of sitemesh and agree that templating can be a great substitute.

Thank you also for the link to SemaCodeFix, sadly I can’t use it as I’m using wordpress.com as my blog host, but I will remember it if in case I move my post in the future.

Josh

]]> By: Carl Sziebert http://developingdeveloper.wordpress.com/2008/02/28/common-reference-data-in-spring-mvc/#comment-21 Carl Sziebert Thu, 13 Mar 2008 17:16:04 +0000 http://developingdeveloper.wordpress.com/?p=8#comment-21 Josh: Great post, I'm using a similar technique, but I thought that I would mention that the same sort of thing can also be achieved with most of the html templating options available to Spring MVC. On another note, you should consider using the SemaCodeFix plugin to format your code blocks. I've used it with great success on my site. Here is the link: http://www.sematopia.com/?p=138 Carl Josh:

Great post, I’m using a similar technique, but I thought that I would mention that the same sort of thing can also be achieved with most of the html templating options available to Spring MVC. On another note, you should consider using the SemaCodeFix plugin to format your code blocks. I’ve used it with great success on my site. Here is the link: http://www.sematopia.com/?p=138

Carl

]]>