Return-Path: Delivered-To: apmail-incubator-cxf-issues-archive@locus.apache.org Received: (qmail 63969 invoked from network); 18 Jan 2007 17:00:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Jan 2007 17:00:51 -0000 Received: (qmail 65643 invoked by uid 500); 18 Jan 2007 17:00:57 -0000 Delivered-To: apmail-incubator-cxf-issues-archive@incubator.apache.org Received: (qmail 65626 invoked by uid 500); 18 Jan 2007 17:00:57 -0000 Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-issues@incubator.apache.org Received: (qmail 65611 invoked by uid 99); 18 Jan 2007 17:00:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2007 09:00:57 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2007 09:00:50 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0EB807141D1 for ; Thu, 18 Jan 2007 09:00:30 -0800 (PST) Message-ID: <25274060.1169139630039.JavaMail.jira@brutus> Date: Thu, 18 Jan 2007 09:00:30 -0800 (PST) From: "Daniel Kulp (JIRA)" To: cxf-issues@incubator.apache.org Subject: [jira] Commented: (CXF-342) Servlet transport should be independent of the JAX-WS frontend In-Reply-To: <15954474.1167748527731.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465809 ] Daniel Kulp commented on CXF-342: --------------------------------- How does using reflection change the fact that it's JAX-WS only or open it up to other frontends? The fact is that Endpoint.publish(...) is JAX-WS specific. Whether it's called via reflection or directly doesn't change the fact that its JAX-WS specific and belongs in the JAX-WS layer. To move this out of JAX-WS, the "endpoint publishing" stuff needs to be abstracted out into an interface that the frontends can implement and the servlet would have to load all of those found on the classpath (spring loading like everything else). The tag in the cxf-servlet.xml file would need to be extended somehow to provide implementation details as to which frontend will handle it. Better would be to make it based on the namespace or something. Exmaple: > Servlet transport should be independent of the JAX-WS frontend > -------------------------------------------------------------- > > Key: CXF-342 > URL: https://issues.apache.org/jira/browse/CXF-342 > Project: CXF > Issue Type: Improvement > Components: Transports > Reporter: Eoghan Glynn > Assigned To: willem Jiang > > The servlet transport is implemented as part of the JAX-WS frontend, but the only real dependency on JAX-WS is the hardcoding of the instantiation of org.apache.cxf.jaxws.EndpointImpl and the Endpoint.publish() call. > This should be done via reflection instead, with the class to instantiate and the publish method configured in the cxf-servlet.xml. > That way the servlet transport could be used with any front-end (as opposed to be being limited to JAX-WS) and the code could be moved out of the rt-frontend-jaxws module and into the rt-transpots-http module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira