You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2010/02/20 12:34:40 UTC
[jira] Created: (SMX4-487) Cannot get working Dynamic Endpoint in
SM 4.0.0 container
Cannot get working Dynamic Endpoint in SM 4.0.0 container
---------------------------------------------------------
Key: SMX4-487
URL: https://issues.apache.org/activemq/browse/SMX4-487
Project: ServiceMix 4
Issue Type: Bug
Components: Bundles
Affects Versions: 4.0.0
Environment: Windows NT, SM 4.0.0
Reporter: Andrei Shakirin
Hi,
Test case: custom binding component calls getContext().resolveEndpointReference() by start ConsumerEndpoint and send messages to resolved endpoint
(based on udp:// protocol). The same binding component provides "udp" protocol in getEPRProtocols() and returns ProviderEndpoint in getResolvedEPR() method.
ConsumerEndpoint is started using static sa and sends messages to provider using dynamic endpoint resolving.
Component works fine under ServiceMix 3.3.1.
Problem: I have a following problem with Dynamic Endpoints under SM 4.0.0:
getContext().resolveEndpointReference() in binding component returns ResolvedEndpoint object containing correct ServiceName ({urn:servicemix:my}MyComponent)
If I try to set this endpoint into exchange and send message, following exception occures:
org.apache.servicemix.nmr.api.ServiceMixException: Could not dispatch exchange.
No matching endpoints.
at org.apache.servicemix.nmr.core.FlowRegistryImpl.dispatch(FlowRegistry
Impl.java:110)
I see as a difference that resolveEndpointReference() returns org.apache.servicemix.jbi.servicedesc.DynamicEndpoint object under SM 3.3.1, but under SM 4.0.0 it returns org.apache.servicemix.common.ResolvedEndpoint object.
JUnit test with ServiceMixClient works fine and also resolves endpoint to DynamicEndpoint object.
Source code of binding component is attached.
Thanks,
Andrei.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SMX4-487) Cannot get working Dynamic Endpoint in
SM 4.0.0 container
Posted by "Andrei Shakirin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Shakirin updated SMX4-487:
---------------------------------
Attachment: DynamicEndpointBC.zip
1) Custom binding component project using dynamic endpoint resolution
2) Sample SA for start ConsumerEndpoint in BC
> Cannot get working Dynamic Endpoint in SM 4.0.0 container
> ---------------------------------------------------------
>
> Key: SMX4-487
> URL: https://issues.apache.org/activemq/browse/SMX4-487
> Project: ServiceMix 4
> Issue Type: Bug
> Components: Bundles
> Affects Versions: 4.0.0
> Environment: Windows NT, SM 4.0.0
> Reporter: Andrei Shakirin
> Attachments: DynamicEndpointBC.zip
>
>
> Hi,
> Test case: custom binding component calls getContext().resolveEndpointReference() by start ConsumerEndpoint and send messages to resolved endpoint
> (based on udp:// protocol). The same binding component provides "udp" protocol in getEPRProtocols() and returns ProviderEndpoint in getResolvedEPR() method.
> ConsumerEndpoint is started using static sa and sends messages to provider using dynamic endpoint resolving.
> Component works fine under ServiceMix 3.3.1.
> Problem: I have a following problem with Dynamic Endpoints under SM 4.0.0:
> getContext().resolveEndpointReference() in binding component returns ResolvedEndpoint object containing correct ServiceName ({urn:servicemix:my}MyComponent)
> If I try to set this endpoint into exchange and send message, following exception occures:
> org.apache.servicemix.nmr.api.ServiceMixException: Could not dispatch exchange.
> No matching endpoints.
> at org.apache.servicemix.nmr.core.FlowRegistryImpl.dispatch(FlowRegistry
> Impl.java:110)
> I see as a difference that resolveEndpointReference() returns org.apache.servicemix.jbi.servicedesc.DynamicEndpoint object under SM 3.3.1, but under SM 4.0.0 it returns org.apache.servicemix.common.ResolvedEndpoint object.
> JUnit test with ServiceMixClient works fine and also resolves endpoint to DynamicEndpoint object.
> Source code of binding component is attached.
> Thanks,
> Andrei.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SMX4-487) Cannot get working Dynamic Endpoint in
SM 4.0.0 container
Posted by "Andrei Shakirin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58146#action_58146 ]
Andrei Shakirin commented on SMX4-487:
--------------------------------------
Has anybody an Idea what could be the reason of this problem under ServiceMix 4 ?
> Cannot get working Dynamic Endpoint in SM 4.0.0 container
> ---------------------------------------------------------
>
> Key: SMX4-487
> URL: https://issues.apache.org/activemq/browse/SMX4-487
> Project: ServiceMix 4
> Issue Type: Bug
> Components: Bundles
> Affects Versions: 4.0.0
> Environment: Windows NT, SM 4.0.0
> Reporter: Andrei Shakirin
> Attachments: DynamicEndpointBC.zip
>
>
> Hi,
> Test case: custom binding component calls getContext().resolveEndpointReference() by start ConsumerEndpoint and send messages to resolved endpoint
> (based on udp:// protocol). The same binding component provides "udp" protocol in getEPRProtocols() and returns ProviderEndpoint in getResolvedEPR() method.
> ConsumerEndpoint is started using static sa and sends messages to provider using dynamic endpoint resolving.
> Component works fine under ServiceMix 3.3.1.
> Problem: I have a following problem with Dynamic Endpoints under SM 4.0.0:
> getContext().resolveEndpointReference() in binding component returns ResolvedEndpoint object containing correct ServiceName ({urn:servicemix:my}MyComponent)
> If I try to set this endpoint into exchange and send message, following exception occures:
> org.apache.servicemix.nmr.api.ServiceMixException: Could not dispatch exchange.
> No matching endpoints.
> at org.apache.servicemix.nmr.core.FlowRegistryImpl.dispatch(FlowRegistry
> Impl.java:110)
> I see as a difference that resolveEndpointReference() returns org.apache.servicemix.jbi.servicedesc.DynamicEndpoint object under SM 3.3.1, but under SM 4.0.0 it returns org.apache.servicemix.common.ResolvedEndpoint object.
> JUnit test with ServiceMixClient works fine and also resolves endpoint to DynamicEndpoint object.
> Source code of binding component is attached.
> Thanks,
> Andrei.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.