-
1. Re: More soap:address problems
zeeshan.javeed Jan 10, 2008 5:15 AM (in response to justinkwaugh)Hi,
For your point 2, I can confirm that I am using the same settings and its working for me. There must be something which is over-riding ur settings. But if it as simple as it is there, It should work, as it working at my end. Check your annotatoin on Interace and implementation files.
Regards,
Zeeshan -
2. Re: More soap:address problems
asoldano Jan 11, 2008 7:33 PM (in response to justinkwaugh)"justinkwaugh" wrote:
I glanced at the code, and it plainly just ignores the incoming request protocol. Why is this? If I am accessing it via an https:// URL, why would it not rewrite it using https://?
You might want to create a JIRA issue for this.
2. The path to the endpoint is plain wrong.
I have a context root specified in the jboss-web.xml of my war, and that is all it uses no matter what. It simply ignores the servlet name and rewrites the path with just the context-root even when I specify my own WSDL in the @WebService annotation. My servlet is specified in the web.xml as follows..<servlet> <servlet-name>MyWebservice</servlet-name> <servlet-class>com.mycompany.webservices.MyWebservice</servlet-class> </servlet> <servlet-mapping> <servlet-name>MyWebservice</servlet-name> <url-pattern>/*</url-pattern> </servlet-mapping>
My jboss-web.xml has the following:<jboss-web> <context-root>webservice</context-root> </jboss-web>
The correct endpoint should behttps://myhost:443/webservice/MyWebservice
but no matter what I do, it rewrites it to justhttps://myhost:443/webservice
This is the right behaviour IMHO. You should use this to get the path /webservice/MyWebservice:<servlet> <servlet-name>MyWebservice</servlet-name> <servlet-class>com.mycompany.webservices.MyWebservice</servlet-class> </servlet> <servlet-mapping> <servlet-name>MyWebservice</servlet-name> <url-pattern>/MyWebservice</url-pattern> </servlet-mapping>
-
3. Re: More soap:address problems
vxj45 Aug 12, 2008 8:07 PM (in response to justinkwaugh)Is there a solution to issue 1? I am using jboss version 4.2.1.
-
4. Re: More soap:address problems
karypid Aug 13, 2008 2:46 AM (in response to justinkwaugh)Try using @WebContext. It works for me using JBossWS-Native 3.0.2 (which is the latest stable version).
For example:@WebContext(authMethod = "BASIC", transportGuarantee=true, secureWSDLAccess = true) @WebService public class MyService ... { ... }
Make sure to enable the "secureWSDLAccess" flag if you need HTTPS-only access for the published WSDL contract. I understand the "transportGuarantee" is for actual access to the service. -
5. Re: More soap:address problems
vxj45 Aug 15, 2008 10:39 AM (in response to justinkwaugh)I tried setting transportGuarantee="true" and transportGuarantee="CONFIDENTIAL". It didn't work for me. I am using jbossws1.2. Forgive my ignorance but how is jbossws-native different from jbossws1.2?
-
6. Re: More soap:address problems
asoldano Aug 25, 2008 11:15 AM (in response to justinkwaugh)JBossWS Native is the name we gave to our own stack implementation when JBossWS started supporting the Metro and CXF stacks too, see http://jbws.dyndns.org/mediawiki/index.php?title=WSF
JBossWS 1.2 is a really old version of JBossWS instead.