Hi Dan, I saw your mail too late. I used MessageUtils.isTrue(obj), which I remember using it in another occasion. That would be also okay, I suppose. regards, aki
2012/3/16 Daniel Kulp <[email protected]>: > > Aki, > > Just use MessageUtils.getContextualBoolean(....) > > and it would handle both cases. :-) > > Dan > > > On Friday, March 16, 2012 04:02:42 PM Aki Yoshida wrote: >> > 2) Small improvement suggestion regarding >> > "jaxws.provider.interpretNullAsOneway" property: does it make sense to >> > define property's value as string "true"/"false" instead Boolean >> > object? It makes configuration via Spring shorter and cleaner: >> > <jaxws:endpoint >> > ... >> > <jaxws:properties> >> > <entry key="jaxws.provider.interpretNullAsOneway" >> > value="true" /> </jaxws:properties> >> > </jaxws:endpoint> >> > >> > Instead >> > >> > <bean id="BooleanTrue" class="java.lang.Boolean"> >> > <constructor-arg index="0" value="true"/> >> > </bean> >> > >> > <jaxws:endpoint >> > ... >> > <jaxws:properties> >> > <entry key="jaxws.provider.interpretNullAsOneway" >> > value-ref="BooleanTrue" /> </jaxws:properties> >> > </jaxws:endpoint> >> > >> > What do you think? >> >> you are right to point out this inconvenience of using boolean. I'll >> make it configurable using a simple string value. >> >> regards, aki >> > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >
