<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>what about deployment types?</div><div><br></div><div>i.e. [localhost:9999 /] /deployment=mysql-connector-java-5.1.15.jar:read-resource</div><div>{</div><div> "outcome" => "success",</div><div> "result" => {</div><div> "name" => "mysql-connector-java-5.1.15.jar",</div><div> "runtime-name" => "mysql-connector-java-5.1.15.jar",</div><div><span class="Apple-tab-span" style="white-space:pre"> </span><b>"type" => "JDBC_DRIVER</b></div><div> "hash" => bytes {</div><div> 0x47, 0x95, 0xcc, 0x29, 0x33, 0x8b, 0x50, 0x49,</div><div> 0xe2, 0x38, 0x94, 0x12, 0x31, 0xb3, 0x6b, 0x39,</div><div> 0x46, 0x95, 0x29, 0x91</div><div> }</div><div> },</div><div> "compensating-operation" => undefined</div><div>}</div><div><br></div><div><br></div><br><div><div>On Apr 15, 2011, at 3:33 PM, Jason T. Greene wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>I think the best solution here is to have a management operation on a runtime node that returns the "available" drivers.<br><br>On 4/15/11 8:29 AM, John Bailey wrote:<br><blockquote type="cite">Currently there is no way. I think we will need update the<br></blockquote><blockquote type="cite">deployment based drive install in some way to make that available.<br></blockquote><blockquote type="cite">The problem with having the deployment add the drivers to the model<br></blockquote><blockquote type="cite">is you then have multiple ways to manage it. You could undeploy to<br></blockquote><blockquote type="cite">remove or you could use a model operation to remove. This should be<br></blockquote><blockquote type="cite">ok as long as the deployment is smart enough to not update the model,<br></blockquote><blockquote type="cite">on undeploy, if the driver was removed by a model op.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Something we should think about from a architectural point of view is<br></blockquote><blockquote type="cite">whether or not we want deployments updating the model in this way.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">John<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Apr 15, 2011, at 8:14 AM, Heiko Braun<<a href="mailto:hbraun@redhat.com">hbraun@redhat.com</a>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I managed to deploy JDBC drivers through the HTTP API. Creating<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">datasources works as well. The remaining question is:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">How to I locate the JDBC drives that are installed as a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">deployment? They don't show up under<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">/subsystem=datasources/jdbc-driver=*<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">In order to create the Datasource I need to provide a list of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">available drives to the user.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Ike<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________ jboss-as7-dev<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">mailing list <a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________ jboss-as7-dev mailing<br></blockquote><blockquote type="cite">list <a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br></blockquote><blockquote type="cite"><a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br></blockquote><br><br>-- <br>Jason T. Greene<br>JBoss, a division of Red Hat<br></div></blockquote></div><br></body></html>