cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: Unmarshalling error when using fastinfoset
Date Wed, 31 Mar 2010 15:54:31 GMT
On Wednesday 31 March 2010 11:27:08 am fahman_dude wrote:
> I confirm herewith that my real project works with the cxf 2.3-snapshot as
> expected (there are some other non-critical issues with the current trunk
> of 2.3 e.g. BeanCreationException during initialization. Will post
> separate jira ticket).

Cool.   I managed to back port the rest of the FI stuff to 2.2.x yesterday.  
Thus, the snapshots for 2.2.8 tomorrow (maybe even today's) should also work.   
Any chance you could give those a try to make sure everything got back ported 
OK?

Dan



> 
> Question to community, is there atleast some sort of rumor when will 2.3 be
> released?
> 
> fahman_dude wrote:
> > Workaround works for the test project but not for my real project. I will
> > attempt to test the real project with the cxf 2.3-snapshot and will
> > report results in here. Dan, do you have a jira ticket on this? If not,
> > dont reply I'll just post new one.
> > 
> > dkulp wrote:
> >> On Monday 29 March 2010 9:25:34 am fahman_dude wrote:
> >>> Hello,
> >>> 
> >>> please find attached eclipse test project. Its got maven config so,
> >>> normally, running "mvn install" should be sufficient to generate,
> >>> compile
> >>> and run unittest.
> >>> 
> >>> I have stripped and simplified a lot of things from my real use case,
> >>> but I
> >>> still get the same exception I reported even with this simplified
> >>> example.
> >>> 
> >>> http://old.nabble.com/file/p28069257/cxf.jaxws.infoset.twoway.mep.test.
> >>> zip cxf.jaxws.infoset.twoway.mep.test.zip
> >> 
> >> The good news is this doesn't fail on trunk/2.3.   I CAN reproduce the
> >> failure
> >> on 2.2.x.   Not all of the FI changes I made could be ported back to
> >> 2.2.x so
> >> I'll need to figure out how to get this working with 2.2.x.
> >> 
> >> As a workaround, I THINK you can set a system property of:
> >> "com.sun.xml.fastinfoset.parser.string-interning"
> >> to "true" and it may work.   It looks like in some cases, JAXB is
> >> expecting
> >> interned strings which FI isn't doing by default.    On 2.3, we force it
> >> to do
> >> so.
> >> 
> >> Dan
> >> 
> >>> dkulp wrote:
> >>> > Any chance you could create a small test case for this?  I did a LOT
> >>> 
> >>> of
> >>> 
> >>> > testing and benchmarking with FastInfoset for 2.2.7 so I know it
> >>> > works for some use cases.
> >>> > 
> >>> > On Wednesday 24 March 2010 10:43:46 am fahman_dude wrote:
> >>> >> Hi,
> >>> >> 
> >>> >> I have a webservice operation that returns primitive "string".
I
> >>> >> call this
> >>> >> very same operation in three different ways: 1. without any sort
of
> >>> >> compression; 2. with mtom compression 3. with fastinfoset
> >>> 
> >>> compression.
> >>> 
> >>> >> The no compression call and mtom compression call works but
> >>> 
> >>> fastinfoset
> >>> 
> >>> >> call fails with this exception:
> >>> >> 
> >>> >> 15:24:49,328 DEBUG [main] apache.cxf.phase.PhaseInterceptorChain
> >>> 
> >>> (240)
> >>> 
> >>> >> - Invoking handleMessage on interceptor
> >>> >> ...
> >>> >> 21) Caused by: java.lang.AssertionError
> >>> >> 
> >>> >> 	at com.sun.xml.bind.v2.util.QNameMap.getEntry(QNameMap.java:460)

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog

Mime
View raw message