On 6/15/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
why would you want to be convinced? :)
none, its the same thing as the xml config, in fact thats probably what the xml reader calls.
i dont know, i would use hibernate. it is evolving at a higher velocity then the spec and it has features i miss like the criteria api and custom types. the idea of running an application server just to get persistence sickens me. i havent checked out spring's jpa stuff either btw.
-IgorI'm kind of glad we're having this discussion here - it's not really
off-topic since I'm still half-wanting to be convinced that I could
use Spring in this project :D
why would you want to be convinced? :)
So, you're saying I don't *have* to wire classes together w/ XML in
Spring but I could use
GenericApplicationContext.registerBeanDefinition() programmatically
instead? What are the drawbacks (besides the obvious -
externalization.)
none, its the same thing as the xml config, in fact thats probably what the xml reader calls.
I looked into Spring 2.0 yesterday shortly...it looks like they've
done some work to be JPA (EJB 3 persistence) friendly...but I have to
admit I really wasn't crazy about what I was seeing there - just
"template" support for JPA.
i dont know, i would use hibernate. it is evolving at a higher velocity then the spec and it has features i miss like the criteria api and custom types. the idea of running an application server just to get persistence sickens me. i havent checked out spring's jpa stuff either btw.
_______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
