Hi,
I am new to Hibernate and trying to convert my existing web application's data layer to using it.
One of the problems I've run into is the following:
I have a Portal class, that has an Id, Name, URL, etc as properties. It's mapped to a portal table.
In the database I have another table that mai
Here is a link to Virtual JDBC that uses a command pettern with a very light
interface that can be implemented over any transport layer:
http://vjdbc.sourceforge.net/
Here is a comment from this project:
"The main difference between VJDBC and RmiJdbc is that RmiJdbc exposes the
complete interfac
Here is an interesting approach to solving an issue with exposing DB
connections via a Type 3 Driver to an un-trusted client: DUALITY JDBC
Proxy - Server controlled JDBC connections and executions. The Server
actually opens connection to the client - no need to open firewall:
http://www.linus.no/j
Philipp Meier wrote, On 6/14/2004 6:46 AM:
>
> There is c-jdbd which acts as a kind of jdbc-"raid" for databases
> (Implementing db-clustering at jdbc level), which might be a goot
starting
> point for this.
Yes, c-jdbc http://c-jdbc.objectweb.org/ was my first thought as well.
-Dave
Yes, looks something like what I was thinking of. I wanted a pluggable
transport layer though
Rob Butler wrote:
I've never used it, but this sounds similar to what you are proposing:
http://rmijdbc.objectweb.org/
Later
Rob
--
Gavin King
+61 41 053 4454
+1 404 822 8349
Hibernate
[EMAIL PROT
I've never used it, but this sounds similar to what you are proposing:
http://rmijdbc.objectweb.org/
Later
Rob
>
> I've been thinking about the problem of users who ask for
> "lazy fetching from the client". As we keep explaining,
> this is an incredibly bad idea, since transaction
> demarcation
Yes, I think you're right. Apparently, depending on the requirements of
the project, the client may as well either run Hibernate and speak
directly with the database, or (if you're concerned about security and
have the time) that both JDBC and Hibernate must be on the server. Clients
should gen
I just did a swing client that uses hibernate, and although in my case I
was alright to make the database available to the client hosts, I'm sure
many can't. So it sounds like this will certainly be useful, but it has me
thinking: will this layer be added only because nobody trusts the
database
OK, so the problem is that this JDBC proxy still allows arbitrary SQL to
be executed on the server. Never worked with rich client applications
before, I had not realized that this (security) was the main reason for
choosing to add a third tier. I thought the problem was minimizing database
connecti
Gavin King schrieb:
After thinking about this, I think I've decided that there is
nothing at all wrong with doing data access via a remote
"gateway", so that Hibernate would run in the client tier and
act as a remote client of a server-side JDBC connection pool.
This would enable transaction demarc
I've been thinking about the problem of users who ask for
"lazy fetching from the client". As we keep explaining,
this is an incredibly bad idea, since transaction
demarcation and caching (and probably also dirty checking)
should take place in the same tier as lazy fetching.
However, many of these
11 matches
Mail list logo
