From cxf-issues-returnosmith@example.org Fri Mar 02 03:07:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 14787 invoked from network); 2 Mar 2007 03:07:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 03:07:12 -0000 Received: (qmail 53041 invoked by uid 500); 2 Mar 2007 03:07:20 -0000 Delivered-To: osmith@example.org Received: (qmail 53019 invoked by uid 500); 2 Mar 2007 03:07:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 53002 invoked by uid 99); 2 Mar 2007 03:07:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 19:07:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 19:07:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 29E557142E4 for <osmith@example.org>; Thu, 1 Mar 2007 19:06:51 -0800 (PST) Message-ID: <8014869.1172804811169.JavaMail.jira@brutus> Date: Thu, 1 Mar 2007 19:06:51 -0800 (PST) From: "Jervis Liu (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Created: (CXF-442) Support the injection of javax.xml.ws.WebServiceContext MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Support the injection of javax.xml.ws.WebServiceContext ------------------------------------------------------- Key: CXF-442 URL: https://issues.apache.org/jira/browse/CXF-442 Project: CXF Issue Type: Sub-task Components: JAX-WS Runtime Reporter: Jervis Liu The injection of javax.xml.ws.WebServiceContext. JSR-109, section 6.2.4: A JAX-WS based container must carry out any injections (if any) requested by the handler, typically via the @Resource annotation (see section 2.2 of JSR-250 Common Annotations for Java Platform specification). A JAX-WS handler should use the javax.xml.ws.WebServiceContext, which is an injectable resource, to access message context and security information relative to the request being served. A unique Handler instance must be provided for each Port component declared in the deployment descriptor or annotated by javax.jws.WebService or javax.xml.ws.WebServiceProvider annotations. CXF does support the injection of WebServiceContext in endpoint but not in handlers yet. I presume a code snippet that has the injection of WebServiceContext would look like below: public class MyHandler implements SOAPHandler<SOAPMessageContext> { .... @Resource WebServiceContext context ... } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Fri Mar 02 03:07:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 14788 invoked from network); 2 Mar 2007 03:07:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 03:07:12 -0000 Received: (qmail 53052 invoked by uid 500); 2 Mar 2007 03:07:20 -0000 Delivered-To: osmith@example.org Received: (qmail 53021 invoked by uid 500); 2 Mar 2007 03:07:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 53000 invoked by uid 99); 2 Mar 2007 03:07:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 19:07:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 19:07:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id E0F067142DF for <osmith@example.org>; Thu, 1 Mar 2007 19:06:50 -0800 (PST) Message-ID: <32262714.1172804810918.JavaMail.jira@brutus> Date: Thu, 1 Mar 2007 19:06:50 -0800 (PST) From: "Jervis Liu (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Created: (CXF-441) Support the injection of context and environment entries MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Support the injection of context and environment entries --------------------------------------------------------- Key: CXF-441 URL: https://issues.apache.org/jira/browse/CXF-441 Project: CXF Issue Type: Sub-task Components: JAX-WS Runtime Reporter: Jervis Liu Assigned To: Jervis Liu When CXF is deployed into a servlet container, the component's context and environment entries are injected into handlers. JSR-109, section 6.2.3: With JAX-WS, the handler allows for resources to be injected, typically by using the @Resource annotation. So a Handler.handle<action>() method may access the component's context and environment entries by using any resources that were injected. It can also use JNDI lookup of the "java:comp/env" context and accessing the env-entry-names defined in the deployment descriptor by performing a JNDI lookup. See chapter 15 of the Enterprise JavaBeans specification - Enterprise JavaBeans Core Contracts and Requirements for details. The container may throw a java.lang.IllegalStateException if the environment is accessed from any other Handler method and the environment is not available. The element init-params in the deployment descriptors is no longer used for JAX-WS based container. If needed, the developer should use the environment entry elements (<env-entry>) declared in the application component's deployment descriptor for this purpose. These can be injected into the handler using the @Resource annotation or looked up using JNDI. An example of this use case: http://forums.java.net/jive/thread.jspa?messageID=131230&tstart=0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Fri Mar 02 03:19:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 17516 invoked from network); 2 Mar 2007 03:19:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 03:19:12 -0000 Received: (qmail 72387 invoked by uid 500); 2 Mar 2007 03:19:20 -0000 Delivered-To: osmith@example.org Received: (qmail 72373 invoked by uid 500); 2 Mar 2007 03:19:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 72350 invoked by uid 99); 2 Mar 2007 03:19:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 19:19:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 19:19:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id E29667142E0 for <osmith@example.org>; Thu, 1 Mar 2007 19:18:50 -0800 (PST) Message-ID: <14494064.1172805530925.JavaMail.jira@brutus> Date: Thu, 1 Mar 2007 19:18:50 -0800 (PST) From: "Freeman Fang (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Assigned: (CXF-443) LocaterService test doesn't work after jaxb upgrade In-Reply-To: <13571677.1172805530865.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-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-443: -------------------------------- Assignee: Freeman Fang > LocaterService test doesn't work after jaxb upgrade > --------------------------------------------------- > > Key: CXF-443 > URL: https://issues.apache.org/jira/browse/CXF-443 > Project: CXF > Issue Type: Test > Reporter: Freeman Fang > Assigned To: Freeman Fang > > LocatorClientServerTest doesn't work after JAXB upgrade, currently this test was disabled in parent/pom.xml. Since locator.wsdl include element ref, I think this scenaria should be supported in CXF > <xs:element name="queryEndpoints"> > <xs:annotation> > <xs:documentation>Input message element for &quot;queryEndpoints&quot; operation.</xs:documentation> > </xs:annotation> > <xs:complexType> > <xs:sequence> > <xs:element ref="query:select"/> > </xs:sequence> > </xs:complexType> > </xs:element> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Fri Mar 02 03:19:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 17518 invoked from network); 2 Mar 2007 03:19:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 03:19:12 -0000 Received: (qmail 72378 invoked by uid 500); 2 Mar 2007 03:19:20 -0000 Delivered-To: osmith@example.org Received: (qmail 72371 invoked by uid 500); 2 Mar 2007 03:19:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 72349 invoked by uid 99); 2 Mar 2007 03:19:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 19:19:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 19:19:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D40DF7142DF for <osmith@example.org>; Thu, 1 Mar 2007 19:18:50 -0800 (PST) Message-ID: <13571677.1172805530865.JavaMail.jira@brutus> Date: Thu, 1 Mar 2007 19:18:50 -0800 (PST) From: "Freeman Fang (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Created: (CXF-443) LocaterService test doesn't work after jaxb upgrade MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org LocaterService test doesn't work after jaxb upgrade --------------------------------------------------- Key: CXF-443 URL: https://issues.apache.org/jira/browse/CXF-443 Project: CXF Issue Type: Test Reporter: Freeman Fang LocatorClientServerTest doesn't work after JAXB upgrade, currently this test was disabled in parent/pom.xml. Since locator.wsdl include element ref, I think this scenaria should be supported in CXF <xs:element name="queryEndpoints"> <xs:annotation> <xs:documentation>Input message element for &quot;queryEndpoints&quot; operation.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element ref="query:select"/> </xs:sequence> </xs:complexType> </xs:element> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Fri Mar 02 07:02:22 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 59158 invoked from network); 2 Mar 2007 07:02:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 07:02:19 -0000 Received: (qmail 95460 invoked by uid 500); 2 Mar 2007 07:02:28 -0000 Delivered-To: osmith@example.org Received: (qmail 95449 invoked by uid 500); 2 Mar 2007 07:02:28 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 95440 invoked by uid 99); 2 Mar 2007 07:02:27 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 23:02:27 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 23:02:18 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 250EF7142E2 for <osmith@example.org>; Thu, 1 Mar 2007 23:01:56 -0800 (PST) Message-ID: <15741713.1172818916149.JavaMail.jira@brutus> Date: Thu, 1 Mar 2007 23:01:56 -0800 (PST) From: "Freeman Fang (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Resolved: (CXF-443) LocaterService test doesn't work after jaxb upgrade In-Reply-To: <13571677.1172805530865.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-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-443. ------------------------------ Resolution: Fixed > LocaterService test doesn't work after jaxb upgrade > --------------------------------------------------- > > Key: CXF-443 > URL: https://issues.apache.org/jira/browse/CXF-443 > Project: CXF > Issue Type: Test > Reporter: Freeman Fang > Assigned To: Freeman Fang > > LocatorClientServerTest doesn't work after JAXB upgrade, currently this test was disabled in parent/pom.xml. Since locator.wsdl include element ref, I think this scenaria should be supported in CXF > <xs:element name="queryEndpoints"> > <xs:annotation> > <xs:documentation>Input message element for &quot;queryEndpoints&quot; operation.</xs:documentation> > </xs:annotation> > <xs:complexType> > <xs:sequence> > <xs:element ref="query:select"/> > </xs:sequence> > </xs:complexType> > </xs:element> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Fri Mar 02 07:02:22 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 59257 invoked from network); 2 Mar 2007 07:02:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 07:02:22 -0000 Received: (qmail 95554 invoked by uid 500); 2 Mar 2007 07:02:30 -0000 Delivered-To: osmith@example.org Received: (qmail 95544 invoked by uid 500); 2 Mar 2007 07:02:30 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 95535 invoked by uid 99); 2 Mar 2007 07:02:30 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 23:02:30 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Mar 2007 23:02:21 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 252497142E1 for <osmith@example.org>; Thu, 1 Mar 2007 23:02:00 -0800 (PST) Message-ID: <24316256.1172818920149.JavaMail.jira@brutus> Date: Thu, 1 Mar 2007 23:02:00 -0800 (PST) From: "maomaode (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Assigned: (CXF-308) search/find the plugins automatically In-Reply-To: <1106688.1166162901084.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-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] maomaode reassigned CXF-308: ---------------------------- Assignee: maomaode > search/find the plugins automatically > ------------------------------------- > > Key: CXF-308 > URL: https://issues.apache.org/jira/browse/CXF-308 > Project: CXF > Issue Type: Sub-task > Components: Tooling > Affects Versions: 2.0-RC > Reporter: maomaode > Assigned To: maomaode > Fix For: 2.0-RC > > > Plugin load should find/search the plugins automatically , and we also need to update the commandDocument to include the plugins' name , when user want to print the usage. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Fri Mar 02 11:03:13 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 47967 invoked from network); 2 Mar 2007 11:03:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 11:03:13 -0000 Received: (qmail 73320 invoked by uid 500); 2 Mar 2007 11:03:21 -0000 Delivered-To: osmith@example.org Received: (qmail 73278 invoked by uid 500); 2 Mar 2007 11:03:21 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 73222 invoked by uid 99); 2 Mar 2007 11:03:21 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 03:03:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 03:03:10 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id CD8587142EE for <osmith@example.org>; Fri, 2 Mar 2007 03:02:50 -0800 (PST) Message-ID: <31297078.1172833370839.JavaMail.jira@brutus> Date: Fri, 2 Mar 2007 03:02:50 -0800 (PST) From: "maomaode (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Resolved: (CXF-308) search/find the plugins automatically In-Reply-To: <1106688.1166162901084.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-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] maomaode resolved CXF-308. -------------------------- Resolution: Fixed > search/find the plugins automatically > ------------------------------------- > > Key: CXF-308 > URL: https://issues.apache.org/jira/browse/CXF-308 > Project: CXF > Issue Type: Sub-task > Components: Tooling > Affects Versions: 2.0-RC > Reporter: maomaode > Assigned To: maomaode > Fix For: 2.0-RC > > > Plugin load should find/search the plugins automatically , and we also need to update the commandDocument to include the plugins' name , when user want to print the usage. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Fri Mar 02 22:16:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 85742 invoked from network); 2 Mar 2007 22:16:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 22:16:12 -0000 Received: (qmail 68881 invoked by uid 500); 2 Mar 2007 22:16:20 -0000 Delivered-To: osmith@example.org Received: (qmail 68867 invoked by uid 500); 2 Mar 2007 22:16:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 68830 invoked by uid 99); 2 Mar 2007 22:16:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 14:16:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 14:16:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D4A27714325 for <osmith@example.org>; Fri, 2 Mar 2007 14:15:50 -0800 (PST) Message-ID: <13312517.1172873750868.JavaMail.jira@brutus> Date: Fri, 2 Mar 2007 14:15:50 -0800 (PST) From: "Jarek Gawor (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Created: (CXF-444) Problem with services initialized without WSDL file MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Problem with services initialized without WSDL file --------------------------------------------------- Key: CXF-444 URL: https://issues.apache.org/jira/browse/CXF-444 Project: CXF Issue Type: Bug Reporter: Jarek Gawor When a service is initialized from an annotated class, the service returns a response that the client does not deserialize properly. I'm attaching a test case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Fri Mar 02 22:21:17 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 88170 invoked from network); 2 Mar 2007 22:21:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Mar 2007 22:21:15 -0000 Received: (qmail 78065 invoked by uid 500); 2 Mar 2007 22:21:20 -0000 Delivered-To: osmith@example.org Received: (qmail 78044 invoked by uid 500); 2 Mar 2007 22:21:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 78002 invoked by uid 99); 2 Mar 2007 22:21:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 14:21:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 14:21:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 542F371432A for <osmith@example.org>; Fri, 2 Mar 2007 14:20:51 -0800 (PST) Message-ID: <33363955.1172874051342.JavaMail.jira@brutus> Date: Fri, 2 Mar 2007 14:20:51 -0800 (PST) From: "Jarek Gawor (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Updated: (CXF-444) Problem with services initialized without WSDL file In-Reply-To: <13312517.1172873750868.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-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated CXF-444: ---------------------------- Attachment: CXF-444.patch If the following is changed (in ServerGreeterNoWsdl.java) from: Object implementor = new GreeterImplNoWsdl(); to: Object implementor = new GreeterImpl(); the test passes. The GreeterImplNoWsdl uses a GreeterNoWsdl.java SEI that is exactly like the generated class but without the asynch methods and without the wsdl= attribute of the WebService annotation. > Problem with services initialized without WSDL file > --------------------------------------------------- > > Key: CXF-444 > URL: https://issues.apache.org/jira/browse/CXF-444 > Project: CXF > Issue Type: Bug > Reporter: Jarek Gawor > Attachments: CXF-444.patch > > > When a service is initialized from an annotated class, the service returns a response that the client does not deserialize properly. I'm attaching a test case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 02:16:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 8544 invoked from network); 5 Mar 2007 02:16:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 02:16:12 -0000 Received: (qmail 76858 invoked by uid 500); 5 Mar 2007 02:16:20 -0000 Delivered-To: osmith@example.org Received: (qmail 76809 invoked by uid 500); 5 Mar 2007 02:16:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 76799 invoked by uid 99); 5 Mar 2007 02:16:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 18:16:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 18:16:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D4B2B714336 for <osmith@example.org>; Sun, 4 Mar 2007 18:15:50 -0800 (PST) Message-ID: <12833212.1173060950868.JavaMail.jira@brutus> Date: Sun, 4 Mar 2007 18:15:50 -0800 (PST) From: "Fred Dushin (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Created: (CXF-445) Accessing Connection-based info from the transport MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Accessing Connection-based info from the transport -------------------------------------------------- Key: CXF-445 URL: https://issues.apache.org/jira/browse/CXF-445 Project: CXF Issue Type: Improvement Components: Transports Affects Versions: 2.0-RC Reporter: Fred Dushin Fix For: 2.0-RC Original post to cxf-dev mailinglist. Patch to follow: I'd like to get access to some connection-based information from the transport -- in particular, properties relating to any security context established at the transport (e.g., via an SSL handshake, or via a GSS-Accept) -- Primarily I'm thinking about the server-side of an invocation, though I suspect there may be client-side requirements, as well, though at present they are not as pressing for me. (They may be later). In any event, I've found that the transport is not populating the Message with any of the information I need, so I'd like to propose what I think should be a simple solution. First, I understand the fact that there are potentially many different transport implementations, even perhaps for the same protocols. So in some cases, this information may not be accessible by the transport, which is unfortunate (and perhaps motivation for not using the transport all together, depending on the business requirements). So the solution should allow for the possibility that some transports can't provide the needed info, so that consumers of the information can code defensively in these situations (throw an exception, log a warning, whatever). I can see how the transport destination implementations are instantiating the Message structures, which in turn get passed to the various interceptors (again, talking about the server-side here). So I'd like the transports, as the divine creators of Messages, to populate said messages with the contextual information I need. The question then becomes, what should this information look like, and how should it be keyed on the Message? We have several alternatives, which I'd like suggestions on before submitting a patch. First, I assume for purely organizational purposes we don't want a *huge* collection of tags on the Message. Not that it matters much (the Message is currently implemented as a HashMap, so adding a lot of data should not have an impact on lookup), but perhaps for purely aestheic reasons, it would be better to aggregate this information in some comprehensible manner. Going on that assumption, we have some options. We could define a type or collection thereof, each of which has a collection of accessors (and mutators, for the benefit of our transports), which define which data is available, where the types stowed on these structs are common, well-known, and guaranteed likely-to-exist types, e.g., class/interface TLSTransportInfo { java.security.cert.Certificate[] getPeerCertificateChain() ... } I started to do this, but the LISP programmer in me said "there has to be a better way". (I have an innate repulsion to vacuous code, but I'm old-fashioned that way :) So I turned to our good friend java.util.Map for inspiration (who needs types when you have a cons!). Why not define leverage a Map<String, Object>, and define a contract for what the structure of the map needs to be -- what tags are associated which what values, which entries are required, vs which are optional. Hey, they might even be able to be recursive structures, if that's not too difficult for consumers to manage. The idea is that the data contract is all documented somewhere, so the producers and consumers of the information just need to consult the docs for the expected behavior. This has the advantage that we don't have to hand-write all these structs, which are nothing but a collection of accessors and mutators, results in fewer types, and in general just seems a lot cleaner to me. (I suppose if we could *codegen* these structs, then that would be an advantage, but I'm not sure if you can codegene structs from schema, where the objects stored on the structs are native Java objects.) I realize that the Message type is a lot like this (it implements Map<String, Object>), but the semantics of "Message" are probably not appropriate for this use. Perhaps this new type could be a base-type for Message, so that it has better visibility/use in CF as a whole. Then a Message would extend this type, which it may also contain. Nothing like confusing our users! :) Anyway, do folks see this as a potentially valuable addition to CXF? Either way, I need the information from the transport. I think it just boils down to how we want that information to be represented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 02:38:11 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 18860 invoked from network); 5 Mar 2007 02:38:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 02:38:11 -0000 Received: (qmail 83495 invoked by uid 500); 5 Mar 2007 02:38:20 -0000 Delivered-To: osmith@example.org Received: (qmail 83486 invoked by uid 500); 5 Mar 2007 02:38:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 83477 invoked by uid 99); 5 Mar 2007 02:38:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 18:38:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 18:38:10 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D06C2714336 for <osmith@example.org>; Sun, 4 Mar 2007 18:37:50 -0800 (PST) Message-ID: <7747320.1173062270851.JavaMail.jira@brutus> Date: Sun, 4 Mar 2007 18:37:50 -0800 (PST) From: "Fred Dushin (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Updated: (CXF-445) Accessing Connection-based info from the transport In-Reply-To: <12833212.1173060950868.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-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Dushin updated CXF-445: ---------------------------- Attachment: CXF-445.patch patch file generated via svn diff from trunk of revision 514527 > Accessing Connection-based info from the transport > -------------------------------------------------- > > Key: CXF-445 > URL: https://issues.apache.org/jira/browse/CXF-445 > Project: CXF > Issue Type: Improvement > Components: Transports > Affects Versions: 2.0-RC > Reporter: Fred Dushin > Fix For: 2.0-RC > > Attachments: CXF-445.patch > > > Original post to cxf-dev mailinglist. Patch to follow: > I'd like to get access to some connection-based information from the transport -- in particular, properties relating to any security context established at the transport (e.g., via an SSL handshake, or via a GSS-Accept) -- > Primarily I'm thinking about the server-side of an invocation, though I suspect there may be client-side requirements, as well, though at present they are not as pressing for me. (They may be later). > In any event, I've found that the transport is not populating the Message with any of the information I need, so I'd like to propose what I think should be a simple solution. > First, I understand the fact that there are potentially many different transport implementations, even perhaps for the same protocols. So in some cases, this information may not be accessible by the transport, which is unfortunate (and perhaps motivation for not using the transport all together, depending on the business requirements). So the solution should allow for the possibility that some transports can't provide the needed info, so that consumers of the information can code defensively in these situations (throw an exception, log a warning, whatever). > I can see how the transport destination implementations are instantiating the Message structures, which in turn get passed to the various interceptors (again, talking about the server-side here). So I'd like the transports, as the divine creators of Messages, to populate said messages with the contextual information I need. The question then becomes, what should this information look like, and how should it be keyed on the Message? > We have several alternatives, which I'd like suggestions on before submitting a patch. > First, I assume for purely organizational purposes we don't want a *huge* collection of tags on the Message. Not that it matters much (the Message is currently implemented as a HashMap, so adding a lot of data should not have an impact on lookup), but perhaps for purely aestheic reasons, it would be better to aggregate this information in some comprehensible manner. > Going on that assumption, we have some options. We could define a type or collection thereof, each of which has a collection of accessors (and mutators, for the benefit of our transports), which define which data is available, where the types stowed on these structs are common, well-known, and guaranteed likely-to-exist types, e.g., > class/interface TLSTransportInfo { > java.security.cert.Certificate[] getPeerCertificateChain() ... > } > I started to do this, but the LISP programmer in me said "there has to be a better way". (I have an innate repulsion to vacuous code, but I'm old-fashioned that way :) So I turned to our good friend java.util.Map for inspiration (who needs types when you have a cons!). Why not define leverage a Map<String, Object>, and define a contract for what the structure of the map needs to be -- what tags are associated which what values, which entries are required, vs which are optional. Hey, they might even be able to be recursive structures, if that's not too difficult for consumers to manage. The idea is that the data contract is all documented somewhere, so the producers and consumers of the information just need to consult the docs for the expected behavior. > This has the advantage that we don't have to hand-write all these structs, which are nothing but a collection of accessors and mutators, results in fewer types, and in general just seems a lot cleaner to me. (I suppose if we could *codegen* these structs, then that would be an advantage, but I'm not sure if you can codegene structs from schema, where the objects stored on the structs are native Java objects.) > I realize that the Message type is a lot like this (it implements Map<String, Object>), but the semantics of "Message" are probably not appropriate for this use. Perhaps this new type could be a base-type for Message, so that it has better visibility/use in CF as a whole. Then a Message would extend this type, which it may also contain. Nothing like confusing our users! :) > Anyway, do folks see this as a potentially valuable addition to CXF? Either way, I need the information from the transport. I think it just boils down to how we want that information to be represented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 03:20:11 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 26577 invoked from network); 5 Mar 2007 03:20:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 03:20:11 -0000 Received: (qmail 16658 invoked by uid 500); 5 Mar 2007 03:20:20 -0000 Delivered-To: osmith@example.org Received: (qmail 16642 invoked by uid 500); 5 Mar 2007 03:20:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 16633 invoked by uid 99); 5 Mar 2007 03:20:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 19:20:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 19:20:10 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id CF402714336 for <osmith@example.org>; Sun, 4 Mar 2007 19:19:50 -0800 (PST) Message-ID: <9604186.1173064790845.JavaMail.jira@brutus> Date: Sun, 4 Mar 2007 19:19:50 -0800 (PST) From: "Dan Diephouse (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Closed: (CXF-179) Move Holder code from JAXWSMethodInvoker to interceptors In-Reply-To: <2647196.1161803836579.JavaMail.root@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-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Diephouse closed CXF-179. ----------------------------- Resolution: Fixed I believe I did this a while ago... :-) > Move Holder code from JAXWSMethodInvoker to interceptors > -------------------------------------------------------- > > Key: CXF-179 > URL: https://issues.apache.org/jira/browse/CXF-179 > Project: CXF > Issue Type: Bug > Reporter: Dan Diephouse > Assigned To: willem Jiang > Fix For: 2.0-RC > > > The holder code should become part of the JAX-WS interceptors, so we can use other invokers and still have Holders work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 05:47:11 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 57224 invoked from network); 5 Mar 2007 05:47:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 05:47:11 -0000 Received: (qmail 30750 invoked by uid 500); 5 Mar 2007 05:47:20 -0000 Delivered-To: osmith@example.org Received: (qmail 30687 invoked by uid 500); 5 Mar 2007 05:47:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 30677 invoked by uid 99); 5 Mar 2007 05:47:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 21:47:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 21:47:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id E28CA714336 for <osmith@example.org>; Sun, 4 Mar 2007 21:46:50 -0800 (PST) Message-ID: <24421196.1173073610925.JavaMail.jira@brutus> Date: Sun, 4 Mar 2007 21:46:50 -0800 (PST) From: "Jarek Gawor (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Created: (CXF-446) Allow JAX-WS implementation bean not to implement the service endpoint interface MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Allow JAX-WS implementation bean not to implement the service endpoint interface -------------------------------------------------------------------------------- Key: CXF-446 URL: https://issues.apache.org/jira/browse/CXF-446 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Reporter: Jarek Gawor Attachments: CXF-446.patch JAX-WS services (as per spec) are not required to implement the service endpoint interface. Right now, if the service does not implement the SEI, a "object is not an instance of" error is returned on an invocation. The attached patch enables the services not to implement the SEI and contains test for such cases. This patch also contains updated test cases for CXF-444. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 05:47:17 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 57268 invoked from network); 5 Mar 2007 05:47:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 05:47:15 -0000 Received: (qmail 31301 invoked by uid 500); 5 Mar 2007 05:47:23 -0000 Delivered-To: osmith@example.org Received: (qmail 31292 invoked by uid 500); 5 Mar 2007 05:47:23 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 30819 invoked by uid 99); 5 Mar 2007 05:47:21 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 21:47:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 21:47:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 4EC3671433C for <osmith@example.org>; Sun, 4 Mar 2007 21:46:51 -0800 (PST) Message-ID: <27466676.1173073611320.JavaMail.jira@brutus> Date: Sun, 4 Mar 2007 21:46:51 -0800 (PST) From: "Jarek Gawor (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Updated: (CXF-446) Allow JAX-WS implementation bean not to implement the service endpoint interface In-Reply-To: <24421196.1173073610925.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-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated CXF-446: ---------------------------- Attachment: CXF-446.patch > Allow JAX-WS implementation bean not to implement the service endpoint interface > -------------------------------------------------------------------------------- > > Key: CXF-446 > URL: https://issues.apache.org/jira/browse/CXF-446 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime > Reporter: Jarek Gawor > Attachments: CXF-446.patch > > > JAX-WS services (as per spec) are not required to implement the service endpoint interface. Right now, if the service does not implement the SEI, a "object is not an instance of" error is returned on an invocation. The attached patch enables the services not to implement the SEI and contains test for such cases. > This patch also contains updated test cases for CXF-444. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 05:49:13 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 57789 invoked from network); 5 Mar 2007 05:49:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 05:49:12 -0000 Received: (qmail 32263 invoked by uid 500); 5 Mar 2007 05:49:21 -0000 Delivered-To: osmith@example.org Received: (qmail 32242 invoked by uid 500); 5 Mar 2007 05:49:21 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 32229 invoked by uid 99); 5 Mar 2007 05:49:21 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 21:49:21 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 21:49:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 7894271433E for <osmith@example.org>; Sun, 4 Mar 2007 21:48:51 -0800 (PST) Message-ID: <30499377.1173073731491.JavaMail.jira@brutus> Date: Sun, 4 Mar 2007 21:48:51 -0800 (PST) From: "Jarek Gawor (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Commented: (CXF-444) Problem with services initialized without WSDL file In-Reply-To: <13312517.1172873750868.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-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477915 ] Jarek Gawor commented on CXF-444: --------------------------------- Please see CXF-446 for slightly updated test cases. > Problem with services initialized without WSDL file > --------------------------------------------------- > > Key: CXF-444 > URL: https://issues.apache.org/jira/browse/CXF-444 > Project: CXF > Issue Type: Bug > Reporter: Jarek Gawor > Attachments: CXF-444.patch > > > When a service is initialized from an annotated class, the service returns a response that the client does not deserialize properly. I'm attaching a test case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 07:30:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 82804 invoked from network); 5 Mar 2007 07:30:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 07:30:11 -0000 Received: (qmail 29723 invoked by uid 500); 5 Mar 2007 07:30:20 -0000 Delivered-To: osmith@example.org Received: (qmail 29673 invoked by uid 500); 5 Mar 2007 07:30:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 29631 invoked by uid 99); 5 Mar 2007 07:30:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 23:30:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 23:30:10 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id B418E71432B for <osmith@example.org>; Sun, 4 Mar 2007 23:29:50 -0800 (PST) Message-ID: <7228549.1173079790719.JavaMail.jira@brutus> Date: Sun, 4 Mar 2007 23:29:50 -0800 (PST) From: "willem Jiang (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Assigned: (CXF-446) Allow JAX-WS implementation bean not to implement the service endpoint interface In-Reply-To: <24421196.1173073610925.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-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] willem Jiang reassigned CXF-446: -------------------------------- Assignee: willem Jiang > Allow JAX-WS implementation bean not to implement the service endpoint interface > -------------------------------------------------------------------------------- > > Key: CXF-446 > URL: https://issues.apache.org/jira/browse/CXF-446 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime > Reporter: Jarek Gawor > Assigned To: willem Jiang > Attachments: CXF-446.patch > > > JAX-WS services (as per spec) are not required to implement the service endpoint interface. Right now, if the service does not implement the SEI, a "object is not an instance of" error is returned on an invocation. The attached patch enables the services not to implement the SEI and contains test for such cases. > This patch also contains updated test cases for CXF-444. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 07:30:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 82811 invoked from network); 5 Mar 2007 07:30:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 07:30:12 -0000 Received: (qmail 29765 invoked by uid 500); 5 Mar 2007 07:30:20 -0000 Delivered-To: osmith@example.org Received: (qmail 29748 invoked by uid 500); 5 Mar 2007 07:30:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 29692 invoked by uid 99); 5 Mar 2007 07:30:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 23:30:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Mar 2007 23:30:11 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id F162B714339 for <osmith@example.org>; Sun, 4 Mar 2007 23:29:50 -0800 (PST) Message-ID: <17903612.1173079790986.JavaMail.jira@brutus> Date: Sun, 4 Mar 2007 23:29:50 -0800 (PST) From: "willem Jiang (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Assigned: (CXF-444) Problem with services initialized without WSDL file In-Reply-To: <13312517.1172873750868.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-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] willem Jiang reassigned CXF-444: -------------------------------- Assignee: willem Jiang > Problem with services initialized without WSDL file > --------------------------------------------------- > > Key: CXF-444 > URL: https://issues.apache.org/jira/browse/CXF-444 > Project: CXF > Issue Type: Bug > Reporter: Jarek Gawor > Assigned To: willem Jiang > Attachments: CXF-444.patch > > > When a service is initialized from an annotated class, the service returns a response that the client does not deserialize properly. I'm attaching a test case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 10:24:12 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 41402 invoked from network); 5 Mar 2007 10:24:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 10:24:12 -0000 Received: (qmail 36423 invoked by uid 500); 5 Mar 2007 10:24:20 -0000 Delivered-To: osmith@example.org Received: (qmail 36375 invoked by uid 500); 5 Mar 2007 10:24:20 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 36247 invoked by uid 99); 5 Mar 2007 10:24:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2007 02:24:20 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2007 02:24:10 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D55BD71433A for <osmith@example.org>; Mon, 5 Mar 2007 02:23:50 -0800 (PST) Message-ID: <32162624.1173090230871.JavaMail.jira@brutus> Date: Mon, 5 Mar 2007 02:23:50 -0800 (PST) From: "Johnson Ma (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Created: (CXF-447) The java2wsdl tool generated wrong namespace for datatypes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org The java2wsdl tool generated wrong namespace for datatypes ---------------------------------------------------------- Key: CXF-447 URL: https://issues.apache.org/jira/browse/CXF-447 Project: CXF Issue Type: Bug Reporter: Johnson Ma @WebService(wsdlLocation = "file:/C:/projects/stp/workspace/runtime-New_configuration(2)/JavaFirstTest0305/wsdl/com/iona/HelloWorld.wsdl", targetNamespace = "http://iona.com/", name = "HelloWorld") public interface HelloWorld { @WebMethod(operationName = "sayHi") public void sayHi( java.lang.Float f1, java.lang.Float f2 ); } Since we do not define @RequestWrapper.className, so the JAXB class used by java2wsdl will be 'com.iona.jaxws.SayHi' However, if we call the wsdl2java on the generated wsdl, it will generate type class 'com.iona.SayHi' The reason is: from the spec, the default jaxb class is packagename+jaxws+methodName. But in the generated wsdl, schema namespace is 'com.iona' , which should be set to 'com.iona.jaxws' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 23:27:45 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 64680 invoked from network); 5 Mar 2007 23:27:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 23:27:45 -0000 Received: (qmail 4373 invoked by uid 500); 5 Mar 2007 23:27:54 -0000 Delivered-To: osmith@example.org Received: (qmail 4318 invoked by uid 500); 5 Mar 2007 23:27:54 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 4307 invoked by uid 99); 5 Mar 2007 23:27:53 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2007 15:27:53 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2007 15:27:44 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 860FE714046 for <osmith@example.org>; Mon, 5 Mar 2007 15:27:24 -0800 (PST) Message-ID: <19982237.1173137244538.JavaMail.root@brutus> Date: Mon, 5 Mar 2007 15:27:24 -0800 (PST) From: "Peter Jones (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Closed: (CXF-410) specifying exclusions tag in pom.xml can cause issues with ibm jdk In-Reply-To: <14747568.1170807785727.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-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Jones closed CXF-410. --------------------------- Resolution: Fixed > specifying exclusions tag in pom.xml can cause issues with ibm jdk > ------------------------------------------------------------------ > > Key: CXF-410 > URL: https://issues.apache.org/jira/browse/CXF-410 > Project: CXF > Issue Type: Sub-task > Reporter: Peter Jones > Assigned To: Peter Jones > > For instance, bindings/http/pom.xml has something like this: > <dependencies> > <dependency> > <groupId>org.codehaus.jra</groupId> > <artifactId>jra</artifactId> > <version>1.0-alpha-1</version> > <exclusions> > <exclusion> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <scope>test</scope> > </dependency> > The exclusion of junit from jra - which I believe is meant to prevent junit from being packaged - causes the second junit dependency to be removed with the ibm jdk. So the tests won't compile. The workaround is to comment out the exclusion from the pom. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Mon Mar 05 23:29:17 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 67677 invoked from network); 5 Mar 2007 23:29:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Mar 2007 23:29:16 -0000 Received: (qmail 5181 invoked by uid 500); 5 Mar 2007 23:29:25 -0000 Delivered-To: osmith@example.org Received: (qmail 5166 invoked by uid 500); 5 Mar 2007 23:29:25 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 5157 invoked by uid 99); 5 Mar 2007 23:29:25 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2007 15:29:25 -0800 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=ASF_EMPTY_LIST_SUB_UNSUB,ASF_LIST_SUB_UNSUB,EMPTY_MESSAGE,HTML_MESSAGE,MIME_HTML_MOSTLY,MISSING_SUBJECT X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [83.161.120.155] (HELO nj300815-ier2.net.avaya.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2007 15:29:13 -0800 Received: from CAQ010AVEXU1.global.avaya.com (h148-147-57-33.avaya.com [83.161.120.155]) by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id l25NSpnI014489 for <osmith@example.org>; Mon, 5 Mar 2007 18:28:51 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C75F7E.084666DE" Subject: Date: Mon, 5 Mar 2007 15:28:51 -0800 Message-ID: <osmith@example.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Index: Acdffgf6eOaRFbpnQ0e/MZDo4P0xrQ== From: "Jakobsen, Dennis \(Dennis\)" <osmith@example.org> To: "osmith@example.org" <osmith@example.org> X-Scanner: InterScan AntiVirus for Sendmail X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C75F7E.084666DE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 ------_=_NextPart_001_01C75F7E.084666DE-- From cxf-issues-returnosmith@example.org Tue Mar 06 08:39:46 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 7778 invoked from network); 6 Mar 2007 08:39:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Mar 2007 08:39:45 -0000 Received: (qmail 63247 invoked by uid 500); 6 Mar 2007 08:39:54 -0000 Delivered-To: osmith@example.org Received: (qmail 63198 invoked by uid 500); 6 Mar 2007 08:39:53 -0000 Mailing-List: contact osmith@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:osmith@example.org> List-Unsubscribe: <mailto:osmith@example.org> List-Post: <mailto:osmith@example.org> List-Id: <cxf-issues.incubator.apache.org> Reply-To: osmith@example.org Delivered-To: mailing list osmith@example.org Received: (qmail 63188 invoked by uid 99); 6 Mar 2007 08:39:53 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Mar 2007 00:39:53 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Mar 2007 00:39:44 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 52A1D71408D for <osmith@example.org>; Tue, 6 Mar 2007 00:39:24 -0800 (PST) Message-ID: <3638421.1173170364335.JavaMail.root@brutus> Date: Tue, 6 Mar 2007 00:39:24 -0800 (PST) From: "Andrea Smyth (JIRA)" <osmith@example.org> To: osmith@example.org Subject: [jira] Updated: (CXF-280) Endpoint Specific Behaviour of RetransmissionQueue In-Reply-To: <20719379.1164982342479.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-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Smyth updated CXF-280: ----------------------------- Description: Instead of managing separate retransmission queues oer endpoint, have the retransmission control the resends on a per endpoint basis, i.e. using the acknowlegement interval in the endpoint;'s RMssertion. The acknowledgement intervals are potentially operation specific (although we may not support this initially). (was: Manage separate RetransmissionQueue per Endpoint and associate this with the RMEndpoint rather than the RMManager in order to support different acknowledgement intervals for individual endpoints. For now, use a separate manager (and separate interceptors) for each such endpoint .) Summary: Endpoint Specific Behaviour of RetransmissionQueue (was: One RetransmissionQueue per Endpoint) > Endpoint Specific Behaviour of RetransmissionQueue > -------------------------------------------------- > > Key: CXF-280 > URL: https://issues.apache.org/jira/browse/CXF-280 > Project: CXF > Issue Type: Task > Components: WS-* Components > Reporter: Andrea Smyth > > Instead of managing separate retransmission queues oer endpoint, have the retransmission control the resends on a per endpoint basis, i.e. using the acknowlegement interval in the endpoint;'s RMssertion. The acknowledgement intervals are potentially operation specific (although we may not support this initially). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From cxf-issues-returnosmith@example.org Tue Mar 06 08:41:48 2007 Return-Path: <cxf-issues-returnosmith@example.org> Delivered-To: osmith@example.org Received: (qmail 9340 invoked from network); 6 Mar 2007 08:41:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Mar 2007 08:41:45
{'source': 'Apache Software Foundation Public Mail Archives'}