> Their requirements are EJB, JSP, AJAX, Hibernate. But
> J2EE is much more.
I guess it is the same with everything in Java, you can't know everything, so the question is a little strange. I guess if those are the requirements then you certainly need to know EJB and JSP part of J2EE. Anything else would be a bonus.
> Their requirements are EJB, JSP, AJAX, Hibernate. But
Some of this is J2EE some of it has nothing to do with Java per se.
> J2EE is much more.
Indeed it is.
With just this little bit of information it's difficult to provide any real tangible advice. What I can say definatively is that learning J2EE is definitely a good idea.
My initial reaction to the list of requirements you provided is that they're fishing for buzzwords. My advice then is this, be prepared to learn, but go for it. Don't lie, be forthright about what you do and do not know and about your willingness and eagerness to learn and to grow as a developer.
Worst that can happen is that you don't get the job, but you will have already learned something in the process.
PS.