Thank for the speedy response! I have looked at HTTP tunnel JDBC driver yet there appear only 1 generic one (IDS) , i can't find one for mySQL (which we are forced to use) - and that 1 generic drivers is a staggering $900 which is my entire budget (including my wages)...
We will probably end up doing a mini-orm version client side (i have experience which such a thing in PHP ;) or create dynamic users in MySQL - as the traffic is quasi nihil - only 2 / 3 people will use it and they only have to validate themselves 1 ... Perhaps a nice JakartaProject such an HTTP-Tunnel for its JDBC compliant drivers wouldn't you think? Anyway just gonna convince my friends to allow access of MySQL directly (but IP/limited) hence we can wrap this baby up.. still thank heaps for the poinaint info Many greetz Onno ----- Original Message ----- From: "Thomas Mahler" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Monday, March 31, 2003 7:12 PM Subject: Re: getting query output > Hi Onno, > > onno wrote: > > Hiyall! > > > > For a project we use OJB on the server side of things - however for the > > application we have > > constructed a seperate java webstart application. Due to security reasons we > > cannot open any ports > > for the public and hence the admin-application. For most things on the admin > > side we route > > all sql queries to a secure servlet. However we didn't realize that we > > couldn't simply > > port the OJB coz it uses the JDBC drivers which need direct access. So i > > wondered at what part > > in the OJB the actual queries get created and are requested. > > have a look at the packages org.apache.ojb.broker.accesslayer.sql (Sql > generation) > and org.apache.ojb.broker.accesslayer for JDBC connectivity. > There are only few classes that directly use JDBC resources, and they > are all in that package. > > Hence I could > > write > > a 'slot' which would reroute the traffic - > > OJB is currently not prepared to do this. Making the usage of JDBC > resources pluggable would be a *major* task. It will also touch > performance critical parts. > I can't recommend that approach. > > > without going through the lenghts > > of creating a full fledged JDBC driver. > > IMO it's much easier (and cleaner) to write a HTTP tunneling JDBC driver > than trying to cut the OJB Accesslayer into pieces. It's not meant for > such an excercise. > > I'm sure someone has developed a JDBC over HTTP tunnel already. AFAIK > the Hypersonic database even ships with such a beast. > > > > > Or in worst case i would need to write the JDBC driver but exactly how would > > i find out what features > > are being used by the OJB as to implements only the needed features... > > > > Hope anybody has some ideas... > > Try > http://www.google.de/search?hl=de&ie=UTF-8&oe=UTF-8&q=%22JDBC+over+SOAP%22&m eta= > > cheers, > Thomas > > > Onno > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
