Thanks Patrick - after seeing your latest post I sat and pondered the single db approach again and agree the custom AccessImpls and the @PrePersist would remove a lot of the angst i had - esp re handling that column in the webapp but trying to again go back to the mainstream and I'm now negotiating the multiple db instances and fairly sure that will come to fruition without too much trouble.
.. so I'm interested to know if there's someway i can parameterise the persistence.xml so that datasource can be mapped per webapp? You mentioned you could give some tips for that, can i drive that from the webapp so the bt project can remain generic? maybe somehow injecting the appname to do derivation of a datasource name? Thanks, Mick -- View this message in context: http://old.nabble.com/-Sculptor--Injecting-tablenames-from-web-tier--tp27195699s17564p27206123.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
