On Sun, Aug 11, 2013 at 10:53 AM, Dushan Abeyruwan <[email protected]> wrote:
> Hi KasunG > > >>> >>> We have upgraded Axis2 Jettison version from 1.1.0.wso2v1 to >>> 1.3.4.wso2v1. Currently Jettison 1.3.4.wso2v1 resides in orbit. So, if you >>> >> > I couldn't find any changers done related to axis2 in your commit > r180586, btw if anything to be change in axis2 level, all the are to be > introduced in kernel/parent , kernel/feature etc.. can you please review > the commits and please introduce axis2 jettion update to 1.3.4 accordingly > > [1] https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/parent > > *<version.jettison>1.1.wso2v1</version.jettison>* > <version.axis2.json>1.6.1.wso2v10</version.axis2.json> > > > [2] > https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/features/org.wso2.carbon.core.common.feature > *<bundleDef>org.codehaus.jettison.wso2:jettison:1.1.wso2v1</bundleDef> > * > > we need to update all otherwise the feature bundle may have > different jettision versions... > > +1. I have committed the changes in r180599. The previous commits only affected AS, but with this change, ESB and other products will get the latest changes too. As noted in the other thread, the unit tests are passing fine, but still trying to get the integration tests to build in my local build. It's failing for me due to other reasons. Thanks, KasunG > are going forward with this, please use the newer version. You can find >>> the related discussion in "Upgrading Jettison from 1.1.wso2v1 to >>> 1.3.4.wso2v1" in Dev. >>> >>> Thanks, >>> KasunG >>> >>> >>> On Fri, Aug 9, 2013 at 7:06 PM, Dushan Abeyruwan <[email protected]>wrote: >>> >>>> $subject any objections ? >>>> This has to be done due to some JSONPhaser limitation which is not >>>> fixed either at the latest jettision version which is critical and blocker. >>>> >>>> *ISSUES* >>>> >>>> *[1]* If received json response as follows [1.1] and >>>> Jettision phrase failed to convert *<16x16> ,**<24x24> .. * since >>>> those aren't valid XML representation,due to that reason we can do any >>>> content base operation on json responses received from JIRA.. >>>> >>>> >>>> [1.1] >>>> >>>> {"self":"xxxj<https://wso2.org/jira/rest/api/2/[email protected]>xxxxxx","key":"gggggg,"name":"kkkkk","emailAddress":"xxx >>>> at xxdot >>>> com","avatarUrls":{"16x16":"yyyyy","24x24":"mmmm","32x32":"mmmmm","48x48":"ccccc"},"displayName":"nnnnnn","active":true,"timeZone":"Asia/Colombo","groups":{"size":3,"items":[]},"expand":"groups"} >>>> >>>> >>>> corresponding XML suppose to be >>>> >>>> <self>xxxxxx</self> <key>x <[email protected]>xxxx</key> >>>> <name>n<[email protected]>nnnnn</name> >>>> <emailAddress>xxxxx</emailAddress> <avatarUrls> *<16x16>cccc</16x16> >>>> <24x24>kkkk</24x24> <32x32ccccc</32x32> <48x48>bbbbb</48x48>*</avatarUrls> >>>> <displayName>xxxxxx</displayName> <active>true</active> >>>> <timeZone>Asia/Colombo</timeZone> <groups> <size>3</size> </groups> >>>> <expand>groups</expand> >>>> >>>> >>>> *Fix* >>>> >>>> *MappedXMLStreamReader in Jettision 1.1* >>>> >>>> } else { >>>> nextKey = (String) node.getKeys().next(); >>>> * Matcher matcher = degitPattern.matcher(nextKey);* >>>> * newObj = node.getObject().get(nextKey);* >>>> * if(matcher.matches()){* >>>> * nextKey = "_"+nextKey;* >>>> * }* >>>> * }* >>>> >>>> a simple fix and it works >>>> >>>> >>>> the response now looks as follows >>>> >>>> >>>> { >>>> "self": >>>> "https://xxxxx/jira/rest/api/2/user?username=<https://wso2.org/jira/rest/api/2/[email protected]> >>>> xxxxxxx", >>>> "key": "[email protected] <[email protected]>", >>>> "name": "dx <[email protected]>xxx", >>>> "emailAddress": "xxxxxxx", >>>> "avatarUrls": { >>>> * "_16x16": >>>> "xxxxxxxavatarId=10142<https://wso2.org/jira/secure/useravatar?size=xsmall&avatarId=10142> >>>> ",* >>>> * "_24x24": >>>> "sssssss=10142<https://wso2.org/jira/secure/useravatar?size=small&avatarId=10142> >>>> ",* >>>> * "_32x32": >>>> "yyyyyy10142<https://wso2.org/jira/secure/useravatar?size=medium&avatarId=10142> >>>> ",* >>>> * "_48x48": >>>> "nnnnnnn=10142<https://wso2.org/jira/secure/useravatar?avatarId=10142> >>>> "* >>>> }, >>>> "displayName": "xx xxx", >>>> "active": "true", >>>> "timeZone": "Asia/xxx", >>>> "groups": {"size": "3"}, >>>> "expand": "groups" >>>> } >>>> >>>> >>>> >>>> cheers, >>>> Dushan Abeyruwan >>>> Associate Tech Lead >>>> *Integration Technologies Team* >>>> *WSO2 Inc. http://wso2.com/* >>>> *Mobile:(+94)714408632* >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Kasun Gajasinghe* >>> Software Engineer; >>> Development Technologies Team, WSO2 Inc.; http://wso2.com >>> >>> >>> , >>> *email: **kasung AT spamfree wso2.com >>> >>> >>> ** cell: **+94 (77) 678-0813* >>> *linked-in: *http://lk.linkedin.com/in/gajasinghe >>> >>> >>> * >>> * >>> *blog: **http://kasunbg.org* <http://kasunbg.org> >>> >>> >>> * >>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> >>> >>> >>> * >>> * >>> >> >> >> >> -- >> Dushan Abeyruwan >> Associate Tech Lead >> *Integration Technologies Team* >> *WSO2 Inc. http://wso2.com/* >> *Mobile:(+94)714408632* >> > > > > -- > Dushan Abeyruwan > Associate Tech Lead > *Integration Technologies Team* > *WSO2 Inc. http://wso2.com/* > *Mobile:(+94)714408632* > -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com ** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe * * *blog: **http://kasunbg.org* <http://kasunbg.org> * twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> * *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
