Tim Sawyer wrote:
I've managed to reproduce the problem with a simple test, and marshalling manually. If I run this code I get the same error:Okay, that explains what's going wrong - multiple binding definitions, and the wrong one is being used. If you want to enter this in Jira as a case where JiBX should give an error message (rather than the mysterious exception) I'll make sure to get a fix in for beta 4.
...
The important thing to note is that both lMarshallContexts are passed the lCallParameter, where the second one should have been passed lResponseParameter (and if you do it works fine) So in the second case, I'm trying to marshall lCallParameter given a factory from LoginApplicationResponseParameter. The error is:
java.lang.NullPointerException
The reason this is occurring may be an error in JibxSoap. I don't think I've tested it with multiple binding definitions, though this is something it certainly needs to support for general use. Are you using the jibx-binding attribute of the <service> element to set the binding definition to be used for the service? The JibxSoap design does only allow for one binding per service, so you can't use both your bindings within the same service. If that's the problem you'll need to combine them into a single binding.
- Dennis
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ jibx-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jibx-users
