| |
| |
| |
|
Page: 1 2
Comments:
<0> session are stateless ?
<0> or at least not persistent
<0> something like that
<0> oh sorry that means jdbc through entity bean
<1> dougless: I generally ONLY use jdbc in stateless sessions
<0> but it is ages since i looked at ejb
<1> and no entities
<1> I just prefer having direct control over my database layer
<2> yeah, entites are evil
<0> i though the idea is to use entity beans for persistence originally ?
<0> or am i mistaken ?
<1> yea, that was the idea
<1> unfortunately, ejb2.0 entities pretty much blow
<0> well
<3> well I can do simple database inserts etc via stateless beans using jdbc, but the same thing can be done via cmp's when to use what?
<0> but if you shortcut the entity beans why using ejb at all ?
<1> dougless: use your best judgement... I have just foregone cmp entirely
<0> after all imho for many thing a pure ejb free solution is quite appropiate
<0> oops
<0> scratch that
<0> new try
<3> well the way I see it use the cmp's for entity based infor like users in a ecommerce systems, or oreders etc. in this respect u can also use the cmp to create new users, though you could use the statelss beans to do the same
<0> after all imho for many things a ejb free solution is quite appropiate
<0> this way
<1> dougless: I use stateless beans for all of it
<3> tmbg: so u avoid cmp's alltogether?
<0> tmbg : but why do you use beans at all ?
<1> dougless: yessir
<1> kmh: there's a lot more to ejb than persistence
<0> what's the advantage of stateless bean to the regukar bean or some java cl*** ?
<1> remotability, abstraction, clustering, pooling
<0> tmbg : yes but to stateless objects ?
<1> etc etc
<0> i mean the container is managing and pooling resources, but ...
<0> well i agree
<1> resource management is another big one
<0> but only if you really have a need for clustering and distributed architecure
<1> component reusability
<3> tmbg: but by not using cmp's or bmp's you are forgoing a lot of efficincy in the application server, like the entity residing in memory etc and working directly on this entity. using via stateless you are constantly streaming all the info back to the client
<1> dougless: that's very possible
<0> otherwise it is just slowing down things
<3> so in other words the "better
<3> " solution is to use cmp, but easier with stateless
<1> I don't know if that's accurate
<1> cmp is theoretically better
<1> but I think in practice, it's not
<1> most people I've talked to consider hibernate or toplink or something similar to be far better than cmp
<1> I just haven't worked with them yet
<0> cmp = ?
<3> true, in practice its lto more complex to put together but it does take advantage of all the the nice things that application servers supply
<1> container managed persistence
<0> oh
<3> yes hibernate is the populare one which I have to get into now
<1> I'm going to spend some time with it eventually
<3> ok, i guess that is all from me.
<1> heheh
<3> just wanted to fix my head around the jdbc through stateless and cmps
<1> yea
<3> by the way i have been messing with j2ee for a while and i just bought a book that i heavily recomend
<1> oh?
<3> got all the info u need as well as nice extras such as design patterns etc
<3> its called java j2ee 1.4 bible by wiley
<3> damn good and thick as hell
<3> so makes a nice paperweight after
<3> lol
<3> ok, back at it, see u guys laters
<1> heheh
<4> hey can anyone recommend some good free java chat clients for a website?
<4> something user friendly
<5> gooooooogle, two|face
<4> but there is spaaaaam everywhere :)
<4> and its "free" but then its not really free
<5> phpFreeChat looks pretty good, not java though
<6> hi everybody
<6> I'm looking for a java powered blog engine
<6> any ideas ?
<5> yes. Look in php instead.
<5> or google
<6> nope, I would like to forget php engines
<6> I'm googling, but i expected you will know something different
<6> cause I'm bothered of php code source, I would like to have a real plugin and xml architecture
<6> I have found blojsom
<7> salam
<6> salam alikoum
<7> :)
<6> http://wiki.blojsom.com/wiki/display/blojsom/Features
<6> nice :)
<8> hey, I am writing an app that inserts entries into a db via jdbc, but some of the entries already exist (the first column is a unique identifier), so INSERT sometimes throws an SQLException.. is it bad coding style to do an update record inside of the SQLException catch clause if the exception is thrown because the record already exists?
Return to
#java
or
Go to some related
logs:
Flashers on the net
#linux
kinky virtous
#linux
openssl R_X86_64_32
earth_gal
joomla how to develop modules
#linuxhelp
#linuxhelp
konsole for windows
|
|