> point is, its nice to have the option. and there are plenty cases where > criteria api is much more readable then hql, not to mention it is much > easier to build search queries, etc instead of using a whole lot of nasty > string concatenations. " where 1=1 " look familliar? :)
Sure does! :) And agreed, I wish they would have included the Criteria API. > because jetty+spring starts up in like 20 seconds (thats with spring > creating all the beans on startup for me), jboss takes more then a minute > just for itself. thats a lot of waiting for me every time hotswap cant cope. > and last time i checked configuring jboss not to start some of the things i > dont need is a nightmare, i tried in the past a few times and a few hours > into it gave up. plus i dont need to deal with any of the stupid descriptor > files, etc. web.xml and spring.xml is all i need and they are all simple. > and no weird classloader issues, etc. its just a simpler development > environment that saves you lots of time, and if you want to deploy on jboss > for prod there is nothing stopping you. Honestly, I haven't had these problems so I can't relate. JBoss 4.0.4.GA starts in about 20-30 seconds and deploying the apps I've built takes 3-5 sec. roughly. The only descriptor file I've had to use so far is a one-liner that maps the URL of the web app to the EAR app. You're right, however, you would always deploy-up to JBoss if needed but probably not deploy-down from JBoss to a servlet/JSP container simply because those services wouldn't be available. > was that a pro or a con? :) Obviously that depends on who you ask :D You could probably imagine my opinion on this. _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
