- Create hidden tooltip element:
- Create JS scripts for showing/hiding tooltip:
function show()
{
var tooltip = document.getElementById('tooltip');
tooltip.style.top = event.clientY;
tooltip.style.left = event.clientX + 10;
tooltip.style.display = 'block';
}
function hide(){
var tooltip = document.getElementById('tooltip');
tooltip.style.display = 'none';
} - Set Javascript events for the chosen page element:
Element content
Friday, 29 May 2009
JS: Display tooltip over page element
To display a tooltip over a page element:
Monday, 4 May 2009
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
A piece of code that I've been working on lately started to throw exceptions when calling a web service using a generated client. The logg file contained only the exception message:
"The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state."
Most of the suggestions found in Web blamed the invalid code, giving examples similar to the following one:
Solution:
After debugging the app it came out that solution was quite simple - the service configuration (URL, security settings) was invalid. I found that out by analyzing the InnerException of the main Exception. The logged exception message was rather irrelevant to the actuall error.
"The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state."
Most of the suggestions found in Web blamed the invalid code, giving examples similar to the following one:
Since I was sure this was not the case I had to discover the real exception reason by myself.
using (MyWebServiceClient service = new MyWegServiceClient())
{
service.DoSomeOperation();
service.Close();
service.DoAnotherOperation();
}
Solution:
After debugging the app it came out that solution was quite simple - the service configuration (URL, security settings) was invalid. I found that out by analyzing the InnerException of the main Exception. The logged exception message was rather irrelevant to the actuall error.
Subscribe to:
Posts (Atom)
