Hi Sir, when I'm training with my present company today, We're asked to develop a simple Online shopping cart. I would suggest you try to develope something like that using JSP, Struts, Spring, and Hibernate(if you are already have a knowledge of this one). Hope this gives you an idea.
dimasalang
Junior Poster in Training
76 posts since Nov 2010
Reputation Points: 11
Solved Threads: 12
Skill Endorsements: 2
Do you have background in spring, hibernate and struts 2? As shopping cart, the users will place their orders and you will compute for their total cost. Code wise, it can be done using Spring for bean injection, JSP pages for your display, Struts 2 for mapping your JSPs to your java controllers, and hibernate for your database queries.
Spring >> Click Here
Hibernate >> Click Here
Struts 2 >> Click Here
And by the way you can also use spring for JSP to controllers mapping if you don't want to study struts 2. ;)
dimasalang
Junior Poster in Training
76 posts since Nov 2010
Reputation Points: 11
Solved Threads: 12
Skill Endorsements: 2
Hi there I'll try to explain this to my very best. :)
Hmmm. When you want to use hibernate in connecting to your DB, you will be needing a data source to connect to the database. You can instatntiate that datasource using Spring, setting the properties like connection string, db username, db password etc. then using it as data source to your hibernate.
By the way datasource is a name given to the connection set up to a database from a server.<Wikipedia> :)
By struts mapping, I mean as a website or something, you would want to do some server side processing whenever a form from your JSP was submitted. Java controller or servlet can do the processing for you. And struts will do the mapping to what controller a page will go once it has been submitted submitted.
Sorry I can't explain it that much. @.@
dimasalang
Junior Poster in Training
76 posts since Nov 2010
Reputation Points: 11
Solved Threads: 12
Skill Endorsements: 2
you should understand that it is pretty hard for us to know what your (future?) employer deems a worthy application.
if you were hired to do back-end development, or as a front-end developer, that changes a lot. are their applications single screen applications, multiple screens, 3D, .... ?
stultuske
Industrious Poster
4,369 posts since Jan 2007
Reputation Points: 1,318
Solved Threads: 610
Skill Endorsements: 23
I agree with stultuske. But I think for now, you should try showing them that you have the skill in doing backend together with front end development. And I suggested the shopping cart with Spring, hibernate and struts forming its framework because I think it's a good way to impress them. ^^
By the way, all I suggested is the common uses of those technologies. By now, I think you should be start developing demo, my suggestion is just to give you an idea, if you can think of anything much better, then that's good! goodluck! :)
dimasalang
Junior Poster in Training
76 posts since Nov 2010
Reputation Points: 11
Solved Threads: 12
Skill Endorsements: 2
dimasalang
Junior Poster in Training
76 posts since Nov 2010
Reputation Points: 11
Solved Threads: 12
Skill Endorsements: 2
That example is just basics. A real day in work, if you're in software development, you would do things much more complex than that.
dimasalang
Junior Poster in Training
76 posts since Nov 2010
Reputation Points: 11
Solved Threads: 12
Skill Endorsements: 2
As a new employee you are unlikely to be asked to do a new project. New hires are usually assigned maintenance tasks, mostly because that teaches them about the existing systems, and partly because they are bottom of the pecking order and nobody likes maintenance.
So a typical task may be to take an existing appication - many thousands of lines of code - and add a new data item to gui and database, or change the logic for processing a particular transaction.
JamesCherrill
... trying to help
8,500 posts since Apr 2008
Reputation Points: 2,583
Solved Threads: 1,454
Skill Endorsements: 29
yes. what's most likely is the set you up at an existing project, starting up with bug fixing to "get to know the application" and some maintenance.
"ow, hey, we want this functionality to change like that now", nothing ground breaking.
starting from small to less small to bigger to (once you really know your way there, and they're convinced you know (and follow) the companies guidelines ... they'll let you start up a project (of course not on your own, but in a team) and later on, maybe even lead one.
stultuske
Industrious Poster
4,369 posts since Jan 2007
Reputation Points: 1,318
Solved Threads: 610
Skill Endorsements: 23
Just try to prove that you're worthy of the job and everything else will fall down into places. ;)
dimasalang
Junior Poster in Training
76 posts since Nov 2010
Reputation Points: 11
Solved Threads: 12
Skill Endorsements: 2