- This topic has 66 replies, 36 voices, and was last updated 18 years, 5 months ago by
.
-
Posts
-
As the developer behind much of the hibernate features in ME, I will definitely vote for Spring as well. My limited experience in the Spring+Hibernate realm has been very much a positive one. Makes a lot of the complexity of coding Hibernate (not necessarily the mapping part, though) go away. Gotta love IoC!
I think its safe to say with this much popularity and the developer that will probably implement it voting for it… it will make it in 😀
Hey, I have surprizingly little pull in the area of priorities. Don’t place too much faith in me! 😉
How does the Spring integration fit in with the priorities? Actually, what are the priorities? Are these listed anywhere?
Andy,
Until we stabalize 3.8 I don’t know that we are even thinking about our next release. But from this poll I would say that Spring support has positioned itself pretty high on the list of TODO items.I voted NO only because I would like to see existing “partial” features completed first. Actually, I think Spring integration makes sense. Not before JSP 2.0 is fully supported.
I voted no, because I am using JDO (the MVCSoft implementation) in combination with Tapestry, so Hibernate does not interest me.
@jetpen wrote:
I voted no, because I am using JDO (the MVCSoft implementation) in combination with Tapestry, so Hibernate does not interest me.
Hibernate support is already there so the forum topic is somewhat of a misnomer. This is more about Spring integration. If you don’t know anything about Spring – it’s a controller framework that implements dependency injection, which allows you to freely switch out the persistance (or view) layer very easily since the container and not code handles dependencies.
Therefore this is for anyone wanting the option/flexibilty to easily switch out Hibernate (JDO, etc…) or Struts (Webwork, Tapestry, Swing, etc…) with whatever they want at any time for any reason. Think of the possibities (one of which MyEclipse can more easily add support for the persistance / view layer of your choice in the future).
I’m sure I probably didn’t do a perfect job of explaining this – but if you want to know more, you should read Martin Fowler’s paper/blog on Dependency Injection for a better explanation.
@awf999 wrote:
See the https://appfuse.dev.java.net/ for lots of Hibernate, Struts, Spring, etc integration.
I too would like to see appfuse as an optional starter project. I have been working on getting a appfuse project started inside MyEclipse and running on Jboss 4.
I am very impressed with the features that continue to be add. Keep up the great work.
I’m a huge fan of Spring. It’s revolutionized my middle-tier development. MyEclipse support would be fantastic.
I’d like a “hibernate/struts” wizard that will create a complete CRUD set. A list form, and add/edit form with delete button, and all the rest of the code to tie everything together.
Lee
A big +1 for Spring in all its glory (but _not_ AppFuse, per se).
Re: “it would be nice when using Hibernate if the config stuff could be located inside a Spring config file instead of a hibernate.properties or hibernate.hbm.xml file”… one still requires separate “hibernate.cfg.xml” file for certain purposes.
Hey ME Team,
Yes, Spring has revolutionized not only my J2EE developmental process, but maintance as well. And as a huge fan of ME, I would LOVE to see Spring automation included.
I’m in the process of having my entire corporation switch over to Eclipse with ME, and it is now basing much of its architecture on Spring. So having Spring automation in ME would be a big selling point for the rest of the developers.Thanks,
James
