On 25/01/2011 12:12, javier wrote: > Hi, Hello
> I have a web service published at localhost:8080. I have no problem > using that WS from taverna but if I try to start using the same service > published at another server (i.e: 192.168.1.2:8080 > <http://192.168.1.2:8080/>) it tries to connect to localhost. Even after > removing the localhost service from the services lists in taverna and > after restarting the application. > > Does Taverna keeps any cache that could be bothering? Taverna does have a cache, but it does not save that when you restart. It also should not confuse different IP addresses. > The WSDL is obtained from the correct url but the service called is the > one I added first (localhost). Do you mean that the service panel shows the services as coming from 192... but when you add them into a workflow, then the new service in the workflow runs on localhost? When you check the details of the service, what does it say? If you created a workflow containing WSDL services on localhost, then Taverna obeys what the WSDL service in the workflow says. Putting a WSDL service definition in the service panel that has the same name as the WSDL service in the workflow, will not affect the setting of the WSDL service in the workflow. > Thanks in advance, > Javier Alan ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/ Developers Guide: http://www.taverna.org.uk/developers/
