Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <7477558.1182274047211.JavaMail.jira@brutus>
Date: Tue, 19 Jun 2007 10:27:27 -0700 (PDT)
From: "Steve Kondik (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Updated: (CXF-340) Support adding extra classes to JAXB
 context
In-Reply-To: <2578573.1167418100956.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-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Kondik updated CXF-340:
-----------------------------

    Attachment: cxf-test-extends.tar.gz

My fault- I thought that the enclosing element set the default namespace.  Inheritance is still not working though.

Attached is an updated version of the test that has an "ExtendedWidget" :)

It fails with the same exception noted above, like JAXB can't see the extended class to use for unmarshalling.


> Support adding extra classes to JAXB context
> --------------------------------------------
>
>                 Key: CXF-340
>                 URL: https://issues.apache.org/jira/browse/CXF-340
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.0-M1
>            Reporter: Dan Diephouse
>            Assignee: Freeman Fang
>             Fix For: 2.1
>
>         Attachments: cxf-test-extends.tar.gz, cxf-test.tar.gz, Widget.java
>
>
> Users may have their own JAXB classes which need to be included in the context. We should provide a simple mechanism to add extra classes to the context. (This worked pretty well in XFire).
> HashMap props = new HashMap();
> props.put("jaxb.additionalContextClasses", new Class[] { Foo.class, Bar.class });
> serverFactory.setProperties(props);
> serverFactory.create();

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