I wanted to update this with a partial solution.
It seems that the josso install places a jar file within tomcats server/lib
that contains a file:
client-config.wsdd
This file contains an entry:
<handler name="WebserviceClientAuthentication"
type="java:org.josso.gateway.WebserviceClientAuthentication"/>
<globalConfiguration>
<requestFlow>
<handler type="WebserviceClientAuthentication"/>
</requestFlow>
</globalConfiguration>
That entry was causing my axis call to fail. Right now I have simply removed
that client-config.wsdd from the jar file altogether and everything seems to
be working. I have no real idea, however, if the josso agent code is still
authenticating as it should.
The file in question is also located within :
webapps/josso/WEB-INF/classes/client-config.wsdd
webapps/josso/WEB-INF/lib/josso-1.5.jar
So I'm hopeful that the josso agent is indeed working as it should. I am
asking the author on ways for me to verify this.
Regards,
-Dennis
Hello.
I have been working on this problem for days now and it seems as if I'm
taking one step
forward and two back. I could use your help please. The short story is that
I'm trying
to logout a josso session id via a web service from within a servlet and it
fails seemingly
within the Axis layer before contacting the outside world.
Here is the mysterious error from my tomcat log:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.apache.axis.ConfigurationException:
java.lang.ClassCastException:
org.josso.gateway.WebserviceClientAuthentication
java.lang.ClassCastException:
org.josso.gateway.WebserviceClientAuthentication
--
View this message in context:
http://www.nabble.com/Axis-Version-1-Question-Problem-tf4884334.html#a13996012
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
