[ http://jira.codehaus.org/browse/XFIRE-366?page=comments#action_64806 ]
Rob Bork commented on XFIRE-366: -------------------------------- Ross asked me to add to this issue description. The first URL below is what was generated for my Mule-hosted service. The second URL is what it needed to be. So 1) the port was missing 2) the path was wrong...for some reason it replaced 'warehouse' with 'services' and 3) the method was ommitted. http://localhost/services/checkInv http://localhost:8062/warehouse/checkInv?method=canOrderBeFullfilled As I mentioned to Ross, I'm not sure where Mule stops and XFire starts on this issue. But could you please review these three items while you're looking at this issue? Thanks. > wsdlsoap:address location attribute not set correctly in generated WSDL > ----------------------------------------------------------------------- > > Key: XFIRE-366 > URL: http://jira.codehaus.org/browse/XFIRE-366 > Project: XFire > Type: Bug > Components: Core > Versions: 1.1-beta-1 > Reporter: Ross Mason > Assignee: Dan Diephouse > > > We're using the ObjectServiceFactory in Mule (this may be an issue in the way > we construct the Service..) When we grab the generated WSDL the location > attribute is missing the server port. This si definitely set on the endpoint > used to access the service - > </wsdl:binding> > <wsdl:service name="mycomponent"> > <wsdl:port binding="tns:mycomponentHttpBinding" > name="mycomponentHttpPort"> > <wsdlsoap:address location="http://localhost/services/mycomponent"; /> > </wsdl:port> > </wsdl:service> > Should be - http://localhost:8081/services/mycomponent"; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
