 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Java Forum / JavaBeans / April 2004Question on session beans
Hi! It was mentioned that our hiring test had a question which I thought was really ambiguous/strange, however senior development staff here don't seem to think so. I thought I would post this question here to get an opinion. Question: True or False, A valid session is required to use a session bean? What do you think the answer is supposed to be? Kevin > Hi! It was mentioned that our hiring test had a question which I > thought was really ambiguous/strange, however senior development staff [quoted text clipped - 5 lines] > > What do you think the answer is supposed to be? It's a good question I think. It is important to know how EJB's can be used (if you have to use them).  SignatureMarkku > > Hi! It was mentioned that our hiring test had a question which I > > thought was really ambiguous/strange, however senior development staff [quoted text clipped - 8 lines] > It's a good question I think. It is important to know how > EJB's can be used (if you have to use them). But the wording IMO could be better, unless it's a sort of 'trap type' question > But the wording IMO could be better, unless it's a sort of 'trap type' > question This is EXACTLY why companies that use tests like these are hiring the least-qualified people. People that can regurgitate test answers on demand are rarely the kinds of developers that make valuable contributions to a team. A smart hiring process is to ask an applicant to tell about a time they had a problem with a session bean. You'll get a FAR more accurate picture of a candidate's abilities and experience as well as their problem-solving abilities. On the other hand, you guys go right ahead hiring the best test-takers - that way I don't have to weed them out. >>But the wording IMO could be better, unless it's a sort of 'trap type' >>question [quoted text clipped - 5 lines] > A smart hiring process is to ask an applicant to tell about a time they > had a problem with a session bean. You'll get a FAR more accurate If there is 500 people looking for the same job you usually can't interview all of them. That's wh the tests are made for. With test results you then choose let say 10% from applicants to the interview. A good XP practise: do the TESTS first, then the real thing :) SignatureMarkku > A good XP practise: do the TESTS first, then the real thing :) A better practice is to write tests that accurately measure the behavior you're looking for. > Hi! It was mentioned that our hiring test had a question which I > thought was really ambiguous/strange, however senior development staff [quoted text clipped - 5 lines] > > What do you think the answer is supposed to be? The answer is "false". EJBs are not aware of "sessions" in the sense that the term is used in the Servlet API. The term is not used in conjunction with EJBs, notwithstanding the naming of "session beans". The point of the question is to probe the examinee's grasp of EJB and its relationships with other J2EE technologies. The only point of potential confusion is that the question does not itself put the term "session" into an appropriate context, but this is probably intentional, and moreover it is immaterial because there is no reasonable context in which the answer to the question would be different. John Bollinger jobollin@indiana.edu > The answer is "false". EJBs are not aware of "sessions" in the sense > that the term is used in the Servlet API. The term is not used in You are right, they are not HttpSessions but they are sessions nonetheless. If you consider a Stateful session bean then it operates within the context of a session with a particular client. So, in this case the answer is true. This is why I thought it was a ambiguous question that could be interpreted in various ways. >>The answer is "false". EJBs are not aware of "sessions" in the sense >>that the term is used in the Servlet API. The term is not used in > You are right, they are not HttpSessions but they are sessions > nonetheless. If you consider a Stateful session bean then it operates > within the context of a session with a particular client. So, in this > case the answer is true. This is why I thought it was a ambiguous > question that could be interpreted in various ways. Even if you apply the interpretation that using a session bean constitutes establishing and using a session with the EJB container, the client does not "require" an existing session of any kind to establish the EJB session. A session object is certainly not operating within the context of some external session -- at best it represents a session itself. In truth though, some of the ways that multiple session and entity objects can be used together do not fit very well into the mold of what we usually mean by a "session". All this probably has something to do with why the EJB specs do not describe session objects or beans in terms of sessions (ironically enough). Session beans' name doesn't suit them very well. John Bollinger jobollin@indiana.edu Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.