On 2/20/06, Cris Daniluk <cris.danilu..mail.com> wrote:
>
> > I'd say I probably covered the tomcat configuration part. However,
> cayenne
> > modeler's stairing me in the face and wants to know the new data node
> JNDI
> > Location. I'm quite certain a part of what I should write here is
> jdbc/zs2,
> > but I'm equaly certain that I should somehow let cayenne know which
> tomcat
> > instance I'm referening to (= tomcat IP:port).
> >
> Cayenne runs inside the Tomcat, so it already knows IP/port :)
>
> "jdbc/zs2" should be the only name you need...
>
> By the way, you may want to use a Context based resource and not a
> global one, if you ever indend to deploy two versions of your app to
> the server (for testing, etc), or just to avoid confusion in general.
Wow wow wow, this can't be right: we must be talking about different
problems.
I'm talking about a client/server application based on a rich client (i.e.
swing), using tomcat on the server as a JNDI DataSource server. What you're
telling me would make sense for a web app (where cayenne indeed would run on
the same server), but that's not the issue.
So, how do the rich clients (using cayenne under the hood, running on client
machines, obviously) know where to look for a JNDI DataSource?
t.n.a.
This archive was generated by hypermail 2.0.0 : Mon Feb 20 2006 - 08:53:43 EST