Thanks Patrick a solution like that would be ideal and very clean but for
these apps the hosting provider is restricting access to just one mysql
database (without a big hike in rates). I'm no mysql guru but fairly sure in
mysql "database" equates to "schema". 

Thats why i'd originally thought to try having common tables shared by the
webapps (with each table including a differentiating column eg. context) ..
until i realised that would need a swag of customisation after sculptor
generation etc etc

I'm testing thus far with none of those properties defined but ie. simply
hsqldb and jetty but would end up with setting as here:

  db.product = mysql
  db.mysql.type.Bigtext=VARCHAR
  db.mysql.length.Bigtext=2048 
  javaType.BigText=String  
  #
  deployment.applicationServer=Tomcat
  #
  generate.gapClass=true
  findAll.paging=true

Note though I still may be able to negotiate having multiple mysql dbs (its
unlikely but worth another try) - so when you say customise the datasource
do you mean in such a way that it would have appropriate generated
generically into the datasource (somehow based on the webapp context) - or
are you meaning a solution that involves inclusion of a hand-coded
datasource into each webapp?

Thanks,
Mick
-- 
View this message in context: 
http://old.nabble.com/-Sculptor--Injecting-tablenames-from-web-tier--tp27195699s17564p27197150.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer

Reply via email to