And what better way to test it than to post a new blog announcing it! If you're reading this, then it works FINE!
Get your copy HERE!
And what better way to test it than to post a new blog announcing it! If you're reading this, then it works FINE!
Get your copy HERE!
Ran into an issue today while trying to connect to a Java Web Service from a .Net environment. It looks like this happens when Web Service Security is enabled in the application server of the web service and uses the ActorURI attribute. .Net's Web Services Enhancements feature does not support relative URI's for this attribute and basically FUBAR's on you. Therefore, you must us an absolute URI.
An example of an absolute URI is "http://LoginWebService" while an example of a relative URI would be "LoginWebService"... You must configure your Application Server to using either the Rational Application Developer or the Application Server Toolkit.