[esb-issues] [JBoss JIRA] Commented: (JBESB-2946) Integration with Riftsaw - ESB service orchestration raises exception

[Len DiMaggio (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12493067#action_12493067 ] 

Len DiMaggio commented on JBESB-2946:
-------------------------------------

Some of the gateways register non-ESB endpoints in the registry, JBossRemoting and HttpGateway.  This is occurring because the SI has found one of these but has ignored it.

> Integration with Riftsaw - ESB service orchestration raises exception
> ---------------------------------------------------------------------
>
>                 Key: JBESB-2946
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2946
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Registry and Repository
>    Affects Versions: 4.6
>         Environment: ESB 4.6
> Riftsaw - from trunk
>            Reporter: Len DiMaggio
>            Priority: Optional
>
> See example code here:
>    http://riftsaw.blogspot.com/2009/11/from-bpel-to-esb-and-back-introduction.html
> The integration successfully orchestrates the ESB service, but it raises this exception:
> 22:38:51,160 INFO [ServiceInvoker] Badly formed EPR [EPR:PortReference <> <wsa:Address http://localhost:8081/> >] for Service> [FirstServiceESB:SimpleListener] and Message [header: [ ]].Courier for > EPR not supported: ESB-unaware EPR used!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira