geronimo-user mailing list archives

You can use a similar path to what the console does to create new
datasources. That is to select a matching RAR (the tranql-connector
RAR for almost any non-XA data source) and then use JSR-88 to
construct a JavaBean tree representing the deployment plan, and then
more JSR-88 to actually deploy it.
However, this is going to create a regular Geronimo deployment. When
you say you don't want this to be persisted, you mean you want it to
be in-memory only and not started up again the next time the server
starts? We don't have explicit support for running modules that are
in-memory only... I'm not sure what you could do to get around that.
Thanks,
Aaron
On 6/25/06, Jimmy Wan <jwan@21technologies.com> wrote:
> I'm trying to build an application where one of the necessary operations
> is the run-time creation of new datasources.
>
> The general idea is that on startup, there will be a single datasource
> registered with Geronimo, containing references to the database
> containing connection information for other databases. If/when new
> databases are registered in the application, the datasources would be
> dynamically added using the connection info that was placed into the
> startup database. The startup database would be the single point of
> configuration for this information. I do want connections to these other
> databases to be managed by Geronimo, but I don't want to manually add
> these connections to Geronimo. I also don't want this configuration
> information to be persisted.
>
> I did something similar with JBoss, but it was a while ago and the
> details are now a tad fuzzy on exactly how this was accomplished.
>
> I could use a nudge in the right direction. What's the best way to do
> this in Geronimo?
>
> --
> Jimmy Wan
> Senior Technical Lead
> 21st Century Technologies, Inc.
>
>
>