You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2009/04/10 11:27:31 UTC

[jira] Assigned: (SM-1835) whitespace interfering with ResolvedEndpoint.resolveEndpoint()

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

Freeman Fang reassigned SM-1835:
--------------------------------

    Assignee: Freeman Fang

> whitespace interfering with ResolvedEndpoint.resolveEndpoint()
> --------------------------------------------------------------
>
>                 Key: SM-1835
>                 URL: https://issues.apache.org/activemq/browse/SM-1835
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-common
>    Affects Versions: 3.3
>            Reporter: Mark Ford
>            Assignee: Freeman Fang
>            Priority: Minor
>         Attachments: patchfile.txt, test-patch.txt
>
>
> The code snippet below is from org.apache.servicemix.common.ResolvedEndpoint :
>     public static ServiceEndpoint resolveEndpoint(DocumentFragment epr, QName elementName, QName serviceName, String uriPrefix) {
>         if (epr.getChildNodes().getLength() == 1) {
>             Node child = epr.getFirstChild();
> The check for the number of child nodes should be checking for the number of element children as opposed to any child like a text node. The way it is now will reject an endpoint reference that has whitespace preceding it. 
> For example:
> DocumentFragment:
> \n
> <wsa:EndpointReference ...>
> \t<wsa:Address>...</wsa:Address>
> </wsa:EndpointReference>
> The work around is to ensure that whitespace is stripped from the EPR prior to it entering SMX. 

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