[
https://issues.apache.org/activemq/browse/AMQNET-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Gomes resolved AMQNET-186.
------------------------------
Resolution: Fixed
Added support for the following standard providers:
ActiveMQ
EMS
MSMQ
Stomp
XMS (not implemented yet -- IBM WebSphere)
Configuration files are still supported for additional 3rd Party provider
implementations. Removed the configuration files for the standard providers,
since they are no longer needed.
> Directly support the main official provider implementations connection
> factories.
> ---------------------------------------------------------------------------------
>
> Key: AMQNET-186
> URL: https://issues.apache.org/activemq/browse/AMQNET-186
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Priority: Minor
> Fix For: 1.2.0
>
> Original Estimate: 2 hours
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> The main provider implementations (currently: ActiveMQ, EMS, MSMQ) should be
> directly supported by the Apache.NMS connection factory. The current
> implementation requires an nmsprovider config file for all provider
> implementations. This should be changed as a way to support 3rd party
> provider implementations that are not part of the official distribution
> package.
> It has been noted on the ActiveMQ discussion lists that by far one of the
> most commonly reported issues surrounds issues of where to deploy the
> nmsprovider configuration file, or the lack of deployment. If the Apache.NMS
> module directly supported these providers, this issue would cease to be, and
> the adoption/deployment of NMS would be greatly enhanced.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
