Hi Tomek,
I was finally able to narrow this down to the
org.codehaus.xfire.transport.http.XFireServletTransport.getServiceURL()
method.
I'm not sure that what I was seeing is technically a bug in XFire. Our
SSL is configured at the hardware level, in a load balancer. As such,
Apache and Tomcat aren't even aware that the connection is encrypted
(which it isn't behind the load balancer).
What appears to be happening is that HttpServletRequest.getScheme()
returns http under this circumstance.
Perhaps this could be added to the set of possible configurable
properties in the future?
In the meantime, I made a custom version of this class to replace the
http with https, and I'm up and running again.
Thanks,
Andrew
Tomek Sztelak wrote:
Hi Andrew,
Can you create jira issue with this ? I'll take a look at it some time
later.
On 4/15/07, Yogesh Chawla - PD <[EMAIL PROTECTED]> wrote:
Hi Andrew,
It looks like you are having problems with the
autogenerated WSDL. I have never cared much for the
WSDL that is autogenerated. Instead I have either
written a WSDL and generated stubs from it or
published the actual WSDL generated by xfire as a
static page with the changes that I needed.
Would something like that work for you?
-Yogesh
--- Andrew Kerr <[EMAIL PROTECTED]> wrote:
> I'd really appreciate some help with this. I spent
> hours looking
> through the XFire source today, and I could not for
> the life of me
> figure out how the URL in:
>
> <wsdlsoap:address
>
location="http://www.something.com/mywebapp/services/MyService"/>
>
> is generated.
>
> A few more details: we're using the
> XFireConfigurableServlet in a web
> application. We use the jsr181 service factory for
> all of our web
> services. The wsdl always looks the same, which
> leads me to believe
> that the code somehow uses the default localhost
> domain name and web
> application context to generate the URL.
>
> Any pointers appreciated.
>
> Thanks,
> Andrew
>
> Andrew Kerr wrote:
> > Hi there,
> >
> > We are porting our application to run entirely
> behind SSL. Our client
> > application is correctly loading the WSDL
> documents via SSL, but
> > unfortunately, the links to the services in the
> generated WSDL are
> > pointing to the unencrypted http version of the
> service.
> >
> > We are using JSR 181 annotations.
> >
> > Here is the offending part of the WSDL:
> >
> > <wsdl:service name="MyService">
> > <wsdl:port name="MyServiceHttpPort"
> binding="tns:MyServiceHttpBinding">
> > <wsdlsoap:address
> >
>
location="http://www.something.com/mywebapp/services/MyService"/>
> > </wsdl:port>
> > </wsdl:service>
> >
> > How do I configure the annotations to set that URL
> to use https?
> >
> > Many thanks,
> > Andrew Kerr
> >
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
>
>
---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
