Dear List,

Does anyone have any timeline information regarding use of suns JDO in a
project, as Craig Russel himself said that suns license issues might change
in this area.! As far as I understand if you include some JDO Interface
classes from SUN in a commercial project, you are breaking the law...? am I
still right ? we are looking for a db persistance technology but from what I
gather ojb is still not stand-alone... I am thinking of using Torque, but
would prefer to use JDO.

regards
BEN


----- Original Message -----
From: "Andreas Wuest" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 29, 2003 2:11 PM
Subject: ojb + struts webapp question


> Hi,
>
> i am new to ojb and i'd like to use it in a struts web application.
however
> i have some question for best practice :
>
> 1. to access the web app the users have to login. after login in i need
>    serveral db accesses on different pages. is it best to store a
>    PersistenceBroker instance in the session (so each logged in user has
>    a broker of its own) or should a i put a PersistenceBroker instance
>    into the application context (all users use the same persistence
broker) ?
>    One broker per User is probably the best solution (concerning
>    transactions), isn't it ?
>
> 2. is there a way to show the sql statement that the persistence broker
>    is running against to database so i can compare the statement with
>    the sql that i intended to run (just to check if the created sql
>    is correct).
>
> thanks in advance,
>
>  Andreas
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to