Best Java/Struts Interview Ever?
Uploader Comments (davelnewton)
Top Comments
-
the sql question #1 was fucking awesome, i actually tried it and it fucking blew up, for those who wants to try too sentence is: SELECT, INSERT, ACTUALLY DELETE INSERT SELECT BY NAMESELECT (SOMESHIT ABOUT PARAMETERS) SELECT INSERT UPDATE (BY NAME!!!?) and shit goes on LOL
All Comments (13)
-
hahahahahahah he must be from railways department he always trying to point engines
-
Now why didn't he just say he didn't know?
-
@davelnewton sessions?
-
@davelnewton For when the user navigates through multiple pages, I'll just pass the step property through url parameter and have the Action class do request.getParameter("step") and set the value to the form
-
@davelnewton My answer to your follow up question, Now that I think about it, I would use struts-tiles and have multiple success forwards in one Action class. The one action class is the one that outputs the wizard's multiple screen depending on the ActionForm's step property which of course will be a html:hidden propert. So in the Action class there will be multiple "return mapping.findForward" which it knows which one to return depending on the form's step value.
I appreciate the interviewers patience though
AZBAJWA421 2 months ago
@AZBAJWA421 Yep, it was pretty remarkable--don't know how they did it.
davelnewton 2 months ago
What is the correct answer to that windows wizard question?
I'm thinking have one ActionForm class that has maybe has a int property called "step" and then have individual Action classes per page that use the same ActionForm class to populate the 5 things per page and the last Action class the displays everything does a request.setAttribute(mapping.findblahlbah(forgot), formName); and in the jsp use el tag to display it like ${formName.fullname} or something like that?
WestFlipian 9 months ago
@WestFlipian No right answer, just looking for how interviewee responds. And reacts to followup questions regarding implementation. Any answer that boils down to some form of state machine with state persisted somehow is basically correct. There are wrong answers, though.
I'd follow up with: 1) how are you representing the wizard's flow in configuration and/or code, and 2) how might you implement this in a general way, like if you had a lot of multiple-screen interactions.
davelnewton 9 months ago
The picture is from istockphoto, if anybody cares. Not really the dude. Probably.
davelnewton 1 year ago