On 20/04/2010 14:00, Shinan Kassam wrote: > I am using: > BlazeDS Turnkey: > Tomcat 6.0.14
Old: 6.0.26 is the latest, you should plan to upgrade asap. > I am building only AMF type services > > I currently have custom authentication working using JDBCRealm. Hence, I > have some database parameters in server.xml as well as my application. Is it > possible to use a portion of the URL as a parameter to connect to a > different database. Use the DataSourceRealm, JDBCRealm is slow & not recommended for production. > For example, currently I use the following URL: > http://localhost:8400/samples/messagebroker/amf > > If the URL was something like: > http://localhost:8400/samples/messagebroker/<customer>/amf > I would like to connect to the database for <customer>. Is anything stopping you from using that information as part of your custom authentication? > Would it be best to pull the portion of the url for the customer and > dynamically create the database connection programatically? Would be slow to do that every time. > OR just have different applications for different customers. > > Alternative: > http://localhost:8400/<customer>/messagebroker/amf > So each customer would physically have different folders and different > applications with different database configurations. It's a little extra work during the build process, but having independent apps is the route I'd take. p
signature.asc
Description: OpenPGP digital signature
