Re: [jibx-users] Xml schema referenced type not defined

Sorry... I don't understand the question... can you provide an example? Keith From: tony Tony [mailto:tonyto...@gmail.com] Sent: Thursday, September 24, 2009 7:49 PM To: JiBX users Subject: Re: [jibx-users] Xml schema referenced type not defined

Re: [jibx-users] CodeGen OTA XSD issue

Hi Mat, They've created circular references in the includes in the 2009A schemas, which I suspect is the cause of the problem (OTA_HotelCommonTypes includes OTA_HotelReservation, and OTA_HotelReservation includes OTA_HotelCommonTypes). This is valid in schema terms, but appears to cause a

Re: [jibx-users] JIBX Clients

Hi Toni, Is this for use with Axis2? I've been working on implementing CodeGen schema generation via Axis2 WSDL2Java, and hope to have that available sometime soon. JiBX/WS doesn't currently use client stub generation, though I'll add that at some point for a user-friendly interface. -

Re: [jibx-users] Error trying to use precompiled bindings and extended classes

That's a strange one. Are you sure the binding used with the jar code is the same one you're using with the include? It looks like there's an abstract mapping in the include which was not in the binding used for the code in the jar. I've added a check for this condition in the current code

Re: [jibx-users] No Unmarshallers being produced by binding

To understand why the dates are getting off you'd need to look at the actual XML being marshalled or unmarshalled. The format you give is that used for the schema xs:dateTime type, which allows (but does not require) a UTC offset. If the XML representation doesn't include UTC offsets it could

Re: [jibx-users] Namespace problem

Hi Adr, The 1.2.1 release had problems with attribute definitions in a different schema, which should be fixed now. Can you try this with the current build? The jars are available from the Maven(1) repository, at http://jibx.sourceforge.net/maven/jibx/jars/ (look for the 1.2.2-SNAPSHOT jars).

Re: [jibx-users] strip-suffixes is recursive?

This is by design, since some schemas use combinations of added words in different orders. It'd be possible to write the code so that it would only remove at most one instance of each suffix, but that seems more trouble than it's worth. You should be able to easily change this behavior with a

Re: [jibx-users] Option for automatically adding namespace in binding

Hi Krishnanunni, The generated binding should have everything needed to work with documents matching the schema definition. What happens if you don't add the ns='...' attribute? - Dennis Dennis M. Sosnoski XML and Web Services in Java Training and Consulting http://www.sosnoski.com -