Session Bean vs. POJO

[hbpost]

Please forgive the newbile nature of this question, but is there any advantage to implementing a web service as an EJB over a POJO.

If one were starting fresh and had no requirement to access the service as a remote bean, would any functionality be lost, or behavior be different, between a POJO and EJB?

Thanks,

Herman Post

[peterj]

There is only one difference that I can think of.

The app server maintains a pool of EJBs. The EJBs are reused for every web service request. Thus is your web service has to do some initialization, it will do it only once and can then service multiple requests. Of course, if the EJBs are not used they can time out and be removed from the pool.

For POJO web services, a new instance is created for each call. Thus if you need to do initialization, it happens for every request.

See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=105344

[hbpost]

thanks much