G
gert
So here i was selling my self to a j2ee consulting company hoping they
would hire me. And while i was lucky to hit the jackpot, meaning
getting a chance to talk to some one that actually knows j2ee, i
starting to discus about why ejb 2.x struts jsf or any non pure xhtml
css javascript (ajax) solution was a bad idea and that i really like
sql more then using a orm layer. You can imagine this was starting to
look more like a battlefield then a job interview
I could defend my self on all grounds except for two things
1) everybody is using struts and hibernate
2) he said making a jndi connecting pool was slow.
Can any one explain to me why jndi/jdbc is slow and whats the
alternative ?
would hire me. And while i was lucky to hit the jackpot, meaning
getting a chance to talk to some one that actually knows j2ee, i
starting to discus about why ejb 2.x struts jsf or any non pure xhtml
css javascript (ajax) solution was a bad idea and that i really like
sql more then using a orm layer. You can imagine this was starting to
look more like a battlefield then a job interview
I could defend my self on all grounds except for two things
1) everybody is using struts and hibernate
2) he said making a jndi connecting pool was slow.
Can any one explain to me why jndi/jdbc is slow and whats the
alternative ?