You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2008/09/01 23:13:52 UTC

[jira] Resolved: (SM-1031) ServiceMix uses wrong component to send Message

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

Guillaume Nodet resolved SM-1031.
---------------------------------

    Resolution: Won't Fix

This is not a bug.  The endpoint given in the subscription request is resolved by the JBI container.  In your case, if you give a "http://xxx" address. the servicemix-http component will create a dynamic endpoint that will be used by the WS-NotificationBroker.  If you want to target a JBI endpoint, prepend "endpoint:" to the uri so that you'd have something like "endpoint:[namespace][sep][service][sep][endpoint]"  which could be either something like "endpoint:http://namespace/service/endpoint"  or "endpoint:urn:namespace:service:endpoint".

> ServiceMix uses wrong component to send Message
> -----------------------------------------------
>
>                 Key: SM-1031
>                 URL: https://issues.apache.org/activemq/browse/SM-1031
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-wsn2005
>    Affects Versions: 3.1.1
>         Environment: Win XP/2003, jdk1.6
>            Reporter: amp
>         Attachments: bug.zip
>
>
> When we deploy wsn2005 and http component in our example, we didn't use http componet, just install it. The Message should be sent to comsumer(not http Endpoint), but it was sent to http component, and get error(in attachment). We did not create any http Endpoint. So this is a bug in servicemix. Servimix's wsn2005 component resolves the endpoint with mistake in the exchange of messages.

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