Folks, thanks for the replies to this issue.
I was able to get the SSL EJB endpoint to work by storing the generated .wsdl
file at a separate url (a regular HTTP url) and accessing it from there in
order to create my Service object. In this way, I avoided the realm
authentication problems.
Then I created my Call object, using the proper SSL information and injected
the realm credentials into its HTTP header just before executing the invoke()
method:
call.setUsername(HTTPS_AUTH_USERID);
call.setPassword(HTTPS_AUTH_PASSWD);
Hope this helps.
I'm also experimenting with injecting the credentials into the initial Service
object's HTTP header (to avoid storing the .wsdl file at a separate locatioin)
but no joy so far.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929855#3929855
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3929855
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
