I agree... If your never going to modify the data I would use a session
bean to do this. EBs cost a lot.
Jim
--On Thursday, May 17, 2001 5:57 PM -0400 toby cabot <[EMAIL PROTECTED]>
wrote:
>> I have a system where I'll be logging user
>> transactions in one of my tables. I won't ever need to access them
>> again.
>
> Doesn't a session bean fit these requirements? It seems to me that you
> could have a stateless session bean which takes an object and writes the
> member variables to a row in the database. The container will manage
> the pooling etc for you, probably more efficently than if you were using
> entity beans.
>
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
