You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2007/08/03 07:55:48 UTC

[jira] Created: (SM-1014) WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null

WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
------------------------------------------------------------------------------------------------

                 Key: SM-1014
                 URL: https://issues.apache.org/activemq/browse/SM-1014
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-http, servicemix-soap
    Affects Versions: 3.1.1
            Reporter: Gert Vanthienen
            Priority: Minor
             Fix For: 3.1.2, 3.2


The exception can be solved by specifying defaultMep on the HTTP consumer endpoint, but I suppose it would be better to have a good default value for the MEP (In-Out?) on the endpoint instead.  

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

[jira] Resolved: (SM-1014) WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null

Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.

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

Gert Vanthienen resolved SM-1014.
---------------------------------

    Resolution: Fixed
      Assignee: Gert Vanthienen

Added a default value for defaultMep to SoapEndpoint
http://svn.apache.org/viewvc?view=rev&revision=562344
http://svn.apache.org/viewvc?view=rev&revision=562351




> WSDL-first example fails javax.jbi.messaging.MessagingException: Do not understand pattern: null
> ------------------------------------------------------------------------------------------------
>
>                 Key: SM-1014
>                 URL: https://issues.apache.org/activemq/browse/SM-1014
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-http, servicemix-soap
>    Affects Versions: 3.1.1
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>            Priority: Minor
>             Fix For: 3.1.2, 3.2
>
>
> The exception can be solved by specifying defaultMep on the HTTP consumer endpoint, but I suppose it would be better to have a good default value for the MEP (In-Out?) on the endpoint instead.  

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