Purushottam, 1. You need to have a jaws.xml file if you have entity beans. That's where you'd set up the datasource to use and the type mappings if you are not happy with the standardjaws.xml file, the bean fields and the mapping to the database columns and so on and so forth. 2. To the best of my knowledge, jaws.xml settings would override settings in standardjaws.xml. I wouldn't really call it 'derived'. There is usually a great deal more of info in the standardjaws.xml file than you'd ever have in the jaws.xml file :) 3. Would be best if you have the ejbs packaged in a single jar file, unless you have a very good reason. Vinay
----- Original Message ----- From: purushottam naktode Sent: Tuesday, May 01, 2001 8:01 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] should all ejbs be specified in one ejb-jar.xml fil
Hi,
I am trying to deploy multiple ejbs, each packaged
in a seperate jar and having their own ejb-jar.xml and
jboss.xml file ( Q 1. Should it also have jaws.xml ?
Q2. Should jaws.xml be derived from
\conf\standardjaws.xml Q3. Should all ejbs be
specified in only one ejb-jar.xml file ?)
I get the error "bean found in jaws.xml but is not
cmp-managed in ejb-jar.xml file" (not exact message).
What could be the problem. Please help.
Thanks,
Puru.
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
|
