Hello,
I need to develop a WS, which has to be deployed on the JBoss 3.2.5. I've
search the Web, but without luck :-( Could you suggest me a way how to do
that, point me to web page and the best to point me to the example?
Thanks a lot !!!
Pat
The WS-Security spec does not specify a standard or convention for dynamically encrypting based on client input. Although it could be possible to add a feature that would use the client identity to determine the certificate to use for encryption. Open one in Jira if this is what you want.
Otherwise your options are
| * Use SSL
| * Deploy the same service multiple times per client
| * Use a separate shared client key for encryption, authentication can still be validated using individual keys for signature processing.
|
-Jason
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048464#4048464
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048464
Hi all, i get a clean tomcat-5.5.23 and jbossws.1.2.0. I follow steps of http://labs.jboss.com/jbossws/user-guide/en/html/installation.html#instal...
and then i run tomcat.
When i try to see http://localhost:8080/jbossws i get a 404 error. I see on webapps that jbossws folder is created, but jbossws-deploy is not created.
There is no logs on console, and the file jbossws.log is not created on tomcat/logs.
I open the tomcat-manager, but jbossws application is not listed. Tomcat serlvet samples and others run perfectly.
I checked that jboss*.jar libs are con tomcat/common/lib with activation and mail, and xerces, xalan and serializer jars are on common/endorsed... So I think the instalation is ok.
What i make wrong??
I use jdk_1_5_09 on WindowsXP, i tried on tomcat5.5.20 and 5.5.23 with jbossws 1.2.0 and 1.2.1.
Regards, Enrique.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048424#4048424
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048424
Even when deploying only a single web service, this error may also be caused by some left-overs after refactoring without properly cleaning up.
I changed the name of my service using Eclipse, which left the old compiled classes in various exploded archive folders. Those were then still copied to, and loaded by, JBoss. This resulted in multiple services (same implementation with different class names) within the same application, and thus yielding the "org.jboss.ws.WSException: Multiple context root not supported" error.
My stupid mistake, of course...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048197#4048197
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048197
