Comments on: Hibernate Metadata Explored http://blog.kischuk.com/2004/05/20/hibernate-metadata-explored/ Just another WordPress.com weblog Wed, 19 May 2010 15:39:28 +0000 hourly 1 http://wordpress.com/ By: Daniel Marchant http://blog.kischuk.com/2004/05/20/hibernate-metadata-explored/#comment-184 Daniel Marchant Fri, 10 Dec 2004 14:46:47 +0000 http://rkischuk.wordpress.com/2004/05/20/hibernate-metadata-explored/#comment-184 Good use of the metadata Rob this would make things pretty interesting. I guess my question is why do you even want to use Struts when there are much better frameworks out there. Of course there is the corporate standard sure, but WebWork might provide an easier mapping to the metadata concepts. Good use of the metadata Rob this would make things pretty interesting.

I guess my question is why do you even want to use Struts when there are much better frameworks out there. Of course there is the corporate standard sure, but WebWork might provide an easier mapping to the metadata concepts.

]]> By: Rob Kischuk http://blog.kischuk.com/2004/05/20/hibernate-metadata-explored/#comment-183 Rob Kischuk Thu, 20 May 2004 14:57:31 +0000 http://rkischuk.wordpress.com/2004/05/20/hibernate-metadata-explored/#comment-183 Good call, James. Certainly I wasn't intending to say that struts-config is monolithic and unwieldy. The addition of modules to Struts was an important advance for Struts and comes highly recommended - I am curious what granularity you suggest for this. <p>I meant more to highlight the difference when compared to Hibernate. If Struts were configured like Hibernate, you'd have one config file for the ControllerServlet, and a config file for each action class. (And you'd need to add the Actions to the controller servlet somewhere in code.) I think the struts approach is fine, just not as conducive to direct translation to JSR 175 Metadata. Good call, James. Certainly I wasn’t intending to say that struts-config is monolithic and unwieldy. The addition of modules to Struts was an important advance for Struts and comes highly recommended – I am curious what granularity you suggest for this.

I meant more to highlight the difference when compared to Hibernate. If Struts were configured like Hibernate, you’d have one config file for the ControllerServlet, and a config file for each action class. (And you’d need to add the Actions to the controller servlet somewhere in code.) I think the struts approach is fine, just not as conducive to direct translation to JSR 175 Metadata.

]]> By: James Mitchell http://blog.kischuk.com/2004/05/20/hibernate-metadata-explored/#comment-182 James Mitchell Thu, 20 May 2004 13:26:54 +0000 http://rkischuk.wordpress.com/2004/05/20/hibernate-metadata-explored/#comment-182 "large configuration file shared by..." That's your first mistake. You should be breaking your forms and mappings down into sizable chunks via multi-config. "Struts"...the other white meat!! “large configuration file shared by…”
That’s your first mistake. You should be breaking your forms and mappings down into sizable chunks via multi-config.

“Struts”…the other white meat!!

]]>