Hi everybody,
I ran into the same problem. Did you solve this issue?
I assume that it has something to do with the fact, that I have a https
endpoint.
If I use a http endpoint the message is signed properly.
regards
View the original post :
helmutdoe wrote : Same Problem here ...
|
| $Proxy29 cannot be cast to org.jboss.ws.core.StubExt
|
| did someone solve this problem?
Could you please post your client side code, including the imports? (you too
xinhua). I suspect you might be mixing jaxrpc and jaxws classes.
View the
helmutdoe wrote : The wsse:Security missing occurs if i remove the followin
line on my code.
|
| ((StubExt) ksb).setConfigName(Standard WSSecurity Client);
| |
|
| And this is traceable to me because then the client application do not know
how he should configure the
[EMAIL PROTECTED] wrote : helmutdoe wrote : Same Problem here ...
| |
| | $Proxy29 cannot be cast to org.jboss.ws.core.StubExt
| |
| | did someone solve this problem?
|
| Could you please post your client side code, including the imports? (you
too xinhua). I suspect you
Hi all,
yes think you were right i had mixed RPC und JAXWS. Also after a while i was
able to fix the wsse:Securtiy -Tag missing by using the folloing code
| import java.io.File;
| import java.net.MalformedURLException;
| import java.net.URL;
| import java.util.ArrayList;
| import
Sorry, forgot to paste the codes
| public static void main(String[] args) {
| KSBService ksb = null;
| try {
| //SSL keystore
| System.setProperty(javax.net.ssl.keyStore,
c:\\ksbws.keystore);
|
helmutdoe wrote : The wsse:Security missing occurs if i remove the followin
line on my code.
|
| ((StubExt) ksb).setConfigName(Standard WSSecurity Client);
| |
|
| And this is traceable to me because then the client application do not know
how he should configure the
Same Problem here ...
$Proxy29 cannot be cast to org.jboss.ws.core.StubExt
did someone solve this problem?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160445#4160445
Reply to the post :
I can confirm the same issue occurring when working with JBoss 4.0.5 JBossWS
2.0.0.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160491#4160491
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4160491
helmutdoe wrote : Same Problem here ...
|
| $Proxy29 cannot be cast to org.jboss.ws.core.StubExt
|
| did someone solve this problem?
Im using JBoss AS 4.2.2 GA JBossWS native 3.0.2
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160552#4160552
Reply
I apologize, I might have been a bit ambiguous -- I wanted to say that I
encountered the same wsse:Security is missing error when the client pings
the web service.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4160562#4160562
Reply to the post :
The wsse:Security missing occurs if i remove the followin line on my code.
((StubExt) ksb).setConfigName(Standard WSSecurity Client);
|
And this is traceable to me because then the client application do not know how
he should configure the SecurityHandlers. Since i had debugged the client
ok,
i see, maybe jboss-wsse-client.xml or standard-jaxws-client-config.xml not
loaded ,so i copied the both xml into META-INF and also changed the client code
like this:
|
| Service s = Service.create(url, qn);
| Test port = s.getPort(Test.class);
ok, i think ((StubExt) ksb).setConfigName(Standard WSSecurity Client); is in
a wrong place, now i put it under http auth block
| .
| BindingProvider bp = (BindingProvider)ksb;
|
i updated the jbossWS-native in jboss4.2.2GA to jbossws-3.0.1-native-2.0.4.GA
the severside exception is also changed:(
| 12:45:06,234 ERROR [HandlerChainExecutor] Exception during handler
processing
| org.jboss.ws.core.CommonSOAPFaultException: This service requires
wsse:Security, which
15 matches
Mail list logo
