Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 90996 invoked from network); 11 Nov 2006 15:23:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Nov 2006 15:23:04 -0000 Received: (qmail 43072 invoked by uid 500); 11 Nov 2006 15:23:08 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 43025 invoked by uid 500); 11 Nov 2006 15:23:08 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 43012 invoked by uid 99); 11 Nov 2006 15:23:08 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Nov 2006 07:23:08 -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; Sat, 11 Nov 2006 07:22:57 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0660D7142CD for ; Sat, 11 Nov 2006 07:22:37 -0800 (PST) Message-ID: <33071406.1163258557017.JavaMail.jira@brutus> Date: Sat, 11 Nov 2006 07:22:37 -0800 (PST) From: "Rich Scheuerle (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Created: (AXIS2-1678) JAX-WS Block representation of JAXB MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org JAX-WS Block representation of JAXB ----------------------------------- Key: AXIS2-1678 URL: http://issues.apache.org/jira/browse/AXIS2-1678 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Rich Scheuerle The JAXB Message contains objects called Blocks. A block is a representation of an xml document , which means that it must have a single instance element defined by a root element. A block can have a number of different backing representations. One of these representations is a JAXB object. I am adding assertions and code to ensure that the JAXB Object that is used for a block can be rendered as an "element". (i.e. the JAXBObject must either be a JAXBElement or it must be an object that has @XmlRootElement defined). The second change is to the JAXBBlockContext. You create a JAXBBlockContext from either the JAXBContext from the user (only dispatch case) or you give the JAXBBlockContext a set of "context packages"....which are then used to create or get an appropriate JAXBContext. This change is needed to ensure that we are popluating the context with the appropriate packages. These changes lead to changes in the classes the reference this constructs: Dispatch and MethodMarshaller classes. These changes revealed some inconsistencies between "element rendered" JAXB Objects and "type rendered" JAXBObjects. For example, a JAXB Object with @XMLRootElement represents both a "element and a type" rendering. A JAXBElement Object represents the "element" rendering, and the JAXBElement's getValue() method returns the "type" rendering. There are several places in the code where it wants the "element" rendering...and other places want the "type" rendering. I tried to correct these as I found them. We are considering some redesign here to address these kinds of concerns. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org