> As for whether EJBs is going to be required in the near future for you > to get a job, who's to say?
Sadly, companies are very biased towards people who don't have specific product experience in many cases. Don't take this the wrong way but EJB's are not all that difficult. I have read a book on them and tried some things with the reference implementation. No big deal. So you have a home and a remote interface. So you have session beans (our struts Java beans are basically the same thing), entity beans (We wrote a bunch of db-bind classes to be used within our struts application to perform this) and message beans (I used JMS in cases to simulate message beans). Ok... So why do so many companies discredit individuals who lack a specific product experience even if they have decent OO skills? :-) A friend of ours who has done EJB for a year says EJB's are very easy. What's difficult is understanding how they all work together. But that's OO and not EJB. I guess since this is an Employer's market (at least in the Phoenix and Denver area), they can put tight strict requirements around. Heck, we'd love it if our employer would buy an App Server but they won't so we're using Struts since it's free. But we've found out that it's very powerful and very easy to work with. thanks for your insight... Theron -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
