stlecho wrote: > Ruwan, > > I've been adding my endpoints and proxies to v1.7.1. When sending an XML > request to the proxy endpoint, I'm receiving a "HTTP/1.1 202 Accepted" > response but I have the impression that the external webservice is not > called. > > Comparing the old (v1.7beta2) with the new synapse.xml config file, I've > noticed that it was possible to specify an endpoint on the target element. > Is this still supported in v1.7.1 ? > Yeah, it does. Basically you should be able to export the full configuration of the ESB 1.7 to the 1.7.1.
May be you are invoking the proxy with a wrong URL in which case the main sequence is used for mediation and drops the message. Thanks, Ruwan > Regards, Stefan. > > Ruwan Linton-3 wrote: > >> Hi Stefan, >> >> We didn't fixed any functional issues in the 1.7.1 release, but we just >> fixed the FireFox3 issues which are on the UI layer. Being said that >> this feature is there on the 1.7 release as well. There fore this has to >> work if the configuration is correct, so you may give this a try with >> the new release and see whether you can get this to work.... If there >> are any errors, you can raise them on them and I will help you to get >> these issues resolved. >> >> Thanks, >> Ruwan >> >> stlecho wrote: >> >>> Ruwan, >>> >>> Has this functionality been released in the v1.7.1 ? >>> >>> PS: Sorry for this terrible late response, but I had some other >>> priorities. >>> >>> Regards, Stefan. >>> >>> Ruwan Linton-3 wrote: >>> >>> >>>> stlecho wrote: >>>> >>>> >>>>> The response I'm getting back from the Webservice is not signed with >>>>> WS-Security. If Rampart tries to treat this message in raises an >>>>> exception, >>>>> because it is supposed to handle signed messages. Rampart should in >>>>> this >>>>> case not be activated at all. >>>>> >>>>> >>>>> >>>> Hi Stefan, >>>> >>>> Sorry for the late reply, I just did another test on this functionality >>>> and found that it is working on the SNAPSHOT (latest build). Could you >>>> please bring the summery of the problem with all logs and configurations >>>> in to the table and lets try to get this resolved. >>>> >>>> You may send a mail to the user list or file a JIRA issue with all the >>>> relevant configurations to reproduce the issue. >>>> >>>> Thanks, >>>> Ruwan >>>> >>>> _______________________________________________ >>>> Esb-java-user mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user >>>> >>>> >>>> >>>> >>> >>> >> _______________________________________________ >> Esb-java-user mailing list >> [email protected] >> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user >> >> >> > > _______________________________________________ Esb-java-user mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
