Separating development-time and deployment-time configuration

[Maciej Zawadzki]

Hello,

First, I would like to congratulate the OJB team on the great job they've done with the project. I've been playing around with OJB on and off for several months now and I have to say that the project makes a lot of complicated tasks very simple.


My question is about separating development-time configuration options from deployment-time configuration. I look at the xml mapping of objects to database tables (the class-descriptors) to be a development-time configuration. But, the configuration of the database connection (the jdbc-connection-descriptor) is a deployment-time configuration. What I mean is that the class-descriptors would not change even though my datasource, subprotocol, or platform can all change from deployment to deployment.

I would like to be able to develop the application and allow my users to decide what datasource name to attach or what database platform it is going to run on. And hopefully my users could do that through simple configuration and not by having to modify a file within my jar file.

Is there a simple way to accomplish this separation? If not, is there a plan to add support for this?


Thanks,

--Maciej






--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>