RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? (Postgres and CMP 2)
Title: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? (Postgres and CMP 2) that is not true marcf -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bunker, DanSent: Tuesday, November 20, 2001 9:59 AMTo: JBoss DevSubject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? (Postgres and CMP 2) I have been developing with CMP 2 and postgresql for the last 2 weeks. Things seem to be going OK for what I'm using it for. I have seen some interesting things with the transaction types. It appears that rabit hole currently only supports "Required" and "RequiresNew" transactions. All others throw null pointer exceptions. Dan -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 5:06 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime in? Is no one else running Rabbit Hole with PostgreSQL and 2.0 EJB? From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 16:14:21 -0600 To: "'Hunter Hillegas'" [EMAIL PROTECTED], Dain Sundstrom [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used.Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: "'Hunter Hillegas'" [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS?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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Hunter, I've seen the same thing with mySQL today (it did work with the CVS sources from about 3 weeks ago). After having a closer look at the list of registered MBeans (localhost:8082) I found it (at least something :) My mysqlDS was perfectly registered but not started. After starting it by hand no problems anymore - deployment works. If that still doesn't work for you I could also send you the relevant files from my setup/beans. I will also try to work out why the bloody thing doesn't get started. Anyone any ideas?? Cheers Torsten On Mon, 19 Nov 2001 16:06:25 -0800 Hunter Hillegas [EMAIL PROTECTED] wrote: So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime in? Is no one else running Rabbit Hole with PostgreSQL and 2.0 EJB? From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 16:14:21 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], Dain Sundstrom [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Have you guys included the latest updates to the ConnectionFactoryLoader configuration format? The hsqldb example has been updated, the manual likewise for mysql and postgres. If updating is not the problem, could you post your cfl config? does DefaultDS get started properly on your system? Thanks david jencks On 2001.11.20 12:57:30 -0500 Torsten Schlumm wrote: Hunter, I've seen the same thing with mySQL today (it did work with the CVS sources from about 3 weeks ago). After having a closer look at the list of registered MBeans (localhost:8082) I found it (at least something :) My mysqlDS was perfectly registered but not started. After starting it by hand no problems anymore - deployment works. If that still doesn't work for you I could also send you the relevant files from my setup/beans. I will also try to work out why the bloody thing doesn't get started. Anyone any ideas?? Cheers Torsten On Mon, 19 Nov 2001 16:06:25 -0800 Hunter Hillegas [EMAIL PROTECTED] wrote: So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime in? Is no one else running Rabbit Hole with PostgreSQL and 2.0 EJB? From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 16:14:21 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], Dain Sundstrom [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ 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
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqldb-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar/ !-- -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:postgresql://lo calhost/groundswell DriverClass=org.postgresql.Driver UserName=postgres Password=/attribute attribute name=JndiNameGroundswell/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute !--Anonymous mbean-ref to database being started -- mbean-refJBOSS-SYSTEM:service=PostgreSQL/mbean-ref mbean-ref name=ResourceAdapterNameJCA:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/mbean-ref mbean-ref name=ConnectionManagerFactoryLoaderNameJCA:service=ConnectionManagerFacto ryLoader,name=MinervaSharedLocalCMFactory/mbean-ref attribute name=ConnectionManagerProperties# #Wed Aug 15 16:17:29 EDT 2001 MinSize=0 MaxSize=10 BlockingTimeoutMillis=5000 IdleTimeoutMinutes=30 CleanupIntervalMinutes=10 MaxIdleTimeoutPercent=1.0 /attribute attribute name=PrincipalMappingClass org.jboss.resource.security.ManyToOnePrincipalMapping /attribute attribute name=PrincipalMappingPropertiesUserName=postgres/attribute /mbean /server From: David Jencks [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 13:48:05 -0500 To: Torsten Schlumm [EMAIL PROTECTED] Cc: Hunter Hillegas [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Have you guys included the latest updates to the ConnectionFactoryLoader configuration format? The hsqldb example has been updated, the manual likewise for mysql and postgres. If updating is not the problem, could you post your cfl config? does DefaultDS get started properly on your system? Thanks david jencks On 2001.11.20 12:57:30 -0500 Torsten Schlumm wrote: Hunter, I've seen the same thing with mySQL today (it did work with the CVS sources from about 3 weeks ago). After having a closer look at the list of registered MBeans (localhost:8082) I found it (at least something :) My mysqlDS was perfectly registered but not started. After starting it by hand no problems anymore - deployment works. If that still doesn't work for you I could also send you the relevant files from my setup/beans. I will also try to work out why the bloody thing doesn't get started. Anyone any ideas?? Cheers Torsten On Mon, 19 Nov 2001 16:06:25 -0800 Hunter Hillegas [EMAIL PROTECTED] wrote: So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime in? Is no one else running Rabbit Hole with PostgreSQL and 2.0 EJB? From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 16:14:21 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], Dain Sundstrom [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Well if you want to get down and dirty in jboss/server/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/JDBCEntityMetaData.java line 336 is where it sets the datasouce for each entity. On line 343 you could add System.out.println(Enity = +entityName+ +dataSourceNameString+ +defaultValues.getDataSourceName()); That should give you the datasource the entity is bound to. Hunter Hillegas wrote: Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqldb-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar/ !-- -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:postgresql://lo calhost/groundswell DriverClass=org.postgresql.Driver UserName=postgres Password=/attribute attribute name=JndiNameGroundswell/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute !--Anonymous mbean-ref to database being started -- mbean-refJBOSS-SYSTEM:service=PostgreSQL/mbean-ref mbean-ref name=ResourceAdapterNameJCA:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/mbean-ref mbean-ref name=ConnectionManagerFactoryLoaderNameJCA:service=ConnectionManagerFacto ryLoader,name=MinervaSharedLocalCMFactory/mbean-ref attribute name=ConnectionManagerProperties# #Wed Aug 15 16:17:29 EDT 2001 MinSize=0 MaxSize=10 BlockingTimeoutMillis=5000 IdleTimeoutMinutes=30 CleanupIntervalMinutes=10 MaxIdleTimeoutPercent=1.0 /attribute attribute name=PrincipalMappingClass org.jboss.resource.security.ManyToOnePrincipalMapping /attribute attribute name=PrincipalMappingPropertiesUserName=postgres/attribute /mbean /server From: David Jencks [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 13:48:05 -0500 To: Torsten Schlumm [EMAIL PROTECTED] Cc: Hunter Hillegas [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Have you guys included the latest updates to the ConnectionFactoryLoader configuration format? The hsqldb example has been updated, the manual likewise for mysql and postgres. If updating is not the problem, could you post your cfl config? does DefaultDS get started properly on your system? Thanks david jencks On 2001.11.20 12:57:30 -0500 Torsten Schlumm wrote: Hunter, I've seen the same thing with mySQL today (it did work with the CVS sources from about 3 weeks ago). After having a closer look at the list of registered MBeans (localhost:8082) I found it (at least something :) My mysqlDS was perfectly registered but not started. After starting it by hand no problems anymore - deployment works. If that still doesn't work for you I could also send you the relevant files from my setup/beans. I will also try to work out why the bloody thing doesn't get started. Anyone any ideas?? Cheers Torsten On Mon, 19 Nov 2001 16:06:25 -0800 Hunter Hillegas [EMAIL PROTECTED] wrote: So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime in? Is no one else running Rabbit Hole with PostgreSQL and 2.0 EJB? From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 16:14:21 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], Dain Sundstrom [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't
RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Funny. I just did that but in org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager line 110 where the datasource is looked up. And it successfully looks up my new datasource. I think you have a different problem. I changed the name of the hypersonic data source. May be the problem is your postgresql driver setup. -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 2:41 PM To: Hunter Hillegas Cc: David Jencks; Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Well if you want to get down and dirty in jboss/server/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/ JDBCEntityMetaData.java line 336 is where it sets the datasouce for each entity. On line 343 you could add System.out.println(Enity = +entityName+ +dataSourceNameString+ +defaultValues.getDataSourceName()); That should give you the datasource the entity is bound to. Hunter Hillegas wrote: Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqld b-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar/ !-- -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:p ostgresql://lo calhost/groundswell DriverClass=org.postgresql.Driver UserName=postgres Password=/attribute attribute name=JndiNameGroundswell/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute !--Anonymous mbean-ref to database being started -- mbean-refJBOSS-SYSTEM:service=PostgreSQL/mbean-ref mbean-ref name=ResourceAdapterNameJCA:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/mbean-ref mbean-ref name=ConnectionManagerFactoryLoaderNameJCA:service=Connecti onManagerFacto ryLoader,name=MinervaSharedLocalCMFactory/mbean-ref attribute name=ConnectionManagerProperties# #Wed Aug 15 16:17:29 EDT 2001 MinSize=0 MaxSize=10 BlockingTimeoutMillis=5000 IdleTimeoutMinutes=30 CleanupIntervalMinutes=10 MaxIdleTimeoutPercent=1.0 /attribute attribute name=PrincipalMappingClass org.jboss.resource.security.ManyToOnePrincipalMapping /attribute attribute name=PrincipalMappingPropertiesUserName=postgres/attribute /mbean /server From: David Jencks [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 13:48:05 -0500 To: Torsten Schlumm [EMAIL PROTECTED] Cc: Hunter Hillegas [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Have you guys included the latest updates to the ConnectionFactoryLoader configuration format? The hsqldb example has been updated, the manual likewise for mysql and postgres. If updating is not the problem, could you post your cfl config? does DefaultDS get started properly on your system? Thanks david jencks On 2001.11.20 12:57:30 -0500 Torsten Schlumm wrote: Hunter, I've seen the same thing with mySQL today (it did work with the CVS sources from about 3 weeks ago). After having a closer look at the list of registered MBeans (localhost:8082) I found it (at least something :) My mysqlDS was perfectly registered but not started. After starting it by hand no problems anymore - deployment works. If that still doesn't work for you I could also send you the relevant files from my setup/beans. I will also try to work out why the bloody thing doesn't get started. Anyone any ideas?? Cheers Torsten On Mon, 19 Nov 2001 16:06:25 -0800 Hunter Hillegas [EMAIL PROTECTED] wrote: So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
I'm not so sure. Despite having my jbosscmp-jdbc.xml file included, I get this on the console as it deploys my beans after I made Dave's change: [13:02:37,433,Default] Entity = ProductAttribute java:/DefaultDS null [13:02:37,437,Default] Entity = Product java:/DefaultDS null [13:02:37,439,Default] Entity = Order java:/DefaultDS null [13:02:37,443,Default] Entity = OrderLineItem java:/DefaultDS null [13:02:37,445,Default] Entity = ProductLineItem java:/DefaultDS null [13:02:37,448,Default] Entity = ProductGroup java:/DefaultDS null It's apparently trying to use DefaultDS even though I explicitly tell it not to in the jbosscmp-jdbc.xml file... If your config is working correctly, I'm stumped! From: Dain Sundstrom [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 14:56:24 -0600 To: 'Dave Smith' [EMAIL PROTECTED], Hunter Hillegas [EMAIL PROTECTED] Cc: David Jencks [EMAIL PROTECTED], Torsten Schlumm [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Funny. I just did that but in org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager line 110 where the datasource is looked up. And it successfully looks up my new datasource. I think you have a different problem. I changed the name of the hypersonic data source. May be the problem is your postgresql driver setup. -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 2:41 PM To: Hunter Hillegas Cc: David Jencks; Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Well if you want to get down and dirty in jboss/server/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/ JDBCEntityMetaData.java line 336 is where it sets the datasouce for each entity. On line 343 you could add System.out.println(Enity = +entityName+ +dataSourceNameString+ +defaultValues.getDataSourceName()); That should give you the datasource the entity is bound to. Hunter Hillegas wrote: Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqld b-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar/ !-- -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:p ostgresql://lo calhost/groundswell DriverClass=org.postgresql.Driver UserName=postgres Password=/attribute attribute name=JndiNameGroundswell/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute !--Anonymous mbean-ref to database being started -- mbean-refJBOSS-SYSTEM:service=PostgreSQL/mbean-ref mbean-ref name=ResourceAdapterNameJCA:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/mbean-ref mbean-ref name=ConnectionManagerFactoryLoaderNameJCA:service=Connecti onManagerFacto ryLoader,name=MinervaSharedLocalCMFactory/mbean-ref attribute name=ConnectionManagerProperties# #Wed Aug 15 16:17:29 EDT 2001 MinSize=0 MaxSize=10 BlockingTimeoutMillis=5000 IdleTimeoutMinutes=30 CleanupIntervalMinutes=10 MaxIdleTimeoutPercent=1.0 /attribute attribute name=PrincipalMappingClass org.jboss.resource.security.ManyToOnePrincipalMapping /attribute attribute name=PrincipalMappingPropertiesUserName=postgres/attribute /mbean /server From: David Jencks [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 13:48:05 -0500 To: Torsten Schlumm [EMAIL PROTECTED] Cc: Hunter Hillegas [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Have you guys included the latest updates to the ConnectionFactoryLoader configuration format? The hsqldb example has been updated, the manual likewise for mysql and postgres. If updating is not the problem, could you
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Weird. So this has to point to either the standardjbosscmp-jdbc.xml or jbosscmp-jdbc.xml. What's really strange is the default is null. This should come from standardjbosscmp-jdbc.xml. What else is strange is that it thinks in jboss-cmp-jdbc.xml for each entity you have a datasource element. Maybee grabbing the wrong standard config? Hunter Hillegas wrote: I'm not so sure. Despite having my jbosscmp-jdbc.xml file included, I get this on the console as it deploys my beans after I made Dave's change: [13:02:37,433,Default] Entity = ProductAttribute java:/DefaultDS null [13:02:37,437,Default] Entity = Product java:/DefaultDS null [13:02:37,439,Default] Entity = Order java:/DefaultDS null [13:02:37,443,Default] Entity = OrderLineItem java:/DefaultDS null [13:02:37,445,Default] Entity = ProductLineItem java:/DefaultDS null [13:02:37,448,Default] Entity = ProductGroup java:/DefaultDS null It's apparently trying to use DefaultDS even though I explicitly tell it not to in the jbosscmp-jdbc.xml file... If your config is working correctly, I'm stumped! From: Dain Sundstrom [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 14:56:24 -0600 To: 'Dave Smith' [EMAIL PROTECTED], Hunter Hillegas [EMAIL PROTECTED] Cc: David Jencks [EMAIL PROTECTED], Torsten Schlumm [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Funny. I just did that but in org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager line 110 where the datasource is looked up. And it successfully looks up my new datasource. I think you have a different problem. I changed the name of the hypersonic data source. May be the problem is your postgresql driver setup. -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 2:41 PM To: Hunter Hillegas Cc: David Jencks; Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Well if you want to get down and dirty in jboss/server/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/ JDBCEntityMetaData.java line 336 is where it sets the datasouce for each entity. On line 343 you could add System.out.println(Enity = +entityName+ +dataSourceNameString+ +defaultValues.getDataSourceName()); That should give you the datasource the entity is bound to. Hunter Hillegas wrote: Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqld b-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar/ !-- -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:p ostgresql://lo calhost/groundswell DriverClass=org.postgresql.Driver UserName=postgres Password=/attribute attribute name=JndiNameGroundswell/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute !--Anonymous mbean-ref to database being started -- mbean-refJBOSS-SYSTEM:service=PostgreSQL/mbean-ref mbean-ref name=ResourceAdapterNameJCA:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/mbean-ref mbean-ref name=ConnectionManagerFactoryLoaderNameJCA:service=Connecti onManagerFacto ryLoader,name=MinervaSharedLocalCMFactory/mbean-ref attribute name=ConnectionManagerProperties# #Wed Aug 15 16:17:29 EDT 2001 MinSize=0 MaxSize=10 BlockingTimeoutMillis=5000 IdleTimeoutMinutes=30 CleanupIntervalMinutes=10 MaxIdleTimeoutPercent=1.0 /attribute attribute name=PrincipalMappingClass org.jboss.resource.security.ManyToOnePrincipalMapping /attribute attribute name=PrincipalMappingPropertiesUserName=postgres/attribute /mbean /server From: David Jencks [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 13:48:05 -0500 To: Torsten Schlumm [EMAIL PROTECTED] Cc: Hunter Hillegas [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss
RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
This section of code is called three times. 1) defaults section of standardjbosscmp-jdbc.xml 2) defaults section of jbosscmp-jdbc.xml 3) entity section for each entity specified in jbosscmp-jdbc.xml The first time it will be null. Are you getting a message like in your DEBUG log like this: [2001-11-20 15:16:06,113,CMP,DEBUG] jar:file:/home/dain/work/jboss/jboss-all/bui ld/output/jboss-3.0.0alpha/deploy/Default/relationship.ear/ejb1003.jar!/META -INF /jbosscmp-jdbc.xml found. Overriding defaults If you are not, the jbosscmp-jdbc.xml (NOT jboss-cmp-jdbc.xml) file is in the wrong place or something like that. I tested this and it worked fine for me. -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 3:13 PM To: Hunter Hillegas Cc: Dain Sundstrom; David Jencks; Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Weird. So this has to point to either the standardjbosscmp-jdbc.xml or jbosscmp-jdbc.xml. What's really strange is the default is null. This should come from standardjbosscmp-jdbc.xml. What else is strange is that it thinks in jboss-cmp-jdbc.xml for each entity you have a datasource element. Maybee grabbing the wrong standard config? Hunter Hillegas wrote: I'm not so sure. Despite having my jbosscmp-jdbc.xml file included, I get this on the console as it deploys my beans after I made Dave's change: [13:02:37,433,Default] Entity = ProductAttribute java:/DefaultDS null [13:02:37,437,Default] Entity = Product java:/DefaultDS null [13:02:37,439,Default] Entity = Order java:/DefaultDS null [13:02:37,443,Default] Entity = OrderLineItem java:/DefaultDS null [13:02:37,445,Default] Entity = ProductLineItem java:/DefaultDS null [13:02:37,448,Default] Entity = ProductGroup java:/DefaultDS null It's apparently trying to use DefaultDS even though I explicitly tell it not to in the jbosscmp-jdbc.xml file... If your config is working correctly, I'm stumped! From: Dain Sundstrom [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 14:56:24 -0600 To: 'Dave Smith' [EMAIL PROTECTED], Hunter Hillegas [EMAIL PROTECTED] Cc: David Jencks [EMAIL PROTECTED], Torsten Schlumm [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Funny. I just did that but in org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager line 110 where the datasource is looked up. And it successfully looks up my new datasource. I think you have a different problem. I changed the name of the hypersonic data source. May be the problem is your postgresql driver setup. -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 2:41 PM To: Hunter Hillegas Cc: David Jencks; Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Well if you want to get down and dirty in jboss/server/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/ JDBCEntityMetaData.java line 336 is where it sets the datasouce for each entity. On line 343 you could add System.out.println(Enity = +entityName+ +dataSourceNameString+ +defaultValues.getDataSourceName()); That should give you the datasource the entity is bound to. Hunter Hillegas wrote: Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqld b-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- === == -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar/ !-- === = -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- === = -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Gro undswell attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:p ostgresql://lo calhost/groundswell DriverClass=org.postgresql.Driver UserName=postgres Password=/attribute attribute name=JndiNameGroundswell/attribute attribute
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
At this point I have no idea what to do next... From: Dave Smith [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 16:12:56 -0500 To: Hunter Hillegas [EMAIL PROTECTED] Cc: Dain Sundstrom [EMAIL PROTECTED], David Jencks [EMAIL PROTECTED], Torsten Schlumm [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Weird. So this has to point to either the standardjbosscmp-jdbc.xml or jbosscmp-jdbc.xml. What's really strange is the default is null. This should come from standardjbosscmp-jdbc.xml. What else is strange is that it thinks in jboss-cmp-jdbc.xml for each entity you have a datasource element. Maybee grabbing the wrong standard config? Hunter Hillegas wrote: I'm not so sure. Despite having my jbosscmp-jdbc.xml file included, I get this on the console as it deploys my beans after I made Dave's change: [13:02:37,433,Default] Entity = ProductAttribute java:/DefaultDS null [13:02:37,437,Default] Entity = Product java:/DefaultDS null [13:02:37,439,Default] Entity = Order java:/DefaultDS null [13:02:37,443,Default] Entity = OrderLineItem java:/DefaultDS null [13:02:37,445,Default] Entity = ProductLineItem java:/DefaultDS null [13:02:37,448,Default] Entity = ProductGroup java:/DefaultDS null It's apparently trying to use DefaultDS even though I explicitly tell it not to in the jbosscmp-jdbc.xml file... If your config is working correctly, I'm stumped! From: Dain Sundstrom [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 14:56:24 -0600 To: 'Dave Smith' [EMAIL PROTECTED], Hunter Hillegas [EMAIL PROTECTED] Cc: David Jencks [EMAIL PROTECTED], Torsten Schlumm [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Funny. I just did that but in org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager line 110 where the datasource is looked up. And it successfully looks up my new datasource. I think you have a different problem. I changed the name of the hypersonic data source. May be the problem is your postgresql driver setup. -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 2:41 PM To: Hunter Hillegas Cc: David Jencks; Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Well if you want to get down and dirty in jboss/server/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/ JDBCEntityMetaData.java line 336 is where it sets the datasouce for each entity. On line 343 you could add System.out.println(Enity = +entityName+ +dataSourceNameString+ +defaultValues.getDataSourceName()); That should give you the datasource the entity is bound to. Hunter Hillegas wrote: Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqld b-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar/ !-- -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:p ostgresql://lo calhost/groundswell DriverClass=org.postgresql.Driver UserName=postgres Password=/attribute attribute name=JndiNameGroundswell/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute !--Anonymous mbean-ref to database being started -- mbean-refJBOSS-SYSTEM:service=PostgreSQL/mbean-ref mbean-ref name=ResourceAdapterNameJCA:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/mbean-ref mbean-ref name=ConnectionManagerFactoryLoaderNameJCA:service=Connecti onManagerFacto ryLoader,name=MinervaSharedLocalCMFactory/mbean-ref attribute name=ConnectionManagerProperties# #Wed Aug 15 16:17:29 EDT 2001 MinSize=0 MaxSize=10 BlockingTimeoutMillis=5000
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Okay, maybe I made a mistake. Still, I'm not sure exactly where. I don't get that message in my log file... Still, I have a file called 'jbosscmp-jdbc.xml' in my META-INF directory of my jar file, along with a jboss.xml file and a ejb-jar.xml file... Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 15:20:04 -0600 To: 'Dave Smith' [EMAIL PROTECTED], Hunter Hillegas [EMAIL PROTECTED] Cc: Dain Sundstrom [EMAIL PROTECTED], David Jencks [EMAIL PROTECTED], Torsten Schlumm [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? This section of code is called three times. 1) defaults section of standardjbosscmp-jdbc.xml 2) defaults section of jbosscmp-jdbc.xml 3) entity section for each entity specified in jbosscmp-jdbc.xml The first time it will be null. Are you getting a message like in your DEBUG log like this: [2001-11-20 15:16:06,113,CMP,DEBUG] jar:file:/home/dain/work/jboss/jboss-all/bui ld/output/jboss-3.0.0alpha/deploy/Default/relationship.ear/ejb1003.jar!/META -INF /jbosscmp-jdbc.xml found. Overriding defaults If you are not, the jbosscmp-jdbc.xml (NOT jboss-cmp-jdbc.xml) file is in the wrong place or something like that. I tested this and it worked fine for me. -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 3:13 PM To: Hunter Hillegas Cc: Dain Sundstrom; David Jencks; Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Weird. So this has to point to either the standardjbosscmp-jdbc.xml or jbosscmp-jdbc.xml. What's really strange is the default is null. This should come from standardjbosscmp-jdbc.xml. What else is strange is that it thinks in jboss-cmp-jdbc.xml for each entity you have a datasource element. Maybee grabbing the wrong standard config? Hunter Hillegas wrote: I'm not so sure. Despite having my jbosscmp-jdbc.xml file included, I get this on the console as it deploys my beans after I made Dave's change: [13:02:37,433,Default] Entity = ProductAttribute java:/DefaultDS null [13:02:37,437,Default] Entity = Product java:/DefaultDS null [13:02:37,439,Default] Entity = Order java:/DefaultDS null [13:02:37,443,Default] Entity = OrderLineItem java:/DefaultDS null [13:02:37,445,Default] Entity = ProductLineItem java:/DefaultDS null [13:02:37,448,Default] Entity = ProductGroup java:/DefaultDS null It's apparently trying to use DefaultDS even though I explicitly tell it not to in the jbosscmp-jdbc.xml file... If your config is working correctly, I'm stumped! From: Dain Sundstrom [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 14:56:24 -0600 To: 'Dave Smith' [EMAIL PROTECTED], Hunter Hillegas [EMAIL PROTECTED] Cc: David Jencks [EMAIL PROTECTED], Torsten Schlumm [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Funny. I just did that but in org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager line 110 where the datasource is looked up. And it successfully looks up my new datasource. I think you have a different problem. I changed the name of the hypersonic data source. May be the problem is your postgresql driver setup. -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 2:41 PM To: Hunter Hillegas Cc: David Jencks; Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Well if you want to get down and dirty in jboss/server/src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata/ JDBCEntityMetaData.java line 336 is where it sets the datasouce for each entity. On line 343 you could add System.out.println(Enity = +entityName+ +dataSourceNameString+ +defaultValues.getDataSourceName()); That should give you the datasource the entity is bound to. Hunter Hillegas wrote: Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqld b-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- === == -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar
RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Hunter, try to remove the line mbean-refJBOSS-SYSTEM:service=PostgreSQL/mbean-ref from your postgres-service.xml (or however it's called). I think that should solve the problem. If I understand the whole process right then this means the datasource thingy depends on a service 'PostgreSQL' and therefore doesn't start until this service is available. But it never will be, because it doesn't exist. In the default setup 'DefaultDS' depends on 'Hypersonic' - therefore you have the line mbean-refJBOSS-SYSTEM:service=Hypersonic/mbean-ref And because the hypersonic db gets started by JBoss mbean code=org.jboss.jdbc.HypersonicDatabase name=JBOSS-SYSTEM:service=Hypersonic attribute name=Port1476/attribute attribute name=Silenttrue/attribute attribute name=Databasedefault/attribute attribute name=Tracefalse/attribute /mbean the thing works. You don't need that with external db's If this was complete nonsense shoot me and call me an idiot - or the other way round (David ??) Tell me if it works, Hunter. Cheers Torsten __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
I think you need to remove the anonymous mbean-ref unless you actually have a mbean named JBOSS-SYSTEM:service=PostgreSQL. If you do, what does it do? If not, your ConnectionFactoryLoader will never get started since it is waiting for an mbean you have no plans to create, ever. The original anonymous mbean-ref was needed because jboss is starting the embedded hsqldb server itself, and it doesn't make sense to start up the ConnectionFactory until the db is available. However, with an external db in a separate process, you are unlikely to be starting it with an mbean. david jencks On 2001.11.20 14:46:08 -0500 Hunter Hillegas wrote: Are we sure that the datasource name in jbosscmp-jdbc.xml is even being checked properly? I gave my config another look and it seems correct. Here are is the console log output: [11:43:51,571,AutoDeployer] Auto deploy of file:/Users/hunter/Desktop/jboss-3.0.0alpha/deploy/postgresqldb-default-serv ice.xml [11:43:51,602,Default] Libraries adding URLClassLoader 1240345370 key URL file:/Users/hunter/Desktop/jboss-3.0.0alpha/lib/ext/postgresql.jar [11:43:51,647,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell [11:43:51,653,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell And the file: ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- server classpath archives= postgresql.jar/ !-- -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Groundswell attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:postgresql://lo calhost/groundswell DriverClass=org.postgresql.Driver UserName=postgres Password=/attribute attribute name=JndiNameGroundswell/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute !--Anonymous mbean-ref to database being started -- mbean-refJBOSS-SYSTEM:service=PostgreSQL/mbean-ref mbean-ref name=ResourceAdapterNameJCA:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/mbean-ref mbean-ref name=ConnectionManagerFactoryLoaderNameJCA:service=ConnectionManagerFacto ryLoader,name=MinervaSharedLocalCMFactory/mbean-ref attribute name=ConnectionManagerProperties# #Wed Aug 15 16:17:29 EDT 2001 MinSize=0 MaxSize=10 BlockingTimeoutMillis=5000 IdleTimeoutMinutes=30 CleanupIntervalMinutes=10 MaxIdleTimeoutPercent=1.0 /attribute attribute name=PrincipalMappingClass org.jboss.resource.security.ManyToOnePrincipalMapping /attribute attribute name=PrincipalMappingPropertiesUserName=postgres/attribute /mbean /server From: David Jencks [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 13:48:05 -0500 To: Torsten Schlumm [EMAIL PROTECTED] Cc: Hunter Hillegas [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Have you guys included the latest updates to the ConnectionFactoryLoader configuration format? The hsqldb example has been updated, the manual likewise for mysql and postgres. If updating is not the problem, could you post your cfl config? does DefaultDS get started properly on your system? Thanks david jencks On 2001.11.20 12:57:30 -0500 Torsten Schlumm wrote: Hunter, I've seen the same thing with mySQL today (it did work with the CVS sources from about 3 weeks ago). After having a closer look at the list of registered MBeans (localhost:8082) I found it (at least something :) My mysqlDS was perfectly registered but not started. After starting it by hand no problems anymore - deployment works. If that still doesn't work for you I could also send you the relevant files from my setup/beans. I will also try to work out why the bloody thing doesn't get started. Anyone any ideas?? Cheers Torsten On Mon, 19 Nov 2001 16:06:25 -0800 Hunter Hillegas [EMAIL PROTECTED] wrote: So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime in? Is no one else running Rabbit Hole with PostgreSQL and 2.0 EJB? From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 16:14:21 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], Dain Sundstrom [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? The ds jndi name is loaded in the metadata object of entities
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
David, updating wasn't the problem but the ..-service.xml I simply didn't see one line mbean-refJBOSS-SYSTEM:service=Hypersonic/mbean-ref which I forgot to delete (I used thehsqldb-default-service.xml as a template). Sorry, it was completely my fault. Thanks anyway. Cheers Torsten PS: does that help you, Hunter, in any way?? __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
With this exact jbosscmp-jdbc.xml file ?xml version=1.0 encoding=UTF-8? jbosscmp-jdbc defaults datasourcejava:/MyDS/datasource debugtrue/debug create-tabletrue/create-table remove-tabletrue/remove-table tuned-updatestrue/tuned-updates read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update pk-constrainttrue/pk-constraint relation-mapping-styleforeign-key/relation-mapping-style /defaults /jbosscmp-jdbc I get the following log messages: [2001-11-20 16:17:22,229,CMP,DEBUG] Loading standardjbosscmp-jdbc.xml : file:/ho me/dain/work/jboss/jboss-all/build/output/jboss-3.0.0alpha/conf/default/stan dard jbosscmp-jdbc.xml [2001-11-20 16:17:22,418,Default,INFO] Entity = A_EJB java:/DefaultDS null [2001-11-20 16:17:22,437,CMP,DEBUG] jar:file:/home/dain/work/jboss/jboss-all/bui ld/output/jboss-3.0.0alpha/deploy/Default/relationship.ear/ejb1002.jar!/META -INF /jbosscmp-jdbc.xml found. Overriding defaults [2001-11-20 16:17:22,452,Default,INFO] Entity = A_EJB java:/MyDS java:/DefaultDS Notice that the datasource name changes correctly. Try my exact xml. If it does not work, try getting the current source. If that does not work, check your jar file. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 3:59 PM To: Torsten Schlumm; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Sorta... I can see that the datasource now starts properly. Still, my jar is trying to use DefaultDS instead of the 'Groundswell' ds I defined... From: Torsten Schlumm [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 21:49:31 + (GMT) To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? David, updating wasn't the problem but the ..-service.xml I simply didn't see one line mbean-refJBOSS-SYSTEM:service=Hypersonic/mbean-ref which I forgot to delete (I used thehsqldb-default-service.xml as a template). Sorry, it was completely my fault. Thanks anyway. Cheers Torsten PS: does that help you, Hunter, in any way?? __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___ 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
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Okay. Your file works and gives me an error that it can't find 'MyDS'. I'll have to go back through and see where I screwed up. Thanks everyone for their input and that bug report can be closed as it does not apply. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Tue, 20 Nov 2001 16:22:46 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], Torsten Schlumm [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? ?xml version=1.0 encoding=UTF-8? jbosscmp-jdbc defaults datasourcejava:/MyDS/datasource debugtrue/debug create-tabletrue/create-table remove-tabletrue/remove-table tuned-updatestrue/tuned-updates read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update pk-constrainttrue/pk-constraint relation-mapping-styleforeign-key/relation-mapping-style /defaults /jbosscmp-jdbc ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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
[JBoss-dev] 2.0 jar Really Likes DefaultDS?
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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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
RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Jaws.xml is used in 2.0 persistence? From: Andreas Schaefer [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 13:53:59 -0800 To: Hunter Hillegas [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Hi I am not quite sure with 2.0 but check jaws.xml file therefore you should have the datasource specified. Andy - Original Message - From: Hunter Hillegas [EMAIL PROTECTED] To: Dain Sundstrom [EMAIL PROTECTED]; JBoss Dev [EMAIL PROTECTED] Sent: Monday, November 19, 2001 1:50 PM Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
In your postgresql-default-service.xml what do you have as the JnDIname and the name of the Mbean? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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
RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
No. -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:57 PM To: JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Jaws.xml is used in 2.0 persistence? From: Andreas Schaefer [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 13:53:59 -0800 To: Hunter Hillegas [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Hi I am not quite sure with 2.0 but check jaws.xml file therefore you should have the datasource specified. Andy - Original Message - From: Hunter Hillegas [EMAIL PROTECTED] To: Dain Sundstrom [EMAIL PROTECTED]; JBoss Dev [EMAIL PROTECTED] Sent: Monday, November 19, 2001 1:50 PM Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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 ___ 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
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Groundswell From: Dave Smith [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 17:21:54 -0500 To: Hunter Hillegas [EMAIL PROTECTED] Cc: JBoss Dev [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? In your postgresql-default-service.xml what do you have as the JnDIname and the name of the Mbean? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime in? Is no one else running Rabbit Hole with PostgreSQL and 2.0 EJB? From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 16:14:21 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], Dain Sundstrom [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? 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 datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-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 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
