Hi,
I get this exception while running an example
org.jibx.runtime.JiBXException: Mapping for type B must extend abstract
mapping for type Ref.
It looks like the error is cause of the way the mapping defines that B
extends A and B extends Ref.
mapping name=b
class=B
*
I will be out of the office starting 01/23/2007 and will not return until
01/29/2007.
I will respond to your message when I return.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay
The problem here is that JiBX for some reason things the B class mapping
does not extend the Ref class mapping. Given your binding, this should
work, so I'm not sure where the problem is arising.
I suggest you first double-check to make sure that all your classes are
up to date (so clean all
Hi Jan,
There's no way to do this at present, though it's on the list for the
JiBX 2.0 changes
(http://www.sosnoski.com/jibx-wiki/space/issues-2.0/binding-definition).
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com -
Hi Yann,
I had to do some digging to find the original message you were referring
to, but will reply to that one as well. I think Stefano's issue is
different from yours.
You're correct that reusing the same element name on a mapping should
work fine as long as the namespaces are different.
Hi Johan,
The unmarshalling error basically means that the code thought it had
processed everything in the owner element content, but hadn't found
anything to do with the collectiontypeone element. That's very
strange, especially since you show the contained structure is required
(meaning
Hi Stefano,
This was one of the clean-up steps I took because the JiBX bindings were
too loosely enforced. Duplicate names were obviously never officially
supported in bindings used for unmarshalling - there's no meaningful way
to do so, since there's no way of knowing which of the conflicting
Hi Brian,
Thanks for helping out on the users list!
Just as an improvement to your recommendation, though, since about 1.1
JiBX has supported a create-type=... attribute for collection
elements (along with mapping and structure, for that matter). This
allows you to avoid the nuisance of
Hi Luis,
Can you add a Jira for this with your code attached (preferably with an
Ant build to demonstrate the problem)? I didn't knowingly change
anything that would cause this, but there have been a lot of code
changes since 1.1.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Hi Marcelo,
You should be able to do this by duplicating some information. Basically
just remove the value definitions from the base class (Vehicle) and
use them directly within the mapping for the subclasses (Truck and
Bus). So the mapping for Truck would look like:
mapping abstract=true
Hi Hao,
You're missing some details in your email. Are you using JibxSoap and
getting this problem? The JibxSoap distribution is seriously
out-of-date, so you get problems if you try to use it with the current
JiBX distribution. I'll try to get it updated by this weekend. If you're
not using
Hi Stefano,
Xsd2Jibx is seriously outdated (though still usable with simple
schemas). That aside, it doesn't know anything about Hibernate so could
not generate anything to control Hibernate persistence.
I am actively working on the replacement for Xsd2Jibx, and I'm hoping to
make that
The easiest way of doing this is by defining a custom
marshaller/unmarshaller for the Message class, with normal mapping
definitions for the Header and Body classes. Your custom unmarshaller
can unmarshal the Header and then check the resulting values to see if
the Body needs to be
You need to be a little more specific about what you want to do. Looking
over the binding tutorial section on Structure Mapping may get you
started: http://jibx.sourceforge.net/tutorial/binding-structures.html#intro
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and
Hi Per-Ivar,
You don't need choice=true for a collection of items - just say
ordered=false and flexible=true on the collection element itself,
then list the different alternatives you want to handle as child
structures within the collection. So something along these lines
should work:
Hi Jörg,
I can't really help you with this, aside from saying that JiBX has no
known legal restrictions on distribution and is freely available from
anywhere in the world through SourceForge distribution.
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
Hi Rohan,
The Xsd2Jibx tool is very outdated and no longer maintained. You'll need
to download an old version of JiBX (try jibx-1.0RC1, since that's from
the same timeframe as the last Xsd2Jibx release) to make this work.
I am actively working on a replacement, and hope to have it available
Hi Dennis,
On 1/25/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
Hi Rohan,
The Xsd2Jibx tool is very outdated and no longer maintained. You'll need
to download an old version of JiBX (try jibx-1.0RC1, since that's from
the same timeframe as the last Xsd2Jibx release) to make this work.
I am
Hi Dennis,
Thanks for ur Rsponse, However my problem was solved. I recompiled the
Xsd2jibx java files and created new jars using the Jibx version i had.
On 1/25/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
Hi Rohan,
The Xsd2Jibx tool is very outdated and no longer maintained. You'll need
19 matches
Mail list logo
