I went through the same fight with Jetty... I finally figured it out,
then immediately started using the Cayenne native pool instead of the
JNDI one :)
Andrus is right though - once you get past configuration, Jetty rules.
Particularly as an embedded app server w/Cayenne, if that's what
you're using it for... I've had great luck with that.
On 10/5/05, Mike Kienenberger <mkienen..mail.com> wrote:
> Ok. It wasn't quite so bad once I realized I could add Cayenne to my
> web container and manually instantiate a PoolManager. Seems like it's
> working. I'll have to wait and see what other fun this causes.
>
> <Call name="addService">
> <Arg>
> <New class="org.mortbay.jetty.plus.DefaultDataSourceService">
> <Set name="Name">DataSourceService</Set>
> <Call name="addDataSource">
> <Arg>jdbc/myPooledDataSource</Arg>
> <Arg>
> <New class="org.objectstyle.cayenne.conn.PoolManager">
> <Arg>org.hsqldb.jdbcDriver</Arg>
> <Arg>jdbc:hsqldb:hsql://localhost</Arg>
> <Arg type="int">1</Arg>
> <Arg type="int">1</Arg>
> <Arg>myusername</Arg>
> <Arg>mypassword</Arg>
> </New>
> </Arg>
> </Call>
> </New>
> </Arg>
> </Call>
>
>
>
> On 10/5/05, Mike Kienenberger <mkienen..mail.com> wrote:
> > Is anyone using JettyPlus with a Cayenne JNDIDataSourceFactory?
> >
> > I'm looking at the JettyPlus configuration file, and it appears that I
> > somehow have to manually construct a DataSource (possibly a pooled
> > data source) using "xml-syntax" java.
> >
> > Seems like there is either an easier way, or that maybe someone else
> > might have already done such a terrible thing....
> >
> > Thanks,
> >
> > -Mike
> >
>
This archive was generated by hypermail 2.0.0 : Wed Oct 05 2005 - 16:28:06 EDT