[
https://issues.apache.org/activemq/browse/AMQNET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60806#action_60806
]
Jim Gomes commented on AMQNET-262:
----------------------------------
After researching and thinking on this topic, I am beginning to question the
use of the GAC with NMS. One of the primary strengths of the architecture of
NMS with broker specific provider implementations is that you can do simple
file copies to install the assemblies. This allows for side-by-side
installation of different versions of NMS. What is the requirement to install
NMS and the provider assemblies into the GAC? I can't see how this has any
benefit, but I can see how it has several downsides. Perhaps explaining how
installing NMS+Providers into the GAC is a "good thing" would be helpful. I'm
beginning to think we are trying to find a solution to a problem that doesn't
exist.
> 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.
