On Tue, Jun 29, 2010 at 10:11 PM, Dennis Sosnoski <d...@sosnoski.com> wrote:
> Never mind, I think I found the issue. I've changed the StAXReaderWrapper > code so that you should no longer need to call startTag() at all and have > changed that back to a private method. Please try the latest 1.2.3-SNAPSHOT > jars and verify that this now works. > Yes it works fine now :-). Thanks for fix !! By the way, I've started working on the JiBX code generation API and implementing a DataBidingProfile for JiBX databinding implementation. I will post my progress as soon as I get to work to some extent and post any questions that might occur along the way. Thanks & Best Regards Nilupa > Thanks again, > > - Dennis > > > > Dennis Sosnoski wrote: > >> Nilupa Bandara wrote: >> >>> On Sat, Jun 26, 2010 at 1:00 AM, Dennis Sosnoski <d...@sosnoski.com> >>> wrote: >>> ... >>> >>> >>>> Nilupa, I've updated JiBX CVS with this change and posted new >>>> 1.2.3-SNAPSHOT jars to the maven1 repository at >>>> http://jibx.sourceforge.net/maven/jibx/jars/ Try adding the call to >>>> startTag() after constructing the StAXReaderWrapper, it should get you >>>> past >>>> the problem. >>>> >>>> >>>> >>>> >>> Hi, >>> >>> Still it gives an error even if I call the startTag() after >>> instantiating >>> the StAXReaderWrapper object[1]. However if I call same method twice >>> startTag(), it works[2] >>> >>> >> >> It sounds like the code is somehow reading beyond the end of the element >> you're having JiBX unmarshal, to the enclosing element end tag. I don't know >> why this would be occurring. >> >> Can you send me the stack traces you get when (1) you don't call >> wrapper.startTag() at all, and when (2) you just call it once? That may help >> me determine what's going wrong. >> >> Thanks, >> >> - Dennis >> >> -- Nilupa Bandara
