Unfortunately I didn't define a jboss.xml for the bean in question. I'd
assumed, perhaps erroneously, that it wasn't required anymore. Also, EJX
doesn't seem to like editing jboss.xml files - I keep getting a "could not
load file:null". So I poorly assumed that jboss.xml support was in the
process of being dropped.
However, the jboss.xml file, manually created, did fix the problem so thank
you.
I guess the only interesting thing was that I was able to locate the pool by
it's name but obviously bound to the wrong pool. Is this the expected
behaviour? It may be more intuitive for the lookup to fail so at least you
know you've goofed with your set up. Just a thought.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
> Sent: Monday, 25 September 2000 5:59
> To: jBoss
> Subject: Re: [jBoss-User] Problems with Postgres Pools
>
>
> Are you using a "jboss.xml" files for your beans? I suspect the
> problem is that your DB resource is getting bound to the default pool
> instead of the pool you want. If you create a jboss.xml file, you can
> create a resource manager and link the ejb-jar.xml resource to the
> resource manager, and the resource manager to the pool you created.
> There are examples in the Minerva documentation that give the
> necessary chunks of jboss.xml. Also, you could try removing all the other
> pools so that your pool becomes the default pool... That will save you
> some work, but only works if you have exactly 1 pool.
>
> Aaron
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
