You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "benson margulies (JIRA)" <ji...@apache.org> on 2007/10/13 22:47:50 UTC

[jira] Created: (CXF-1110) Adding DefaultHandler to handler list for jetty disables all service endpoints.

Adding DefaultHandler to handler list for jetty disables all service endpoints.
-------------------------------------------------------------------------------

                 Key: CXF-1110
                 URL: https://issues.apache.org/jira/browse/CXF-1110
             Project: CXF
          Issue Type: Bug
          Components: Configuration
    Affects Versions: 2.0.2
            Reporter: benson margulies


I load this set of beans along with a JAX-WS endpoint definition. If I comment the DefaultHandler in, I can't reach my handler. if I comment it out, I can.

After some thought, it seems to me that this should work, unless there is something wrong with the order in which the handlers end up arranged. The DefaultHandler is only supposed to get into the act if nothing else handles the request. Could it be that whatever Context that CXF is putting into the bus itself is ending up last instead of first? Should there be an explicit XML element in the namespace to specify where the CXF endpoint ends up?


<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:sec="http://cxf.apache.org/configuration/security"
 xmlns:http="http://cxf.apache.org/transports/http/configuration"
 xmlns:httpj="http://cxf.apache.org/transports/http-jetty/configuration" xmlns:jaxws="http://java.sun.com/xml/ns/jaxws"
 xsi:schemaLocation="http://cxf.apache.org/configuration/security
          http://cxf.apache.org/schemas/configuration/security.xsd
            http://cxf.apache.org/transports/http/configuration
            http://cxf.apache.org/schemas/configuration/http-conf.xsd
            http://cxf.apache.org/transports/http-jetty/configuration
            http://cxf.apache.org/schemas/configuration/http-jetty.xsd
            http://www.springframework.org/schema/beans
            http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">

 <httpj:engine-factory bus="cxf">
  <httpj:engine port="8808">
   <httpj:handlers>
    <bean class="org.mortbay.jetty.handler.ContextHandler">
     <property name="contextPath" value="/${staticResourceBase}" />
     <property name="handler">
      <bean class="org.mortbay.jetty.handler.ResourceHandler">
       <property name="baseResource">
        <bean class="org.mortbay.resource.FileResource">
         <constructor-arg value="${staticResourceURL}" />
        </bean>
        </property>
      </bean>
     </property>
    </bean>
    <!-- 
    <bean class="org.mortbay.jetty.handler.DefaultHandler"/>
    -->
   </httpj:handlers>
  </httpj:engine>
 </httpj:engine-factory>
</beans>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CXF-1110) Adding DefaultHandler to handler list for jetty disables all service endpoints.

Posted by "willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

willem Jiang resolved CXF-1110.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3

This should be fixed in the SVN repository.

