You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2007/10/27 01:11:53 UTC
[jira] Commented: (CXF-1143) Default CXF behavior of listing all
available endpoints
[ https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131 ]
Glen Mazza commented on CXF-1143:
---------------------------------
Do you mean that http://my-host/cxf/ shows the WSDL? Is that the problem, you want to suppress showing the WSDL, regardless of address, or you just don't want to show it at that particular address? (i.e. the normal http://myhost/cxf/service?wsdl or whatever address would be OK for you)?
> Default CXF behavior of listing all available endpoints
> -------------------------------------------------------
>
> Key: CXF-1143
> URL: https://issues.apache.org/jira/browse/CXF-1143
> Project: CXF
> Issue Type: Improvement
> Reporter: Tawfik Lachheb
>
> If I publish the cxf servlet as /cxf then going to http://my-host/cxf/ lists all available endpoints.
> This is something we don't want to have in our production environment. Is there a way to disable this?
> Thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (CXF-1143) Default CXF behavior of listingall
available endpoints
Posted by Adrian C <ad...@gmail.com>.
I think I see what is going on - in the servlet controller the generate list
is call getDestinations not getDestinations for path... will try to rebuild
& test with this and see if that fixes the problem
Willem2 wrote:
>
>
> Ok, there are some changes in CXFServlet 2.0.3(vote version).
> So please let me know if here any issue with the new coming up 2.0.3.
>
> Willem.
>
> -----Original Message-----
> From: Adrian C [mailto:adrian.corcoran@gmail.com]
> Sent: Tue 11/13/2007 1:18
> To: cxf-dev@incubator.apache.org
> Subject: RE: [jira] Commented: (CXF-1143) Default CXF behavior of
> listingall available endpoints
>
>
>
> Hi,
>
> Let me validate that's what I saw when trying that rather than waste your
> time. I am using 2.0.3, but just moved to it on Friday - I may have seen
> that with 2.0.2 though ... will verify tonight what if the issue is still
> there.
>
>
> Willem2 wrote:
>>
>>
>> Hi,
>>
>> I don't think CXFServlet share the same Bus instance together.
>> I will look this issue later today .
>> BTW, which CXF are you using?
>>
>> Willem.
>>
>> -----Original Message-----
>> From: Adrian C [mailto:adrian.corcoran@gmail.com]
>> Sent: Tue 11/13/2007 0:08
>> To: cxf-dev@incubator.apache.org
>> Subject: Re: [jira] Commented: (CXF-1143) Default CXF behavior of
>> listingall available endpoints
>>
>>
>> If you have two servlets, they both displpay the same list of services:
>>
>> <servlet>
>> <servlet-name>CoreCXFServlet</servlet-name>
>> <display-name>Core CXF Servlet</display-name>
>>
>> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
>> <init-param>
>> <param-name>config-location</param-name>
>> <param-value>com/xxx/de/ws/core/services/ws.context.xml</param-value>
>> </init-param>
>> <load-on-startup>4</load-on-startup>
>> </servlet>
>>
>> <servlet>
>> <servlet-name>ExtCXFServlet</servlet-name>
>> <display-name>Extensions CXF Servlet</display-name>
>>
>> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
>> <init-param>
>> <param-name>config-location</param-name>
>> <param-value>com/xxx/de/ws/ext/services/ws.context.xml</param-value>
>> </init-param>
>> <load-on-startup>5</load-on-startup>
>> </servlet>
>>
>> I have't looked into this but I think its because they both use the same
>> bus, where as xfire used separate xfire instances for exache
>> XFireConfigurableServlet
>>
>>
>>
>> Glen Mazza-2 wrote:
>>>
>>> I don't think it is necessarily "missing" with CXF:
>>> http://www.jroller.com/gmazza/date/20071019#step7
>>>
>>> I would guess you just need to add a separate mapping in the web.xml to
>>> another servlet, and turn on the display for xxx and turn it off for
>>> yyy.
>>>
>>> Glen
>>>
>>> Am Montag, den 12.11.2007, 03:59 -0800 schrieb Adrian C:
>>>>
>>>> Hi, just saw this and its something that is applicable to some of the
>>>> work
>>>> that I am doing also. Perhaps one of the things that is missing here
>>>> and
>>>> was
>>>> something that you could do with xfire is to have different endpoints
>>>> available from different servlets - that way when you went to
>>>> http://my-host/cxf/xxx you could see one list of services and
>>>> http://my-host/cxf/yyy you could see another...
>>>>
>>>>
>>>> JIRA jira@apache.org wrote:
>>>> >
>>>> >
>>>> > [
>>>> >
>>>> https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
>>>> > ]
>>>> >
>>>> > Glen Mazza commented on CXF-1143:
>>>> > ---------------------------------
>>>> >
>>>> > Do you mean that http://my-host/cxf/ shows the WSDL? Is that the
>>>> problem,
>>>> > you want to suppress showing the WSDL, regardless of address, or you
>>>> just
>>>> > don't want to show it at that particular address? (i.e. the normal
>>>> > http://myhost/cxf/service?wsdl or whatever address would be OK for
>>>> you)?
>>>> >
>>>> >> Default CXF behavior of listing all available endpoints
>>>> >> -------------------------------------------------------
>>>> >>
>>>> >> Key: CXF-1143
>>>> >> URL: https://issues.apache.org/jira/browse/CXF-1143
>>>> >> Project: CXF
>>>> >> Issue Type: Improvement
>>>> >> Reporter: Tawfik Lachheb
>>>> >>
>>>> >> If I publish the cxf servlet as /cxf then going to
>>>> http://my-host/cxf/
>>>> >> lists all available endpoints.
>>>> >> This is something we don't want to have in our production
>>>> environment.
>>>> >> Is there a way to disable this?
>>>> >> Thanks
>>>> >
>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13708181
>> Sent from the cxf-dev mailing list archive at Nabble.com.
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13709780
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13730792
Sent from the cxf-dev mailing list archive at Nabble.com.
RE: [jira] Commented: (CXF-1143) Default CXF behavior of listingall
available endpoints
Posted by Adrian C <ad...@gmail.com>.
sorry for the deplay in getting back - swamped.
yes this issue occurs in 2.0.3, below are snippets of my configuration. When
I go to either servlet in my browser, I get the full list of services
registered in the system both prod & noprod.
I suppose the easiest way to fix this would be to patch generateServiceList
to see if the address contains the servlet path from the
httpservletrequest...
web.xml
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>
classpath*:/com/testing/de/ws/xfire/core/cxf-init.xml
</param-value>
</context-param>
<servlet>
<servlet-name>CoreCXFServlet</servlet-name>
<display-name>Core CXF Servlet</display-name>
<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
<init-param>
<param-name>config-location</param-name>
<param-value>com/testing/de/ws/xfire/core/services/ws.context.xml</param-value>
</init-param>
<load-on-startup>4</load-on-startup>
</servlet>
<servlet>
<servlet-name>NonProdCXFServlet</servlet-name>
<display-name>Non Production CXF Servlet</display-name>
<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
<init-param>
<param-name>config-location</param-name>
<param-value>com/testing/de/ws/xfire/core/services/ws.nonprod.context.xml</param-value>
</init-param>
<load-on-startup>5</load-on-startup>
</servlet>
cxf-init.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
"http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
<import resource="classpath:META-INF/cxf/cxf.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" />
<import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
<!-- load up the beans, needed for local transport -->
<import
resource="classpath:com/testing/de/ws/xfire/core/services/ws.context-beans.xml"
/>
</beans>
ws.context.xml:
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cxf="http://cxf.apache.org/core"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd">
<bean id="propertyConfigurer"
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="locations" >
<list>
<value>classpath:com/testing/de/config/default.deployment.properties</value>
<value>${testing.dir}/config/deployment.properties</value>
</list>
</property>
<property name="ignoreUnresolvablePlaceholders" value="true" />
<property name="ignoreResourceNotFound" value="true" />
</bean>
<!-- services -->
<import
resource="classpath:com/testing/ws/de/identitymanagement/IdentityManagementV1.xml"
/>
<import
resource="classpath:com/testing/ws/de/servicemanagement/ServiceManagementV1.xml"
/>
<import resource="classpath:com/testing/ws/de/nist/NistV1.xml" />
<import
resource="classpath:com/testing/ws/de/identification/IdentificationV1.xml"
/>
</beans>
ws.nonprod.context.xml:
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cxf="http://cxf.apache.org/core"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd">
<bean id="propertyConfigurer"
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="locations" >
<list>
<value>classpath:com/testing/de/config/default.deployment.properties</value>
<value>${testing.dir}/config/deployment.properties</value>
</list>
</property>
<property name="ignoreUnresolvablePlaceholders" value="true" />
<property name="ignoreResourceNotFound" value="true" />
</bean>
<!-- not production... -->
<import
resource="classpath:com/testing/ws/de/policymanagement/PolicyManagementV1.xml"
/>
</beans>
Willem2 wrote:
>
>
> Ok, there are some changes in CXFServlet 2.0.3(vote version).
> So please let me know if here any issue with the new coming up 2.0.3.
>
> Willem.
>
> -----Original Message-----
> From: Adrian C [mailto:adrian.corcoran@gmail.com]
> Sent: Tue 11/13/2007 1:18
> To: cxf-dev@incubator.apache.org
> Subject: RE: [jira] Commented: (CXF-1143) Default CXF behavior of
> listingall available endpoints
>
>
>
> Hi,
>
> Let me validate that's what I saw when trying that rather than waste your
> time. I am using 2.0.3, but just moved to it on Friday - I may have seen
> that with 2.0.2 though ... will verify tonight what if the issue is still
> there.
>
>
> Willem2 wrote:
>>
>>
>> Hi,
>>
>> I don't think CXFServlet share the same Bus instance together.
>> I will look this issue later today .
>> BTW, which CXF are you using?
>>
>> Willem.
>>
>> -----Original Message-----
>> From: Adrian C [mailto:adrian.corcoran@gmail.com]
>> Sent: Tue 11/13/2007 0:08
>> To: cxf-dev@incubator.apache.org
>> Subject: Re: [jira] Commented: (CXF-1143) Default CXF behavior of
>> listingall available endpoints
>>
>>
>> If you have two servlets, they both displpay the same list of services:
>>
>> <servlet>
>> <servlet-name>CoreCXFServlet</servlet-name>
>> <display-name>Core CXF Servlet</display-name>
>>
>> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
>> <init-param>
>> <param-name>config-location</param-name>
>> <param-value>com/xxx/de/ws/core/services/ws.context.xml</param-value>
>> </init-param>
>> <load-on-startup>4</load-on-startup>
>> </servlet>
>>
>> <servlet>
>> <servlet-name>ExtCXFServlet</servlet-name>
>> <display-name>Extensions CXF Servlet</display-name>
>>
>> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
>> <init-param>
>> <param-name>config-location</param-name>
>> <param-value>com/xxx/de/ws/ext/services/ws.context.xml</param-value>
>> </init-param>
>> <load-on-startup>5</load-on-startup>
>> </servlet>
>>
>> I have't looked into this but I think its because they both use the same
>> bus, where as xfire used separate xfire instances for exache
>> XFireConfigurableServlet
>>
>>
>>
>> Glen Mazza-2 wrote:
>>>
>>> I don't think it is necessarily "missing" with CXF:
>>> http://www.jroller.com/gmazza/date/20071019#step7
>>>
>>> I would guess you just need to add a separate mapping in the web.xml to
>>> another servlet, and turn on the display for xxx and turn it off for
>>> yyy.
>>>
>>> Glen
>>>
>>> Am Montag, den 12.11.2007, 03:59 -0800 schrieb Adrian C:
>>>>
>>>> Hi, just saw this and its something that is applicable to some of the
>>>> work
>>>> that I am doing also. Perhaps one of the things that is missing here
>>>> and
>>>> was
>>>> something that you could do with xfire is to have different endpoints
>>>> available from different servlets - that way when you went to
>>>> http://my-host/cxf/xxx you could see one list of services and
>>>> http://my-host/cxf/yyy you could see another...
>>>>
>>>>
>>>> JIRA jira@apache.org wrote:
>>>> >
>>>> >
>>>> > [
>>>> >
>>>> https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
>>>> > ]
>>>> >
>>>> > Glen Mazza commented on CXF-1143:
>>>> > ---------------------------------
>>>> >
>>>> > Do you mean that http://my-host/cxf/ shows the WSDL? Is that the
>>>> problem,
>>>> > you want to suppress showing the WSDL, regardless of address, or you
>>>> just
>>>> > don't want to show it at that particular address? (i.e. the normal
>>>> > http://myhost/cxf/service?wsdl or whatever address would be OK for
>>>> you)?
>>>> >
>>>> >> Default CXF behavior of listing all available endpoints
>>>> >> -------------------------------------------------------
>>>> >>
>>>> >> Key: CXF-1143
>>>> >> URL: https://issues.apache.org/jira/browse/CXF-1143
>>>> >> Project: CXF
>>>> >> Issue Type: Improvement
>>>> >> Reporter: Tawfik Lachheb
>>>> >>
>>>> >> If I publish the cxf servlet as /cxf then going to
>>>> http://my-host/cxf/
>>>> >> lists all available endpoints.
>>>> >> This is something we don't want to have in our production
>>>> environment.
>>>> >> Is there a way to disable this?
>>>> >> Thanks
>>>> >
>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13708181
>> Sent from the cxf-dev mailing list archive at Nabble.com.
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13709780
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13729967
Sent from the cxf-dev mailing list archive at Nabble.com.
RE: [jira] Commented: (CXF-1143) Default CXF behavior of listingall available endpoints
Posted by "Jiang, Ning (Willem)" <Ni...@iona.com>.
Ok, there are some changes in CXFServlet 2.0.3(vote version).
So please let me know if here any issue with the new coming up 2.0.3.
Willem.
-----Original Message-----
From: Adrian C [mailto:adrian.corcoran@gmail.com]
Sent: Tue 11/13/2007 1:18
To: cxf-dev@incubator.apache.org
Subject: RE: [jira] Commented: (CXF-1143) Default CXF behavior of listingall available endpoints
Hi,
Let me validate that's what I saw when trying that rather than waste your
time. I am using 2.0.3, but just moved to it on Friday - I may have seen
that with 2.0.2 though ... will verify tonight what if the issue is still
there.
Willem2 wrote:
>
>
> Hi,
>
> I don't think CXFServlet share the same Bus instance together.
> I will look this issue later today .
> BTW, which CXF are you using?
>
> Willem.
>
> -----Original Message-----
> From: Adrian C [mailto:adrian.corcoran@gmail.com]
> Sent: Tue 11/13/2007 0:08
> To: cxf-dev@incubator.apache.org
> Subject: Re: [jira] Commented: (CXF-1143) Default CXF behavior of
> listingall available endpoints
>
>
> If you have two servlets, they both displpay the same list of services:
>
> <servlet>
> <servlet-name>CoreCXFServlet</servlet-name>
> <display-name>Core CXF Servlet</display-name>
>
> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
> <init-param>
> <param-name>config-location</param-name>
> <param-value>com/xxx/de/ws/core/services/ws.context.xml</param-value>
> </init-param>
> <load-on-startup>4</load-on-startup>
> </servlet>
>
> <servlet>
> <servlet-name>ExtCXFServlet</servlet-name>
> <display-name>Extensions CXF Servlet</display-name>
>
> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
> <init-param>
> <param-name>config-location</param-name>
> <param-value>com/xxx/de/ws/ext/services/ws.context.xml</param-value>
> </init-param>
> <load-on-startup>5</load-on-startup>
> </servlet>
>
> I have't looked into this but I think its because they both use the same
> bus, where as xfire used separate xfire instances for exache
> XFireConfigurableServlet
>
>
>
> Glen Mazza-2 wrote:
>>
>> I don't think it is necessarily "missing" with CXF:
>> http://www.jroller.com/gmazza/date/20071019#step7
>>
>> I would guess you just need to add a separate mapping in the web.xml to
>> another servlet, and turn on the display for xxx and turn it off for
>> yyy.
>>
>> Glen
>>
>> Am Montag, den 12.11.2007, 03:59 -0800 schrieb Adrian C:
>>>
>>> Hi, just saw this and its something that is applicable to some of the
>>> work
>>> that I am doing also. Perhaps one of the things that is missing here and
>>> was
>>> something that you could do with xfire is to have different endpoints
>>> available from different servlets - that way when you went to
>>> http://my-host/cxf/xxx you could see one list of services and
>>> http://my-host/cxf/yyy you could see another...
>>>
>>>
>>> JIRA jira@apache.org wrote:
>>> >
>>> >
>>> > [
>>> >
>>> https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
>>> > ]
>>> >
>>> > Glen Mazza commented on CXF-1143:
>>> > ---------------------------------
>>> >
>>> > Do you mean that http://my-host/cxf/ shows the WSDL? Is that the
>>> problem,
>>> > you want to suppress showing the WSDL, regardless of address, or you
>>> just
>>> > don't want to show it at that particular address? (i.e. the normal
>>> > http://myhost/cxf/service?wsdl or whatever address would be OK for
>>> you)?
>>> >
>>> >> Default CXF behavior of listing all available endpoints
>>> >> -------------------------------------------------------
>>> >>
>>> >> Key: CXF-1143
>>> >> URL: https://issues.apache.org/jira/browse/CXF-1143
>>> >> Project: CXF
>>> >> Issue Type: Improvement
>>> >> Reporter: Tawfik Lachheb
>>> >>
>>> >> If I publish the cxf servlet as /cxf then going to
>>> http://my-host/cxf/
>>> >> lists all available endpoints.
>>> >> This is something we don't want to have in our production
>>> environment.
>>> >> Is there a way to disable this?
>>> >> Thanks
>>> >
>>
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13708181
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13709780
Sent from the cxf-dev mailing list archive at Nabble.com.
RE: [jira] Commented: (CXF-1143) Default CXF behavior of listingall
available endpoints
Posted by Adrian C <ad...@gmail.com>.
Hi,
Let me validate that's what I saw when trying that rather than waste your
time. I am using 2.0.3, but just moved to it on Friday - I may have seen
that with 2.0.2 though ... will verify tonight what if the issue is still
there.
Willem2 wrote:
>
>
> Hi,
>
> I don't think CXFServlet share the same Bus instance together.
> I will look this issue later today .
> BTW, which CXF are you using?
>
> Willem.
>
> -----Original Message-----
> From: Adrian C [mailto:adrian.corcoran@gmail.com]
> Sent: Tue 11/13/2007 0:08
> To: cxf-dev@incubator.apache.org
> Subject: Re: [jira] Commented: (CXF-1143) Default CXF behavior of
> listingall available endpoints
>
>
> If you have two servlets, they both displpay the same list of services:
>
> <servlet>
> <servlet-name>CoreCXFServlet</servlet-name>
> <display-name>Core CXF Servlet</display-name>
>
> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
> <init-param>
> <param-name>config-location</param-name>
> <param-value>com/xxx/de/ws/core/services/ws.context.xml</param-value>
> </init-param>
> <load-on-startup>4</load-on-startup>
> </servlet>
>
> <servlet>
> <servlet-name>ExtCXFServlet</servlet-name>
> <display-name>Extensions CXF Servlet</display-name>
>
> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
> <init-param>
> <param-name>config-location</param-name>
> <param-value>com/xxx/de/ws/ext/services/ws.context.xml</param-value>
> </init-param>
> <load-on-startup>5</load-on-startup>
> </servlet>
>
> I have't looked into this but I think its because they both use the same
> bus, where as xfire used separate xfire instances for exache
> XFireConfigurableServlet
>
>
>
> Glen Mazza-2 wrote:
>>
>> I don't think it is necessarily "missing" with CXF:
>> http://www.jroller.com/gmazza/date/20071019#step7
>>
>> I would guess you just need to add a separate mapping in the web.xml to
>> another servlet, and turn on the display for xxx and turn it off for
>> yyy.
>>
>> Glen
>>
>> Am Montag, den 12.11.2007, 03:59 -0800 schrieb Adrian C:
>>>
>>> Hi, just saw this and its something that is applicable to some of the
>>> work
>>> that I am doing also. Perhaps one of the things that is missing here and
>>> was
>>> something that you could do with xfire is to have different endpoints
>>> available from different servlets - that way when you went to
>>> http://my-host/cxf/xxx you could see one list of services and
>>> http://my-host/cxf/yyy you could see another...
>>>
>>>
>>> JIRA jira@apache.org wrote:
>>> >
>>> >
>>> > [
>>> >
>>> https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
>>> > ]
>>> >
>>> > Glen Mazza commented on CXF-1143:
>>> > ---------------------------------
>>> >
>>> > Do you mean that http://my-host/cxf/ shows the WSDL? Is that the
>>> problem,
>>> > you want to suppress showing the WSDL, regardless of address, or you
>>> just
>>> > don't want to show it at that particular address? (i.e. the normal
>>> > http://myhost/cxf/service?wsdl or whatever address would be OK for
>>> you)?
>>> >
>>> >> Default CXF behavior of listing all available endpoints
>>> >> -------------------------------------------------------
>>> >>
>>> >> Key: CXF-1143
>>> >> URL: https://issues.apache.org/jira/browse/CXF-1143
>>> >> Project: CXF
>>> >> Issue Type: Improvement
>>> >> Reporter: Tawfik Lachheb
>>> >>
>>> >> If I publish the cxf servlet as /cxf then going to
>>> http://my-host/cxf/
>>> >> lists all available endpoints.
>>> >> This is something we don't want to have in our production
>>> environment.
>>> >> Is there a way to disable this?
>>> >> Thanks
>>> >
>>
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13708181
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13709780
Sent from the cxf-dev mailing list archive at Nabble.com.
RE: [jira] Commented: (CXF-1143) Default CXF behavior of listingall available endpoints
Posted by "Jiang, Ning (Willem)" <Ni...@iona.com>.
Hi,
I don't think CXFServlet share the same Bus instance together.
I will look this issue later today .
BTW, which CXF are you using?
Willem.
-----Original Message-----
From: Adrian C [mailto:adrian.corcoran@gmail.com]
Sent: Tue 11/13/2007 0:08
To: cxf-dev@incubator.apache.org
Subject: Re: [jira] Commented: (CXF-1143) Default CXF behavior of listingall available endpoints
If you have two servlets, they both displpay the same list of services:
<servlet>
<servlet-name>CoreCXFServlet</servlet-name>
<display-name>Core CXF Servlet</display-name>
<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
<init-param>
<param-name>config-location</param-name>
<param-value>com/xxx/de/ws/core/services/ws.context.xml</param-value>
</init-param>
<load-on-startup>4</load-on-startup>
</servlet>
<servlet>
<servlet-name>ExtCXFServlet</servlet-name>
<display-name>Extensions CXF Servlet</display-name>
<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
<init-param>
<param-name>config-location</param-name>
<param-value>com/xxx/de/ws/ext/services/ws.context.xml</param-value>
</init-param>
<load-on-startup>5</load-on-startup>
</servlet>
I have't looked into this but I think its because they both use the same
bus, where as xfire used separate xfire instances for exache
XFireConfigurableServlet
Glen Mazza-2 wrote:
>
> I don't think it is necessarily "missing" with CXF:
> http://www.jroller.com/gmazza/date/20071019#step7
>
> I would guess you just need to add a separate mapping in the web.xml to
> another servlet, and turn on the display for xxx and turn it off for
> yyy.
>
> Glen
>
> Am Montag, den 12.11.2007, 03:59 -0800 schrieb Adrian C:
>>
>> Hi, just saw this and its something that is applicable to some of the
>> work
>> that I am doing also. Perhaps one of the things that is missing here and
>> was
>> something that you could do with xfire is to have different endpoints
>> available from different servlets - that way when you went to
>> http://my-host/cxf/xxx you could see one list of services and
>> http://my-host/cxf/yyy you could see another...
>>
>>
>> JIRA jira@apache.org wrote:
>> >
>> >
>> > [
>> >
>> https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
>> > ]
>> >
>> > Glen Mazza commented on CXF-1143:
>> > ---------------------------------
>> >
>> > Do you mean that http://my-host/cxf/ shows the WSDL? Is that the
>> problem,
>> > you want to suppress showing the WSDL, regardless of address, or you
>> just
>> > don't want to show it at that particular address? (i.e. the normal
>> > http://myhost/cxf/service?wsdl or whatever address would be OK for
>> you)?
>> >
>> >> Default CXF behavior of listing all available endpoints
>> >> -------------------------------------------------------
>> >>
>> >> Key: CXF-1143
>> >> URL: https://issues.apache.org/jira/browse/CXF-1143
>> >> Project: CXF
>> >> Issue Type: Improvement
>> >> Reporter: Tawfik Lachheb
>> >>
>> >> If I publish the cxf servlet as /cxf then going to http://my-host/cxf/
>> >> lists all available endpoints.
>> >> This is something we don't want to have in our production environment.
>> >> Is there a way to disable this?
>> >> Thanks
>> >
>
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13708181
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: [jira] Commented: (CXF-1143) Default CXF behavior of listing
all available endpoints
Posted by Adrian C <ad...@gmail.com>.
If you have two servlets, they both have the same list of services.
Glen Mazza-2 wrote:
>
> I don't think it is necessarily "missing" with CXF:
> http://www.jroller.com/gmazza/date/20071019#step7
>
> I would guess you just need to add a separate mapping in the web.xml to
> another servlet, and turn on the display for xxx and turn it off for
> yyy.
>
> Glen
>
> Am Montag, den 12.11.2007, 03:59 -0800 schrieb Adrian C:
>>
>> Hi, just saw this and its something that is applicable to some of the
>> work
>> that I am doing also. Perhaps one of the things that is missing here and
>> was
>> something that you could do with xfire is to have different endpoints
>> available from different servlets - that way when you went to
>> http://my-host/cxf/xxx you could see one list of services and
>> http://my-host/cxf/yyy you could see another...
>>
>>
>> JIRA jira@apache.org wrote:
>> >
>> >
>> > [
>> >
>> https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
>> > ]
>> >
>> > Glen Mazza commented on CXF-1143:
>> > ---------------------------------
>> >
>> > Do you mean that http://my-host/cxf/ shows the WSDL? Is that the
>> problem,
>> > you want to suppress showing the WSDL, regardless of address, or you
>> just
>> > don't want to show it at that particular address? (i.e. the normal
>> > http://myhost/cxf/service?wsdl or whatever address would be OK for
>> you)?
>> >
>> >> Default CXF behavior of listing all available endpoints
>> >> -------------------------------------------------------
>> >>
>> >> Key: CXF-1143
>> >> URL: https://issues.apache.org/jira/browse/CXF-1143
>> >> Project: CXF
>> >> Issue Type: Improvement
>> >> Reporter: Tawfik Lachheb
>> >>
>> >> If I publish the cxf servlet as /cxf then going to http://my-host/cxf/
>> >> lists all available endpoints.
>> >> This is something we don't want to have in our production environment.
>> >> Is there a way to disable this?
>> >> Thanks
>> >
>
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13708181
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: [jira] Commented: (CXF-1143) Default CXF behavior of listing
all available endpoints
Posted by Adrian C <ad...@gmail.com>.
If you have two servlets, they both displpay the same list of services:
<servlet>
<servlet-name>CoreCXFServlet</servlet-name>
<display-name>Core CXF Servlet</display-name>
<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
<init-param>
<param-name>config-location</param-name>
<param-value>com/xxx/de/ws/core/services/ws.context.xml</param-value>
</init-param>
<load-on-startup>4</load-on-startup>
</servlet>
<servlet>
<servlet-name>ExtCXFServlet</servlet-name>
<display-name>Extensions CXF Servlet</display-name>
<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
<init-param>
<param-name>config-location</param-name>
<param-value>com/xxx/de/ws/ext/services/ws.context.xml</param-value>
</init-param>
<load-on-startup>5</load-on-startup>
</servlet>
I have't looked into this but I think its because they both use the same
bus, where as xfire used separate xfire instances for exache
XFireConfigurableServlet
Glen Mazza-2 wrote:
>
> I don't think it is necessarily "missing" with CXF:
> http://www.jroller.com/gmazza/date/20071019#step7
>
> I would guess you just need to add a separate mapping in the web.xml to
> another servlet, and turn on the display for xxx and turn it off for
> yyy.
>
> Glen
>
> Am Montag, den 12.11.2007, 03:59 -0800 schrieb Adrian C:
>>
>> Hi, just saw this and its something that is applicable to some of the
>> work
>> that I am doing also. Perhaps one of the things that is missing here and
>> was
>> something that you could do with xfire is to have different endpoints
>> available from different servlets - that way when you went to
>> http://my-host/cxf/xxx you could see one list of services and
>> http://my-host/cxf/yyy you could see another...
>>
>>
>> JIRA jira@apache.org wrote:
>> >
>> >
>> > [
>> >
>> https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
>> > ]
>> >
>> > Glen Mazza commented on CXF-1143:
>> > ---------------------------------
>> >
>> > Do you mean that http://my-host/cxf/ shows the WSDL? Is that the
>> problem,
>> > you want to suppress showing the WSDL, regardless of address, or you
>> just
>> > don't want to show it at that particular address? (i.e. the normal
>> > http://myhost/cxf/service?wsdl or whatever address would be OK for
>> you)?
>> >
>> >> Default CXF behavior of listing all available endpoints
>> >> -------------------------------------------------------
>> >>
>> >> Key: CXF-1143
>> >> URL: https://issues.apache.org/jira/browse/CXF-1143
>> >> Project: CXF
>> >> Issue Type: Improvement
>> >> Reporter: Tawfik Lachheb
>> >>
>> >> If I publish the cxf servlet as /cxf then going to http://my-host/cxf/
>> >> lists all available endpoints.
>> >> This is something we don't want to have in our production environment.
>> >> Is there a way to disable this?
>> >> Thanks
>> >
>
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A--jira--Commented%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing%09all-available-endpoints-tf4791360.html#a13708181
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: [jira] Commented: (CXF-1143) Default CXF behavior of listing all
available endpoints
Posted by Glen Mazza <gl...@verizon.net>.
I don't think it is necessarily "missing" with CXF:
http://www.jroller.com/gmazza/date/20071019#step7
I would guess you just need to add a separate mapping in the web.xml to
another servlet, and turn on the display for xxx and turn it off for
yyy.
Glen
Am Montag, den 12.11.2007, 03:59 -0800 schrieb Adrian C:
>
> Hi, just saw this and its something that is applicable to some of the work
> that I am doing also. Perhaps one of the things that is missing here and was
> something that you could do with xfire is to have different endpoints
> available from different servlets - that way when you went to
> http://my-host/cxf/xxx you could see one list of services and
> http://my-host/cxf/yyy you could see another...
>
>
> JIRA jira@apache.org wrote:
> >
> >
> > [
> > https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
> > ]
> >
> > Glen Mazza commented on CXF-1143:
> > ---------------------------------
> >
> > Do you mean that http://my-host/cxf/ shows the WSDL? Is that the problem,
> > you want to suppress showing the WSDL, regardless of address, or you just
> > don't want to show it at that particular address? (i.e. the normal
> > http://myhost/cxf/service?wsdl or whatever address would be OK for you)?
> >
> >> Default CXF behavior of listing all available endpoints
> >> -------------------------------------------------------
> >>
> >> Key: CXF-1143
> >> URL: https://issues.apache.org/jira/browse/CXF-1143
> >> Project: CXF
> >> Issue Type: Improvement
> >> Reporter: Tawfik Lachheb
> >>
> >> If I publish the cxf servlet as /cxf then going to http://my-host/cxf/
> >> lists all available endpoints.
> >> This is something we don't want to have in our production environment.
> >> Is there a way to disable this?
> >> Thanks
> >
Re: [jira] Commented: (CXF-1143) Default CXF behavior of listing
all available endpoints
Posted by Adrian C <ad...@gmail.com>.
Hi, just saw this and its something that is applicable to some of the work
that I am doing also. Perhaps one of the things that is missing here and was
something that you could do with xfire is to have different endpoints
available from different servlets - that way when you went to
http://my-host/cxf/xxx you could see one list of services and
http://my-host/cxf/yyy you could see another...
JIRA jira@apache.org wrote:
>
>
> [
> https://issues.apache.org/jira/browse/CXF-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538131
> ]
>
> Glen Mazza commented on CXF-1143:
> ---------------------------------
>
> Do you mean that http://my-host/cxf/ shows the WSDL? Is that the problem,
> you want to suppress showing the WSDL, regardless of address, or you just
> don't want to show it at that particular address? (i.e. the normal
> http://myhost/cxf/service?wsdl or whatever address would be OK for you)?
>
>> Default CXF behavior of listing all available endpoints
>> -------------------------------------------------------
>>
>> Key: CXF-1143
>> URL: https://issues.apache.org/jira/browse/CXF-1143
>> Project: CXF
>> Issue Type: Improvement
>> Reporter: Tawfik Lachheb
>>
>> If I publish the cxf servlet as /cxf then going to http://my-host/cxf/
>> lists all available endpoints.
>> This is something we don't want to have in our production environment.
>> Is there a way to disable this?
>> Thanks
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
>
--
View this message in context: http://www.nabble.com/Created%3A-%28CXF-1143%29-Default-CXF-behavior-of-listing-all-available-endpoints-tf4698264.html#a13704364
Sent from the cxf-issues mailing list archive at Nabble.com.