I should have posted these answers sooner then one month but time flies so here
you go (in case somebody will stumble upon same things):
-I solved relatively fast the wstools problem which turned out to be the result
of using the full path for the SEI class in the command which I described in
po
I think my post is related with this topic as well:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025390#4025390
Need clarification about this please:
1) the wstools.sh script which comes with the jbossws-1.2.0.GA points to both:
WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client
Hello again,
I should've mention that I replaced jbossws-1.0.4.GA (which was included in the
distribution package for JBoss AS) and I installed correctly the
jbossws-1.2.0.GA version (I was careful with the libraries and I can access
"http://localhost:8080/jbossws/"; which is fine).
Now I read
