Out of curiosity is your webservice provided by the LC server? We were
having a similar so we dynamically created the webservice connection,
and called the webservice and the result through the script so that
there was no need for binding and using hidden fields. We used the
event.target.URL function to grab the address of the server that the
form is being used on when opened in workspace. Then you'd just do
some string manipulation to grab the first few characters of the
string to get the server name, append your webservice to the end of
the string. The only problem we had with this is that if i went ahead
used pdf preview in designer, it would give me all these msgs saying
that it was trying to connect to my local computer. So we created a
form variable to hold the event.target.URL and if it doesn't start
with "http" it means the form is being called from a local machine
(rather than workspace), and thus an address is hardcoded.
And additional benefit is that you only need to call event.target.url,
so if you're testing through preview pdf, you only get the message
that its trying to connect to your machine once.
function GetWebservice()
{
if(ServerUrl.value!=null && ServerUrl.value.substring(0,4)=="http")
{
//Server Previously Found;
return ServerUrl.value;
}
var server = event.target.URL;
if(server.substring(0,7)!="http://")
server = "
http://serverName:8080/workspace/";
server = server.substring(0,server.indexOf("/",8));
ServerUrl.value = server;
return server;
}
Then you can use that url to append your webservice address;
var myUrl = GetWebservice() + "/soap/services/myWebService?wsdl";
var connection = Net.SOAP.connect(myUrl);
var result = connection.webServiceMethod({"param1": value1, "param2":
value2});
Hope that helped and wasn't too unclear :)
Billy
On May 14, 7:58 am, Amal Elaine <
amalela...@gmail.com> wrote:
> Thanks Duane,
>
> I can share the specifics, not a problem there, but your comments have me
> rethinking my approach. You know, for each form to make a back-end
> connection in order to complete a search may be overkill. I think I will
> hold on this until we have an adobe resource in house so we can further
> address an efficient solution. I continue to suffer from "I don't know what
> I don't know" ;-)
>
> Elaine
>