look in org.jboss.metadata.ApplicationMetaData we match on the start of the publicID. This sets a flag marking the app as ejb 2.0. Later in the cmp plugin this flag is checked and the jbosscmp-jdbc.xml file is loaded. If you really want to track down the location of the file load grep the metadata pakages in the cmp plugin.
-dain > -----Original Message----- > From: Fred Loney [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 29, 2001 8:56 PM > To: [EMAIL PROTECTED] > Subject: [JBoss-user] JBoss 3.0 jbosscmp-jdbc.xml not loaded > > > JBoss 3.0 preliminary release replaces jaws.xml with > jbosscmp-jdbc.xml. > I had that working but upgraded the xdoclet version, thereby > regenerating the various .xml files and now JBoss 3.0 loads > standardjaws.xml and ignores standardjbosscmp.xml and > jbosscmp-jdbc.xml. > I restored the pre-upgrade environment to no effect. JBoss loads > entities with the default jaws settings, but ignores jbosscmp-jdbc.xml > settings. No entity is recognized, no matter how trivial the app. > > I am at a loss how to get JBoss 3.0 to load jbosscmp-jdbc.xml. Any > advice is appreciated, including code pointers. I've studied, rebuilt > and hacked the relevant JBoss code all day to no effect. Where is the > decision to load jbosscmp-jdbc.xml made? > > ejb-jar.xml: > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise > JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd";> > > <ejb-jar> > > ... Standard stuff > > jbosscmp-jdbc.xml: > > <?xml version="1.0" encoding="UTF-8"?> > > <jaws> > > .. All ignored > > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
