Good idea, but my DOCTYPE is correct, exactly as is below... I assume it is using 2.0 persistence since it doesn't choke on the relationships or the new entity bean structures...
> From: Peter Levart <[EMAIL PROTECTED]> > Date: Tue, 20 Nov 2001 10:28:54 +0100 > To: Hunter Hillegas <[EMAIL PROTECTED]>, JBoss Dev > <[EMAIL PROTECTED]> > Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? > > This should work and it works for me (using Sybase, but nevertheless). Have > you checked the DOCTYPE of the ejb-jar.xml file? It should read: > > <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans > 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd";> > > If not, then you end up using JAWS instead... > > > On Monday 19 November 2001 20:47, Hunter Hillegas wrote: >> I am deploying a 2.0EJB jar into RH3. >> >> Here's my jbosscmp-jdbc.xml file: >> >> <?xml version="1.0" encoding="UTF-8"?> >> <!DOCTYPE jbosscmp-jdbc> >> >> <jbosscmp-jdbc> >> <defaults> >> <datasource>java:/Groundswell</datasource> >> <type-mapping>PostgreSQL</type-mapping> >> <debug>true</debug> >> <create-table>true</create-table> >> <remove-table>false</remove-table> >> <read-only>false</read-only> >> <time-out>300</time-out> >> <select-for-update>false</select-for-update> >> <preferred-relation-mapping>foreign-key</preferred-relation-mapping> >> </defaults> >> </jbosscmp-jdbc> >> >> No matter what, the jar tries to run against DefaultDS when I want it to >> run against 'Groundswell' as the datasource. >> >> What am I doing wrong? >> >> Hunter >> >> >> _______________________________________________ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
