<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><br></div><div>Please note that I was talking about the AS7 management API.</div><div>Make sure not to mix it with JBDS specific requests and accidentally hijack my thread.</div><div><br></div><div>Although the ideas you are describing make sense to me, I still get the feeling it's related </div><div>not related to my suggestion at all and does address a different problem domain.</div><div><br></div><div>Ike</div><br><div><div>On May 9, 2011, at 2:37 PM, Joel Tosi wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">
Pushing Peter's idea of a central repository slightly further - is
this something that we could use in JON? Then standing up new
instances would be able to choose from 'available resources' - maybe
just defining Schema is it didn't exist?<br>
<br>
On 05/09/2011 04:56 AM, Peter Larsen wrote:
<blockquote cite="mid:4DC7BA42.2060608@redhat.com" type="cite">On
05/09/2011 05:35 AM, Heiko Braun wrote:
<br>
<blockquote type="cite">
<br>
Following up with some of the discussion we'd been having in the
past few weeks,
<br>
I would like to call for comments on the idea of a central,
domain level driver registry
<br>
that can be used to query specific deployments like JDBC
drivers.
<br>
</blockquote>
<br>
What I am missing is a registry/wizard help in JBDS to setup data
sources easily. Something where I can quickly create a data
source, and test it, from within JBDS, but where I can also bring
up the wizard and add more advanced options.
<br>
<br>
<blockquote type="cite">Creating datasource configuration is
currently way to complex for the average user.
<br>
Once you've deployed the JDBC driver you need provide the
correct driver name, driver class and version
<br>
besides the regular data source attributes. Since we are lacking
a way to query for installed JDBC drivers
<br>
this currently means providing the required attributes as string
values.
<br>
</blockquote>
Currently we have partly a wizard driven method of doing this for
Hibernate but it somehow doesn't relate to the persistence.xml
which SEAM works on. I also find that I usually work from the
usual 5-10 different data sources over multiple projects. Creating
a repository or registry where I can define my data-sources _once_
and simply pull them in to my current project would be helpful.
Maybe somekind of "data-sources.xml" can be used to store the
registry, imported and exported to/from workspaces would allow the
developer to quickly get common configurations going for a new
workspace/project.
<br>
<br>
There's another advantage - if a password changes to a
data-source, just changing the registry should be enough to change
all deployed versions of that data-source.
<br>
<br>
<br>
<blockquote type="cite">A more simple and less error prone
approach would be to provide a selection of drivers to chose
from.
<br>
But this would require something like a domain level driver
registry.
<br>
</blockquote>
That's already in JBDS? It's a bit buggy since it cannot locate
the driver JAR files correctly but it's there. It would be nice if
selecting a database type would automatically install/implement
the correct driver.
<br>
<br>
<blockquote type="cite">The same mechanism might be used to query
available resource adapters or other specific deployment types
<br>
that are typically referenced by applications.
<br>
</blockquote>
I think that is a dangerous path. I may have 3-4 database drivers
globally in /lib or similar resources that I may not use for
project A but I need for Project B. Besides, the driver alone does
not give me instance name, host name, user name, password to just
mention a few of the required parameters.
<br>
<br>
<blockquote type="cite">Any reasons why this cannot be done?
<br>
Any objections why it shouldn't be?
<br>
Other ideas how this situation can be improved?
<br>
</blockquote>
A central repository for pre-configured data-sources that includes
not only the driver, but url, username, password and hopefully
room for some of the advanced parameters too would be helpful.
Doing it outside JBDS makes little sense to me. And there needs to
be a "reconcile" option so changes done to the registry can be
adopted to the project/application.
<br>
<br>
<br>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
jboss-as7-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>jboss-as7-dev mailing list<br><a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br></blockquote></div><br></body></html>