> Adding DefaultHandler to handler list for jetty disables all service endpoints.
> -------------------------------------------------------------------------------
>
>                 Key: CXF-1110
>                 URL: https://issues.apache.org/jira/browse/CXF-1110
>             Project: CXF
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 2.0.2
>            Reporter: benson margulies
>            Assignee: willem Jiang
>             Fix For: 2.0.3
>
>
> I load this set of beans along with a JAX-WS endpoint definition. If I comment the DefaultHandler in, I can't reach my handler. if I comment it out, I can.
> After some thought, it seems to me that this should work, unless there is something wrong with the order in which the handlers end up arranged. The DefaultHandler is only supposed to get into the act if nothing else handles the request. Could it be that whatever Context that CXF is putting into the bus itself is ending up last instead of first? Should there be an explicit XML element in the namespace to specify where the CXF endpoint ends up?
> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xmlns:sec="http://cxf.apache.org/configuration/security"
>  xmlns:http="http://cxf.apache.org/transports/http/configuration"
>  xmlns:httpj="http://cxf.apache.org/transports/http-jetty/configuration" xmlns:jaxws="http://java.sun.com/xml/ns/jaxws"
>  xsi:schemaLocation="http://cxf.apache.org/configuration/security
>           http://cxf.apache.org/schemas/configuration/security.xsd
>             http://cxf.apache.org/transports/http/configuration
>             http://cxf.apache.org/schemas/configuration/http-conf.xsd
>             http://cxf.apache.org/transports/http-jetty/configuration
>             http://cxf.apache.org/schemas/configuration/http-jetty.xsd
>             http://www.springframework.org/schema/beans
>             http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
>  <httpj:engine-factory bus="cxf">
>   <httpj:engine port="8808">
>    <httpj:handlers>
>     <bean class="org.mortbay.jetty.handler.ContextHandler">
>      <property name="contextPath" value="/${staticResourceBase}" />
>      <property name="handler">
>       <bean class="org.mortbay.jetty.handler.ResourceHandler">
>        <property name="baseResource">
>         <bean class="org.mortbay.resource.FileResource">
>          <constructor-arg value="${staticResourceURL}" />
>         </bean>
>         </property>
>       </bean>
>      </property>
>     </bean>
>     <!-- 
>     <bean class="org.mortbay.jetty.handler.DefaultHandler"/>
>     -->
>    </httpj:handlers>
>   </httpj:engine>
>  </httpj:engine-factory>
> </beans>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (CXF-1110) Adding DefaultHandler to handler list for jetty disables all service endpoints.

Posted by "willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

willem Jiang reassigned CXF-1110:
---------------------------------

    Assignee: willem Jiang

> Adding DefaultHandler to handler list for jetty disables all service endpoints.
> -------------------------------------------------------------------------------
>
>                 Key: CXF-1110
>                 URL: https://issues.apache.org/jira/browse/CXF-1110
>             Project: CXF
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 2.0.2
>            Reporter: benson margulies
>            Assignee: willem Jiang
>
> I load this set of beans along with a JAX-WS endpoint definition. If I comment the DefaultHandler in, I can't reach my handler. if I comment it out, I can.
> After some thought, it seems to me that this should work, unless there is something wrong with the order in which the handlers end up arranged. The DefaultHandler is only supposed to get into the act if nothing else handles the request. Could it be that whatever Context that CXF is putting into the bus itself is ending up last instead of first? Should there be an explicit XML element in the namespace to specify where the CXF endpoint ends up?
> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xmlns:sec="http://cxf.apache.org/configuration/security"
>  xmlns:http="http://cxf.apache.org/transports/http/configuration"
>  xmlns:httpj="http://cxf.apache.org/transports/http-jetty/configuration" xmlns:jaxws="http://java.sun.com/xml/ns/jaxws"
>  xsi:schemaLocation="http://cxf.apache.org/configuration/security
>           http://cxf.apache.org/schemas/configuration/security.xsd
>             http://cxf.apache.org/transports/http/configuration
>             http://cxf.apache.org/schemas/configuration/http-conf.xsd
>             http://cxf.apache.org/transports/http-jetty/configuration
>             http://cxf.apache.org/schemas/configuration/http-jetty.xsd
>             http://www.springframework.org/schema/beans
>             http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
>  <httpj:engine-factory bus="cxf">
>   <httpj:engine port="8808">
>    <httpj:handlers>
>     <bean class="org.mortbay.jetty.handler.ContextHandler">
>      <property name="contextPath" value="/${staticResourceBase}" />
>      <property name="handler">
>       <bean class="org.mortbay.jetty.handler.ResourceHandler">
>        <property name="baseResource">
>         <bean class="org.mortbay.resource.FileResource">
>          <constructor-arg value="${staticResourceURL}" />
>         </bean>
>         </property>
>       </bean>
>      </property>
>     </bean>
>     <!-- 
>     <bean class="org.mortbay.jetty.handler.DefaultHandler"/>
>     -->
>    </httpj:handlers>
>   </httpj:engine>
>  </httpj:engine-factory>
> </beans>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.