Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <17080760.1194959630797.JavaMail.jira@brutus>
Date: Tue, 13 Nov 2007 05:13:50 -0800 (PST)
From: "Benson Margulies (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Commented: (CXF-1198) Element with a refName pointing to an
 unqualified element that isn't in the same schema.
In-Reply-To: <11202240.1194817970705.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542136 ] 

Benson Margulies commented on CXF-1198:
---------------------------------------

JAXBSchemaInitializer.begin(MessagePartInfo) is coming up with a bogus element name with the help of ClassBeanInfoImpl from Sun. The namespace is null.

> Element with a refName pointing to an unqualified element that isn't in the same schema.
> ----------------------------------------------------------------------------------------
>
>                 Key: CXF-1198
>                 URL: https://issues.apache.org/jira/browse/CXF-1198
>             Project: CXF
>          Issue Type: Bug
>          Components: JAXB Databinding
>    Affects Versions: 2.1
>            Reporter: Benson Margulies
>            Assignee: Daniel Kulp
>         Attachments: diffs.txt
>
>
> I made a change to the classes for the Javascript test harness service, and I hit an apparently unrelated problem.
> If you remove the @Ignore from DocLitWrappedTest, and run with -ea, you'll hit an assertion. The assertion is because there is a type with an element with no schema type, no schema type name, and a refName of {}testBean1. Now, there's no such beast. Really. testBean1 derives from the class TestBean1, which looks like ...
> @XmlRootElement
> @XmlType(namespace = "uri:org.apache.cxf.javascript.testns")
> public class TestBean1
> In the past, I hit some cases like this where the XML Schema objects were more or less acting like a faithful recording of what the XML might look like: ref='bloop' for bloop in the TNS. Whether or not that's a good idea, it isn't what's happening this time, in that the type that contains the element that causes this havoc lives in a different namespace than the TestBean1, so in XML the ref would have an actual prefix.
> Dan may already be 'in process' on this issue, I don't know why adding a wrapper type to enable something else entirely uncovered this particular manifestation.

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