responding to my own post...
looks like my datasources didn't deploy correctly, even though there was no
error or exception thrown when they were deployed.
I'll check against the latest db service sample files to see if there is
something there...
hunter
__
Hi,
you can also edit standardjboss.xml which is pared each time to map DB
resources to jdbc/whatever.
Burkhard
- Original Message -
From: "Maraya Michael" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 11, 2001 5:12 PM
Subject: RE: [JBoss-user]
s.xml.
---
Michael R. Maraya
> --
> From: Oliver Henlich[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Wednesday, July 11, 2001 8:33 AM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] DataSources, JNDI, ejb-jar.xml and avoiding
> jbo
Hi!
There seem to be so many postings about this stuff and all the solutions
seem to involve the use of jboss.xml. The documentation says "Note that
this file [jboss.xml] is almost NEVER required by JBoss."
I would really like to be able to access the DataSource as all the books
and tutorials de
What you must remember is that this was designed this way
This is to allow you to map things at deployment time. Just like CMP
beans should be mapped at deployment time so should resources. What if
you have 6 DS resources on the server... which should I pick to map to
if you dont tell me (
Every vendor has their own way of glueing the pieces together, most
(that I have experience with, anyway) use XML. For example,
Vendor
GLUE
-
JBoss
jboss.xml + jboss-web.xml
Sun (J2EE SDK) sun-j2ee-ri.xml
BEA
weblogic-ejb-jar.
Hi!
There seem to be so many postings about this stuff and all the solutions
seem to involve the use of jboss.xml. The documentation says "Note that this
file [jboss.xml] is almost NEVER required by JBoss."
I would really like to be able to access the DataSource as all the books and
tutorials
