[JBoss Web Services Metro] - Using WS-Security UsernameToken (jbossws-metro-3.2.1)
by steve_a_edwards
JBoss + Metro client - help!
We are writing a Web Service client to access a Web Service server (.NET) which requires WS-Security UsernameToken with Password Digest.
The server has provided us with a WSDL which does not have any WS-Policy component.
Our client code successfully generates a SOAP message without the WS-Security SOAP Header.
The client code is run from within a Servlet in a web app, which is based on jboss-5.1.0.GA.
The Web Service stack being used is jbossws-metro-3.2.1.GA.
…
[View More]So far, we have not found a successful way of including WS-Security UsernameToken.
Is there a way of programmatically ensuring this is included, without
using xml configuration files?
Having scoured the posts here and on other fora, it appears that for JBoss + Metro, it is
necessary to use a file wsit-client.xml:
- is that correct?
- if yes where in our web app do we need to place it?
- what would the content of this file be?
(Could not find any of the demo files of the package 'org.jboss.test.ws.jaxws.samples.wsse' in the distribution.)
BTW, the transmission will be over SSL, so message-level encryption is not necessary.
Steve
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266717#4266717
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266717
[View Less]
15 years, 3 months
- 1
- 0
[JBoss Web Services Metro] - Re: JBossWS 3.1.2 Metro
by steve_a_edwards
JBoss + Metro client - help!
We are writing a Web Service client to access a Web Service server (.NET) which requires WS-Security UsernameToken with Password Digest.
The server has provided us with a WSDL which does not have any WS-Policy component.
Our client code successfully generates a SOAP message without the WS-Security SOAP Header.
The client code is run from within a Servlet in a web app, which is based on jboss-5.1.0.GA.
The Web Service stack being used is jbossws-metro.
So far, …
[View More]we have not found a successful way of including WS-Security UsernameToken.
Is there a way of programmatically ensuring this is included?
Having scoured the posts here and on other fora, it appears that for JBoss + Metro, it is
necessary to use a file wsit-client.xml:
- is that correct?
- if yes where in our web app do we need to place it?
- what would the content of this file be?
BTW, the transmission will be over SSL, so message-level encryption is not necessary.
Steve
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266665#4266665
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266665
[View Less]
15 years, 3 months
- 1
- 0
[JBoss Web Services Metro] - JBossWS Metro 3.1.1 IllegalStateException - Cannot obtain Se
by mmello
Hello,
I am getting the following error (full stack trace at bottom of posting):
2009-11-06 14:00:02,101 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/Quickstart_webservice_producer].[GoodbyeWorldWS]] Servlet.service() for servlet GoodbyeWorldWS threw exception
java.lang.IllegalStateException: Cannot obtain ServletAdapter
at org.jboss.wsf.stack.metro.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:74)
Background:
I am trying to deploy …
[View More]webservices in JBossESB and secure them with OpenSSO. OpenSSO requires JBossWS Metro or CXF. It cannot use Native.
Also, I have to use JBossESB 4.6 and JBossAS 4.2.3, as those are the only versions that seem to work correctly and integrate with the Eclipse tools I am using.
So ...
When I deploy the JBossESB Quickstart WebserviceProducer sample onto JBossESB4.6+JBossAS4.2.3, it works fine. (This is expected, as it is "as shipped".)
However, if I then install JBossWS Metro 3.1.1 into that JBossAS4.2.3 container and redeploy the exact same Quickstart_webservice_producer.esb file, it gives the above error.
And, I only got this far after copying a few jar files into the servers/default/lib directory, like jboss-ejb3.jar and jboss-ejb3-client.jar.
Any ideas on how to get this to work?
I found ZERO instances of this error via google! I only saw the one instance of a code change where someone committed the error message in code.
I'm not sure if I should post here or in the esb user forum. It is hard to know when dealing with the integration of multiple products.
Thanks for any help with this!
-- Matt
2009-11-06 14:00:02,101 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/Quickstart_webservice_producer].[GoodbyeWorldWS]] Servlet.service() for servlet GoodbyeWorldWS threw exception
java.lang.IllegalStateException: Cannot obtain ServletAdapter
at org.jboss.wsf.stack.metro.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:74)
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
2009-11-06 14:00:02,101 ERROR [org.jboss.soa.esb.actions.soap.AbstractWsdlContractPublisher] Failed to load WSDL contract information from WS Endpoint 'http://cayesb2.sfg.com:8080/Quickstart_webservice_producer/GoodbyeWorldWS...'.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264392#4264392
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264392
[View Less]
15 years, 4 months
- 1
- 0
- ← Newer
- 1
- Older →