Return-Path: 
 <dev-return-21569-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: (qmail 71626 invoked from network); 10 Aug 2010 20:46:11 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 10 Aug 2010 20:46:11 -0000
Received: (qmail 19545 invoked by uid 500); 10 Aug 2010 20:46:11 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 19428 invoked by uid 500); 10 Aug 2010 20:46:10 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 19419 invoked by uid 99); 10 Aug 2010 20:46:10 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 20:46:10 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 20:46:09 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o7AKjmWI000954
	for <dev@activemq.apache.org>; Tue, 10 Aug 2010 20:45:49 GMT
Message-ID: <20412166.4501281473148955.JavaMail.jira@thor>
Date: Tue, 10 Aug 2010 16:45:48 -0400 (EDT)
From: "Jim Gomes (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQNET-262) NMS cannot be used if installed in
 the GAC
In-Reply-To: <25812807.40601279027911775.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c


     [ https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes resolved AMQNET-262.
------------------------------

    Resolution: Fixed

I changed the search order for loading provider assemblies.  The connection factory will first look for a custom provider configuration file before attempting to use standard provider implementations.  For those applications that want to tightly bind to a specific version of NMS + Provider by installing and accessing the assemblies via the GAC, they can deploy a custom provider config file with the strong name of the assembly.  For example, the following file named {{nmsprovider-activemq.config}} can be deployed into the application installation folder:

{code:xml|title=nmsprovider-activemq.config}
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
	<provider assembly="Apache.NMS.ActiveMQ, Version, Culture, PublicKeyToken" classFactory="Apache.NMS.ActiveMQ.ConnectionFactory"/>
</configuration>
{code}

In the provider tag's assembly attribute, the full GAC version that the application wants to use can be specified.


> NMS cannot be used if installed in the GAC
> ------------------------------------------
>
>                 Key: AMQNET-262
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-262
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: NMS
>    Affects Versions: 1.3.0
>         Environment: Windows .NET 2.0
>            Reporter: Daniel Ellis
>            Assignee: Jim Gomes
>            Priority: Minor
>             Fix For: 1.4.0
>
>         Attachments: NMS GAC.patch
>
>          Time Spent: 45 minutes
>  Remaining Estimate: 0 minutes
>
> If you install {{Apache.NMS.dll}} and {{Apache.NMS.ActiveMQ.dll}} in the GAC then NMS is not able to load {{Apache.NMS.ActiveMQ.dll}}.
> {{NMSConnectionFactory.cs}} is storing the pre-defined connection factories in _schemaProviderFactoryMap_, but is storing the DLL file names to locate the assemblies.
> One solution would be to store the _AssemblyQualifiedName_ instead and leave the assembly loading to the system.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.