I mentioned in a previos message that I am having some problems with
namespaces. I have a custom marshaller that examines a list for elements
that implement IMarshallable, and when it finds them, it calls
BindingDirectory.getFactory, then creates a marshalling context and
tries to marshall the
Hi Stephen,
I think the problem is related to the way Collections work. JiBX will
attempt to place everything in a collection unless it is restricted
somehow to a particular type; this works great when what you want is
heterogeneous collections, but, in your case you only want to have
Tenders
Hi Leif,
I worked through the implications of this error and added checking
during validation to catch the problem case. I also fixed the line 0
problem. :-)
- Dennis
Leif Stainsby wrote:
Hi,
I'm reporting this because the error message said I should ;-). I don't
have a particular
Leif, I'm somehow missing context on this one - I don't see any earlier
messages relating to this. Can you tell me how you got the
IllegalStateException? I'd like to make sure it's resolved for the
future. Thanks,
- Dennis
Leif Stainsby wrote:
Hi,
It appears that the problem involved
Hi Lorrin,
The Schema generator is in need of updating. I think I've finally added
the last feature for JiBX 1.0 (yes, I know I've said that before), and
should go back to revise the binding generator and schema generator to
match the JiBX changes since they were written. I probably won't get
Hi Nuno,
I've never seen anything like this, though it may be some kind of subtle
error in the character handling. What character encoding are you using
in your document? Also, try adding some more whitespace before the
DadosOficina start tag and see if that makes a difference. Finally,
As Leif (eventually) discovered, the issue here was that his namespace
declaration, nested inside the ServiceIdentification element mapping,
only applies to the definitions within that mapping. If you want a
namespace to apply to all the components of your binding, make it a
child of the
I am trying to figure out how to use jibx and maven 2. I was hoping I could ask the question here because it is hard to explain how to use jibx across modules in the maven mailing list.
As an example, I have the following directory structure:common common1 common2 subcommon subcommon1
Probably the order of child components in the binding definition. The
include elements need to be the first child elements of the binding
element, before anything else. If that doesn't help, show the first 5
lines of AddClaimOverride.xml.
- Dennis
sanjeev kumar wrote:
Hi,
Could somebody