Hi Pascal, Hi LCB -- Thanks for your suggestions.
Your standardjbosscmp-jdbc.xml / jbosscmp-jdbc.xml analysis has the ring of truth to it; we need to check into it to determine for sure. Your analysis also explains why this is not a general problem for JBoss, but is a general problem for Nukes.... all Nukes modules share the faulty configuration file(s). These faulty configuration files would have been manually administered in a typical JBoss app environment, but instead they are automatically generated or fixed in CVS and automatically included in the Nukes build process. Because Nukes modules have never used pure-CMP prior to now (in particular, using the create-table xdoclet tag to generate the xml to get the container to create the tables), this problem has never shown up before now. The next question is where to put the fix(es) into Nukes -- * in the nukes installer? * in the ant build process... the build.xml? the local.properties file? the mapping propery files? Jae's post begins to go into this question; looks like we're hot on the trail of a good solution. Thanks again for helping us get pure-CMP going for Nukes. --Howard View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833509#3833509 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833509 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
