Issue 6341: Adding InvalidExternalEndpoint Exception to new Bridge::start_bridge()  ope                                                                                                                             (notification-jms-ftf)
Source: PrismTech (Dr. Ramzi Karoui, ramzi.karoui@prismtech.com)
Nature: Uncategorized Issue
Severity: 
Summary: Adding InvalidExternalEndpoint Exception to new Bridge::start_bridge()  operation.
·	The Bridge::start_bridge operation is now raises two exceptions: BridgeAdlreadyStarted and InvalidExternalEndpoint.
The rational behind this extension is that during Bridge::start_bridge operation, consumer and publisher are created. If any ExternalEndpoint information (be it source or sink) is invalid, client cannot be created,   thus InvalidExternalEndpoint will be raised

Resolution: see above
Revised Text: In section 3.1:
add "InvalidExternalEndpoints" to exception list for Bridge::start_Bridge operation definition..

Add the following paragraph to the end of 3.1.2.1:
"
Passing wrong external end point raises the InvalidExternalEndPoints exception.
"

Actions taken:
October 20, 2003: received issue
September 24, 2004: closed issue
Discussion: 
The exception name is InvalidExternalEndpoints. accept proposal to add InvalidExternalEndpoints exception to start_Bridge operation
End of Annotations:=====
hange 3
Adding InvalidExternalEndpoint Exception to new Bridge::start_bridge()  operation.
·	The Bridge::start_bridge operation is now raises two exceptions: BridgeAdlreadyStarted and InvalidExternalEndpoint.
The rational behind this extension is that during Bridge::start_bridge operation, consumer and publisher are created. If any ExternalEndpoint information (be it source or sink) is invalid, client cannot be created,   thus InvalidExternalEndpoint will be raised.