[jboss-as7-dev] :installed-drivers-list on managed server or SG?

Brian Stansberry brian.stansberry at redhat.com
Wed Jun 8 12:19:58 EDT 2011


On 6/8/11 3:31 AM, Heiko Braun wrote:
>
> On Jun 8, 2011, at 10:23 AM, Heiko W.Rupp wrote:
>
>> This means to me, that when I deploy something to a server group, this thing
>> ends up in every managed AS  and the other way around: everything that is deployed
>> to a managed AS can be found on all managed AS of the respective server group.
>>
>> This also implies that for deployments, the server-group is the point of interaction and
>> not a single host.
>
>
> IIRC the problem is that only runtime component on each host (JCA in this case)
> knows how to identify the deployment. For any other component it's merely a blob.
> This means that only after a successful deployment to a host, the blob is identified as a JDBC driver
> and hence operation requests need to be executed on this level.
>

Yes, that's why finding out what the installed drivers are requires a 
call to the servers.

-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat


More information about the jboss-as7-dev mailing list