10 types of Action

[Manjusha Muraleedas]

Hi,

I have been asked in an interview to explain 10 types of actions(Struts).

But I know only 5 typs.

ForwardAction
IncludeAction
DispatchAction
LookupdispatchAction
SwichAction

But the interviewer is not satisfied with my answer. But the interviwer is not at all happy with my answer.
Is there really 10 types actions? Can anyone give any link regarding this

[Bear Bibeault]

It never ceases to amaze me the stupid questions that will result from people untrained in the interview process.

[Vikas Kapoor]

In order to get job you are supposed to clear this kind of interview.

[Manjusha Muraleedas]

So it was the time to show my confidence in Struts....

I am the loser .

Or I could have ask him what he really meant...

[Bear Bibeault]

Vikas Kapoor wrote:In order to get job you are supposed to clear this kind of interview.

It's a crappy interview question. Memorizing stuff like this is in no way a good indication of understanding.

[arulk pillai]

You could say that I generally keep my Struts API handy while coding, and I can't remember the exact names. You can then possibly list the ones you can remember.

As pointed out by Bear, this is not a good interview question.

[Manjusha Muraleedas]

Thank you all...Thank you so much for the information....

[Luke Kolin]

Vikas Kapoor wrote:In order to get job you are supposed to clear this kind of interview.

In order to get a bad job, you are supposed to clear this kind of interview. Bad interviewers clear bad people.

Cheers!

Luke

[Manjusha Muraleedas]

[Tim Holloway]

One of the primary reasons I never sat for the SCJP was because the last time I picked up a study guide, it started off with questions about options on the fine-grained control of the assertion mechanism.

I'm very fond of assertions, myself, having used them since my C days. But 99 times out of 100, if I'm going to employ them, I'm going to use them ALL, not switch them on and off piecemeal. Yes, fine-grained control sounds nice, but if I ever need it, I expect to bloody well well go RTFM and save the brain-space for functions I do everyday. Especially since there's a very good chance that details of any given obscure mechanism will have changed between the time I studied it and the time I needed it, making memorization a liability rather than an asset.

I'm sorry. The things that really make a good developer are not things that can be so easily quantitized. Not everything in the world maps well to binary (our current political climate illustrates that all too well ). This sort of is just ignorance and laziness in the hiring process at best, and a possible warning that actual talent isn't what's wanted at that particular company at worst. They're looking for compliance, not ability. And, sadly, that often means what they really get are the people who are most willing to lie. Which is really all they deserve.

The most rewarding places to work aren't the ones with the artificial requirements, That's a "fence-them-in" mentality. Most of us enjoy the freedom that software design and development allow us, and that's more the antithesis of fencing. So, all things considered, I prefer to just pass by employers who lack the flexibility and the vision to look beyond narrow constraints.

[Vikas Kapoor]

Bear Bibeault wrote:It's a crappy interview question. Memorizing stuff like this is in no way a good indication of understanding.

Luke Kolin wrote:In order to get a bad job, you are supposed to clear this kind of interview. Bad interviewers clear bad people.

I am completely agree with you guys. I might have seen limited industry/people but majority of people I have seen were not good interviewer.