Tag: troubleshooting

[Java] A web service client example

Web Services for dummies: creare un servizio web SOAP per Tomcat – il Consumer

During my autumnal experience working with Spring on a e-commerce service library,
I had to implement a Web Service client to interface a popular italian payment gateway.

I found a useful and clear article (in Italian) that explains how to create
Web Service client directly from an Eclipse* wizard:
Web Services for dummies: creare un servizio web SOAP per Tomcat – il Consumer“;

you need only your service’s WSDL URL and wizard will generate Java classes
that you can use as Web Service client.

While building this solution some errors occurred, so here are the solutions…

1) “IWAB0503E Unable to update Java build path. Please check your system environment”
This was trivial, due to presence of two different versions javax.xml.soap under my STS*;
removing one of two and restarting STS(Eclipse)* that was fixed.
Reference: “Unable to update Java build path. Please check your system environment. | Roberto Oróstica Correa’s Blog
2) “Server did not recognize the value of HTTP Header SOAPAction”
The problem is caused by using the wrong SOAP version.
As shown in service definition (wsdl) SOAP version required is 1.2,
but my request was 1.1 version;
to fix you have to change namespace definition in Spring xml configuration file,
from http://schemas.xmlsoap.org/soap/envelope/ (v1.1 namespace)
to http://www.w3.org/2003/05/soap-envelope (v1.2 namespace)

* Actually I was using Spring Tool Suite, based on Eclipse

Service discovered by WSDL

[Ubuntu Firefox] "Your browser does not support OpenSearch search plugins"

If you use ubuntu-repo firefox, maybe you’ll get this error

Your browser does not support OpenSearch search plugins

I found, amongst many curious posts, that such behaviour is caused by Unity Desktop Integration (have a look in Firefox extensions)…

Unity Desktop Integration

So, it’s easy, just disable it and restart Firefox


then try to add a plugin, from Mycroft site for instance


And it works!

banale ripristino di sessione di gnome

in seguito a qualche incauta operazione sui settaggi della sessione di gnome, e conseguente crash del relativo demone, mi ritrovavo costantemente senza gnome-panel, senza la possibilità di agganciarmi al demone di sessione, per esempio dal pannello di controllo, ecc…

le soluzioni al problema trovate googlando erano un po’ tutte drastiche, del tipo “rm -f ~/.gnome2

in realtà, una volta constatato che avviando come “Gnome d’emergenza” (Failsafe) tutto era normale, è bastato copiare, editando il file ~/.gnome2/session, la sezione [fAILSAFE] sopra a quella [Default], e all’avvio tutto era tornato normale

%d blogger hanno fatto clic su Mi Piace per questo: