Return-Path: Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: (qmail 16103 invoked from network); 19 Dec 2010 03:24:24 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Dec 2010 03:24:24 -0000 Received: (qmail 26040 invoked by uid 500); 19 Dec 2010 03:24:23 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 25871 invoked by uid 500); 19 Dec 2010 03:24:23 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 25854 invoked by uid 99); 19 Dec 2010 03:24:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Dec 2010 03:24:23 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Dec 2010 03:24:22 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oBJ3O271023999 for ; Sun, 19 Dec 2010 03:24:02 GMT Message-ID: <15978651.197591292729042409.JavaMail.jira@thor> Date: Sat, 18 Dec 2010 22:24:02 -0500 (EST) From: "Samisa Abeysinghe (JIRA)" To: java-dev@axis.apache.org Subject: [jira] Resolved: (AXIS2-2793) WSDL2Java should generate some kind of infrastructure on the server side for soap:headers defined in WSDL MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AXIS2-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2-2793. -------------------------------------- Resolution: Won't Fix For three years, this has been hanging there - does not look like a required feature. > WSDL2Java should generate some kind of infrastructure on the server side for soap:headers defined in WSDL > --------------------------------------------------------------------------------------------------------- > > Key: AXIS2-2793 > URL: https://issues.apache.org/jira/browse/AXIS2-2793 > Project: Axis2 > Issue Type: New Feature > Reporter: Glen Daniels > Assignee: Amila Chinthaka Suriarachchi > > Right now we generate extra parameters on Stubs for s on the client side. We do not do any equivalent for the server side skeletons. This is potentially a problem in that if one of the headers is sent at runtime with MustUnderstand="true", we'll get a fault even though we should understand the header. > Proposal is to define an "ApplicationHeaderHandler" which reads metadata from AxisService describing which headers the service understands. It a) checks to see that those headers are present in the message (faults if not), b) marks them as processed so MU test works, and c) supplies the OMElements in convenient properties of the MessageContext. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org