As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
It may not be the exact category to place this query,
but i could not found better than this. I request to
administrator(s) to handle this.
I am working on Spring framework since last one years.
But did not get involved in concepts, just use it as per project need.
Now i need to explore it as much as i can.
Please let me know which one is good to go with--
1. Spring In Action
2. Pro.Spring.3 by Clarence Ho and Rob Haroop
3. Spring Recipes: A Problem-Solution Approach by Gary Mak
Or there any other book?
Thank You.
I read Spring Recipes, and I recommend it. It's clear, easy to follow, and covered everything I needed.
I actually started from Spring in Action and switched to recipes. It was just better organized, and more extensive.
Maybe you're looking for a better understanding of dependency injection per se. In that case I suggest you to read Manning's Dependency Injection http://www.manning.com/prasanna/. It uses Spring as example as well.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am using Spring MVC and Hibernate for a project. I am little confused about which technology to use in front end part(in jsp part), to get better look and fill as well which is easy to adopt.
Thanks in advance, :)
I would suggest GWT with Spring and Hibernate if that fits your requirements. GWT has great widgets and a vibrant community. There's GWTP, a nice MVP framework for GWT.
For other options, go through Matt Raible's Java frameworks comparison. Spend 2/3 days to pick one that fits your requirements the best.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am new to JSF and was wondering if there is any way to do something like a "type ahead" that could be incorporated into a h:selectOneMenu scenario. I didn't know if this could be achieved using AJAX or something similar.
I saw this IBM article that looks very close to what I want to achieve -->
http://publib.boulder.ibm.com/infocenter/rbdhelp/v7r5m0/index.jsp?topic=/com.ibm.etools.egl.jsfsearch.tutorial.doc/topics/egl_lesson02-01-06.html
I am using Spring + Hibernate + JSF.
I was wondering if anyone had any thoughts on the easiest way to achieve this or any more resources (I am having a hard time finding material).
Take a look at the PrimeFaces Autocomplete component:
http://www.primefaces.org/showcase/ui/autoCompleteBasic.jsf
This has all of the functionality that you are describing out of box and it is fairly easy to integrate into your application. You would of course need to integrate PrimeFaces into your JSF application however there are plenty of online resources to help you with that.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I may have to contribute to a legacy system, classic asp with vbscript web app at work.
What are some good learning tutorials/books on this.
Please don't say you should just use .NET mvc as changing the existing system isn't an option.
I won't forget the good old ASP For Dummies, read it every day for about one month and enjoyed every page of it. Clear, simple and to the point. :)
I would recommend this book, i used to use it as a daily reference when i started learning classic asp, pretty much like yourself i didnt have the option to use dot net
http://www.amazon.co.uk/Beginning-ASP-3-0-Programmer/dp/0764543636/ref=sr_1_11?s=books&ie=UTF8&qid=1297414852&sr=1-11
Also try http://www.w3schools.com/asp/default.asp for some basic samples. If you provide more information on what you will be coding in asp i can probably suggest more sites.
Regards
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I am at the point in my design where I am contemplating dropping the MVC design for performance reasons, not sure if straight out PHP pages with header/footer includes would out perform my MVC setup (using PHP/Zend). I have a feeling it would.
Comments?
What's the value of your time? Of your productivity? Of your code's maintainability?
vs.
What's the cost of an additional server?
It depends on what you're building. MVC can certainly be overkill for some things, and not even applicable to others. Weigh that against future maintenance, working with other developers, how much of the MVC design pattern are you going to be rewriting on your own, etc.
This article discusses MVC, and its inventor's new paradigm DCI that is possible going to be a challenger for traditional OO.
I'm familiar with MVC from its original Smalltalk-80 context. The decision on whether to use MVC or something else is about clarity of the code, not performance. If there are particular problems with the performance of MVC in PHP, I don't know about them.
But again, the primary reason to move toward MVC is that separation of concerns is an important value in ensuring that software is supportable and maintainable over time.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We are migrating an application from Tomcat to WebLogic. There are many things we just don't know about. Is there any decent tutorial out there?
We know about this but I'd like to read about experiencies, and/or processed information.
Thanks in advance.
Ok, I'm late, but I'm going to share the two tutorials I'm following, since I would have found helpful to have those right away.
http://www.scribd.com/doc/6339325/Weblogic-Tutorial
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
WebLogic is a complex, enterprise-level product. I believe Oracle is making a pretty good attempt at explaining it in the intro doc: http://download.oracle.com/docs/cd/E12839%5F01/web.1111/e13752/toc.htm. You can follow the links to get to the detailed documentation of the features that interest you.
If that's not to your liking, Amazon has books like e.g.
http://www.amazon.com/Professional-Oracle-WebLogic-Server-Programmer/dp/0470484306
It depends a lot on your app, but if you can deploy it in tomcat, I'd be surprised if you couldn't deploy it in WebLogic.
Having said that, I certainly hope you have a good reason for using WebLogic (and I hope that reason isn't "The sales guy said it's awesome"). In my admittedly limited experience with WebLogic, I've found it to be a huge pain to use and impossible to troubleshoot if something goes wrong (and it will go wrong).
On the other hand, I have lots of experience with Tomcat, which is dirt-simple to use and easy to troubleshoot (not that you need to troubleshoot, since it pretty much just works).