Jae -- 

"jae77" wrote : i am going to update mapping propery files (the ones used by the 
local.properties file) to have the pk-constraint settting automatically defined. this 
should handle that issue 
  | ...
  |  i know i've accidently forgotten to change the mapping in the local.properties 
file and had these same types of errors. 

OK, you're going to be setting pk-constraint default on a per-DB basis, sounds good. 
But what about properly switching jbosscmp-jdbc.xml settings? 

>From MySQL & Pure-CMP --- issues w News & FAQ modules
 http://www.jboss.org/index.html?module=bb&op=posting&mode=quote&p=3833509

"sesques" wrote : 
  | ...You don't have to rely on database specific tags for the mapping, all the 
mappings are described in the standardjbosscmp-jdbc.xml file. For MySQL, the mapping 
for Strings is VARCHAR(250).
  | 
  | So, you just have to specify the datasource mapping type in jbosscmp-jdbc like LCB 
says ...

"LCB" wrote : 
  | <jbosscmp-jdbc>...
  |   |    <defaults>
  |   |      <datasource>java:NukesDS</datasource>
  |   |      <datasource-mapping>mySQL</datasource-mapping>
  |   |    </defaults>

"hxp" wrote : 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.
  | 

What is the best way -- in the Nukes context -- to implement what Pascal Sesques and 
LCB are recommending? 

Will the user be able to control everything cleanly from local.properties? Will the 
installer work properly, even when a different datasource (other than the one 
specified in local.properties) is selected?

Most importantly, will this work across all nukes modules, and with all 
JBoss-supported databases, transparently without further user configuration?

-- Howard

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833511#3833511

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833511


-------------------------------------------------------
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

Reply via email to