JiBX unmarshalling - DOM error

[Arjen Poutsma]

Arjen,
Thanks for the fix! Was this an extensive update or a couple of blocks of code? Just curious, which classes and what areas were updated.

thanks again!
Ron

You're welcome! It was quite extensive, and it involved moving some ws-core code to a separate xml module, so that oxm could also use it. Then I wrote some more tests, and worked from there. I'm still not sure if I like the solution I have right now, but at least you have something to work with. The stuff I might change will be internal only, and shouldn't affect the public interface.

Cheers,

[rwilcom]

How long until an M2 build is available (that will contain these updates)?

thanks.
Ron

[Arjen Poutsma]

I will create a snapshot today, which will not be M2 but contains the stuff you need.

[rwilcom]

Great! Where will I be able to download this - will it be under 'files' in sourceforge?

thanks,
Ron

[rwilcom]

I am still wondering where I can get the snapshot of the Spring WS package that includes the JiBX (axiom soap factory) corrections? Any help or direction would be appreciated.

thanks!
Ron

[Arjen Poutsma]

Look here.

[rwilcom]

I have an M2 snapshot (the one with the JiBX fixes) - I am trying to move forward with using the JiBX marshalling implementation so I set it up to use the AxiomSoapMessageContextFactory. Now I am getting dependencies errors - my first was for JiBX itself (so I loaded the latest JiBX jars and got passed those)... now I am getting Axiom dependency failures. Says that the AxioumSoapMessageContextFactory cannot be initialized because it depends on class 'org.apache.axiom.om.OMException' - so, now I am downloading Axiom 1.0 ... but my question is when does this dependency landslide end?

What other dependencies am I going to run into here - trial and error is no fun.

thanks.
Ron

[Arjen Poutsma]

SWS is a pretty flexible framework, which is hard to describe in maven2 dependencies. For instance, it does not require JiBX nor Axiom to work, that's why I set these dependencies as optional in the POM. The alternative would be to set them as required, but then everybody will download axiom, Jibx, castor, xlmbeans, etc. etc. Not a solution, IMO.

I think that they are going to implement something similar to Ivy configurations in maven 2.1, which should be useful. Then, I could just define an axiom or jibx configuration, and all deps would resolve automatically.

But to answer your question: the basic deps you need are (off the top of my head):

• stax-api
• a stax implementation (Woodstox is fast: wstx-asl)
• axiom-api
• axiom-impl
• jibx-run
• jibx-bind & bcel (only at compile time)

Cheers,