The problem must be something else. Please take a look at the
structure-binding tutorial at
http://jibx.sourceforge.net/tutorial/binding-structures.html#intro
A quote:
[...] the structure of your objects is not tied to the structure of the
XML - you can restructure your object classes without
this issue has been discussed on the list before., and i entered it in
jira. i have the same problem. so far there does not seem to exist a
real solution for it.
the only possibility to add the desired attribute 'xsi:schemaLocation'
is by adding get/set methods for it to your mapped classes.
i
Angel,
did you think about utilizing the DomElementMapper from the
org.jibx.extras package to (un)marshal the XmlResultSet? Or has that
nothing to do with DOM?
Tilman
The better way of handling this is with a custom marshaller/unmarshaller
for your XmlResultSet, where you can work at the
hi,
is there a way to include constant values into the binding definition
like:
value style=attribute name=whatever _const_=a_constant_value/
or can i retrieve such a value from a different object than the context
object? maybe from a static method:
mapping name=A type=AClass
value
useful and try it out I'd appreciate it if you
could also add it to the Wiki. For what it's worth I think I've made it
a little easier to use, with some basic instructions on the form to add
or edit a snip.
- Dennis
Tilman Linden wrote:
hello again,
i wonder if there is a possibility
hello again,
i wonder if there is a possibility to access the element stack inside of
a binding definition, just like you can do inside a Custom Marshaller
using getStackObject(...).
assume the following scenario:
class A {
String a_name;
B b;
C c;
}
class B {
String b_name;
}
class C
hi,
i wanted to use the DomElementMapper provided in the extras package.
unfortunately, i always get an ArrayIndexOutOfBoundException when
marshalling an Element... Seems to have something to do with namespace
indices, but could not figure out any details...
i am using jibx beta3c now. any
hi,
since i added the test-methods to the following binding, i get the
VerifyError described below when instantiating Objects of class
Location. I played around a little bit and noticed that the appearance
of any of first three test-methods causes the error while the last
test-method
Hello all,
as i am new to this list please let me shortly introduce myself. My name
is Tilman and i am working for the Fraunhofer Institut based in
Berlin/Germany as a Student worker. I am currently working on a project
in the Context of Grid Computing and we want to use JiBX to store the
state