You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "lucian.m" <lu...@cdmv.com> on 2011/07/22 22:49:08 UTC
How work publishedEndpointUrl
Hello Sir,
Tomcat in my system is behind the firewall and Apache in the DMZ
I built a service that can be consumed from a Tomcat, but I need the access
from Apache
According to the CXF documentation for this I must add the attribute
"publishedEndpointUrl" element in jaxws: endpoint.
In my project "SimpleWebApp" and CxF-servlet.xml I added:
<jaxws: endpoint id = "endPoint1"
address = "/ p1"
implementor = "# simpleImpl"
publishedEndpointUrl = "http://www.myinc.com/ss/services/p1">
When I call: http://www.myinc.com/ss/services/p1?wsdl I do not get the
expected result.
Do I do something that is not correct.
Please help me to solve this problem.
I've done extensive research on the Internet but without positive result.
Ex :
https://issues.apache.org/jira/browse/CXF-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
Thank you!
--
View this message in context: http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4624660.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: How work publishedEndpointUrl
Posted by "lucian.m" <lu...@cdmv.com>.
Thank you for this information!
Regards,
Lucian Moldoveanu
Département TI | IT Department
www.cdmv.com <http://www.cdmv.com>
________________________________
De : Glen Mazza (Talend) [via CXF] [mailto:ml-node+4638374-887814675-233669@n5.nabble.com]
Objet : Re: How work publishedEndpointUrl
I'm not certain, but first I would get the web service provider to be
accessible at any endpoint URL
(http://www.foo.com/services/mywebservice?wsdl) using the Notes in #2 in
my response below. Then you'll need to find out how to get Apache to
forward http://www.myinc.com/ss/services/p1?wsdl to that URL -- URL
forwarding from Apache to Tomcat I have not done in a very long time but
Apache server has its own mailing list, also that's probably an easily
googlable topic.
Once done, use publishedEndpointURL to change the value to whatever you
want clients to see (so when they enter
http://www.myinc.com/ss/services/p1?wsdl they will see the WSDL), and/or
distribute the WSDL to the SOAP clients with the desired (Apache)
endpoint URL in the wsdl:service section. When the SOAP client is
generated using wsdl-to-java it will use that endpoint URL as the
default in making webservice calls; alternatively the SOAP client can
change the endpoint URL it uses with the
BindingProvider.ENDPOINT_ADDRESS_PROPERTY as shown here:
http://www.jroller.com/gmazza/entry/soap_client_tutorial.
HTH,
Glen
On 07/26/2011 05:55 PM, lucian.m wrote:
> Hello Sir,
>
>
>
> I understand that the publishedEndpointUrl is not the solution.
>
> Can you give me an example of what I have to do to deploy on Tomcat and configure the "public" URL for Apache.
>
> It will be very appreciated if you could help me.
>
>
>
> Thank you!
>
>
>
> Lucian Moldoveanu
>
> Département TI | IT Department
>
> www.cdmv.com<http://www.cdmv.com>
>
>
>
> ________________________________
>
> De : Glen Mazza (Talend) [via CXF] [mailto:[hidden email]]
> Envoyé : 22 juillet 2011 17:05
> À : Moldoveanu, Lucian
> Objet : Re: How work publishedEndpointUrl
>
>
>
> That value is a bit misleading, it is indeed what gets published in the
> WSDL (for clients to reference), but the actual endpoint URL is still
> calculated based on values in Note #2 here:
> http://www.jroller.com/gmazza/entry/web_service_tutorial#notes for
> servlet deployment or Endpoint.publish() for embedded deployment. I.e.,
> what you provide for publishedEndpointURL only affects what is displayed
> in the WSDL, not the real endpoint URL.
>
> Glen
>
> On 07/22/2011 04:49 PM, lucian.m wrote:
>
>
>> Hello Sir,
>>
>> Tomcat in my system is behind the firewall and Apache in the DMZ
>> I built a service that can be consumed from a Tomcat, but I need the access
>> from Apache
>>
>> According to the CXF documentation for this I must add the attribute
>> "publishedEndpointUrl" element in jaxws: endpoint.
>>
>> In my project "SimpleWebApp" and CxF-servlet.xml I added:
>> <jaxws: endpoint id = "endPoint1"
>> address = "/ p1"
>> implementor = "# simpleImpl"
>> publishedEndpointUrl = "http://www.myinc.com/ss/services/p1">
>>
>> When I call: http://www.myinc.com/ss/services/p1?wsdl I do not get the
>> expected result.
>>
>> Do I do something that is not correct.
>> Please help me to solve this problem.
>>
>> I've done extensive research on the Internet but without positive result.
>> Ex :
>> https://issues.apache.org/jira/browse/CXF-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>
>> Thank you!
>>
>> --
>> View this message in context: http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4624660.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
--
Glen Mazza
Application Integration Division
Talend (http://www.talend.com/ai)
blog: http://www.jroller.com/gmazza
________________________________
If you reply to this email, your message will be added to the discussion below:
http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4638374.html
To unsubscribe from How work publishedEndpointUrl, click here <http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4624660&code=bHVjaWFuLm1vbGRvdmVhbnVAY2Rtdi5jb218NDYyNDY2MHwtNzAwNzc3NDE5> .
--
View this message in context: http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4644172.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: How work publishedEndpointUrl
Posted by Glen Mazza <gm...@talend.com>.
I'm not certain, but first I would get the web service provider to be
accessible at any endpoint URL
(http://www.foo.com/services/mywebservice?wsdl) using the Notes in #2 in
my response below. Then you'll need to find out how to get Apache to
forward http://www.myinc.com/ss/services/p1?wsdl to that URL -- URL
forwarding from Apache to Tomcat I have not done in a very long time but
Apache server has its own mailing list, also that's probably an easily
googlable topic.
Once done, use publishedEndpointURL to change the value to whatever you
want clients to see (so when they enter
http://www.myinc.com/ss/services/p1?wsdl they will see the WSDL), and/or
distribute the WSDL to the SOAP clients with the desired (Apache)
endpoint URL in the wsdl:service section. When the SOAP client is
generated using wsdl-to-java it will use that endpoint URL as the
default in making webservice calls; alternatively the SOAP client can
change the endpoint URL it uses with the
BindingProvider.ENDPOINT_ADDRESS_PROPERTY as shown here:
http://www.jroller.com/gmazza/entry/soap_client_tutorial.
HTH,
Glen
On 07/26/2011 05:55 PM, lucian.m wrote:
> Hello Sir,
>
>
>
> I understand that the publishedEndpointUrl is not the solution.
>
> Can you give me an example of what I have to do to deploy on Tomcat and configure the "public" URL for Apache.
>
> It will be very appreciated if you could help me.
>
>
>
> Thank you!
>
>
>
> Lucian Moldoveanu
>
> Département TI | IT Department
>
> www.cdmv.com<http://www.cdmv.com>
>
>
>
> ________________________________
>
> De : Glen Mazza (Talend) [via CXF] [mailto:ml-node+4624709-1224231891-233669@n5.nabble.com]
> Envoyé : 22 juillet 2011 17:05
> À : Moldoveanu, Lucian
> Objet : Re: How work publishedEndpointUrl
>
>
>
> That value is a bit misleading, it is indeed what gets published in the
> WSDL (for clients to reference), but the actual endpoint URL is still
> calculated based on values in Note #2 here:
> http://www.jroller.com/gmazza/entry/web_service_tutorial#notes for
> servlet deployment or Endpoint.publish() for embedded deployment. I.e.,
> what you provide for publishedEndpointURL only affects what is displayed
> in the WSDL, not the real endpoint URL.
>
> Glen
>
> On 07/22/2011 04:49 PM, lucian.m wrote:
>
>
>> Hello Sir,
>>
>> Tomcat in my system is behind the firewall and Apache in the DMZ
>> I built a service that can be consumed from a Tomcat, but I need the access
>> from Apache
>>
>> According to the CXF documentation for this I must add the attribute
>> "publishedEndpointUrl" element in jaxws: endpoint.
>>
>> In my project "SimpleWebApp" and CxF-servlet.xml I added:
>> <jaxws: endpoint id = "endPoint1"
>> address = "/ p1"
>> implementor = "# simpleImpl"
>> publishedEndpointUrl = "http://www.myinc.com/ss/services/p1">
>>
>> When I call: http://www.myinc.com/ss/services/p1?wsdl I do not get the
>> expected result.
>>
>> Do I do something that is not correct.
>> Please help me to solve this problem.
>>
>> I've done extensive research on the Internet but without positive result.
>> Ex :
>> https://issues.apache.org/jira/browse/CXF-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>
>> Thank you!
>>
>> --
>> View this message in context: http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4624660.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
--
Glen Mazza
Application Integration Division
Talend (http://www.talend.com/ai)
blog: http://www.jroller.com/gmazza
RE: How work publishedEndpointUrl
Posted by "lucian.m" <lu...@cdmv.com>.
Hello Sir,
I understand that the publishedEndpointUrl is not the solution.
Can you give me an example of what I have to do to deploy on Tomcat and configure the "public" URL for Apache.
It will be very appreciated if you could help me.
Thank you!
Lucian Moldoveanu
Département TI | IT Department
www.cdmv.com <http://www.cdmv.com>
________________________________
De : Glen Mazza (Talend) [via CXF] [mailto:ml-node+4624709-1224231891-233669@n5.nabble.com]
Envoyé : 22 juillet 2011 17:05
À : Moldoveanu, Lucian
Objet : Re: How work publishedEndpointUrl
That value is a bit misleading, it is indeed what gets published in the
WSDL (for clients to reference), but the actual endpoint URL is still
calculated based on values in Note #2 here:
http://www.jroller.com/gmazza/entry/web_service_tutorial#notes for
servlet deployment or Endpoint.publish() for embedded deployment. I.e.,
what you provide for publishedEndpointURL only affects what is displayed
in the WSDL, not the real endpoint URL.
Glen
On 07/22/2011 04:49 PM, lucian.m wrote:
> Hello Sir,
>
> Tomcat in my system is behind the firewall and Apache in the DMZ
> I built a service that can be consumed from a Tomcat, but I need the access
> from Apache
>
> According to the CXF documentation for this I must add the attribute
> "publishedEndpointUrl" element in jaxws: endpoint.
>
> In my project "SimpleWebApp" and CxF-servlet.xml I added:
> <jaxws: endpoint id = "endPoint1"
> address = "/ p1"
> implementor = "# simpleImpl"
> publishedEndpointUrl = "http://www.myinc.com/ss/services/p1">
>
> When I call: http://www.myinc.com/ss/services/p1?wsdl I do not get the
> expected result.
>
> Do I do something that is not correct.
> Please help me to solve this problem.
>
> I've done extensive research on the Internet but without positive result.
> Ex :
> https://issues.apache.org/jira/browse/CXF-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>
> Thank you!
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4624660.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Application Integration Division
Talend (http://www.talend.com/ai)
blog: http://www.jroller.com/gmazza
________________________________
If you reply to this email, your message will be added to the discussion below:
http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4624709.html
To unsubscribe from How work publishedEndpointUrl, click here <http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4624660&code=bHVjaWFuLm1vbGRvdmVhbnVAY2Rtdi5jb218NDYyNDY2MHwtNzAwNzc3NDE5> .
--
View this message in context: http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4636562.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: How work publishedEndpointUrl
Posted by Glen Mazza <gm...@talend.com>.
That value is a bit misleading, it is indeed what gets published in the
WSDL (for clients to reference), but the actual endpoint URL is still
calculated based on values in Note #2 here:
http://www.jroller.com/gmazza/entry/web_service_tutorial#notes for
servlet deployment or Endpoint.publish() for embedded deployment. I.e.,
what you provide for publishedEndpointURL only affects what is displayed
in the WSDL, not the real endpoint URL.
Glen
On 07/22/2011 04:49 PM, lucian.m wrote:
> Hello Sir,
>
> Tomcat in my system is behind the firewall and Apache in the DMZ
> I built a service that can be consumed from a Tomcat, but I need the access
> from Apache
>
> According to the CXF documentation for this I must add the attribute
> "publishedEndpointUrl" element in jaxws: endpoint.
>
> In my project "SimpleWebApp" and CxF-servlet.xml I added:
> <jaxws: endpoint id = "endPoint1"
> address = "/ p1"
> implementor = "# simpleImpl"
> publishedEndpointUrl = "http://www.myinc.com/ss/services/p1">
>
> When I call: http://www.myinc.com/ss/services/p1?wsdl I do not get the
> expected result.
>
> Do I do something that is not correct.
> Please help me to solve this problem.
>
> I've done extensive research on the Internet but without positive result.
> Ex :
> https://issues.apache.org/jira/browse/CXF-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>
> Thank you!
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/How-work-publishedEndpointUrl-tp4624660p4624660.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Application Integration Division
Talend (http://www.talend.com/ai)
blog: http://www.jroller.com/gmazza