Description
Problem occures when my @BeanParam object has String @HeaderParam values that are null.
On client side inside ClientProxyImpl#getValuesFromBeanParam always returns full Map<String, BeanPair> even when BeanPair has null values.
ClientProxyImpl.java
// line 481 String propertyName = m.getName().substring(3); Method getter = bean.getClass().getMethod("get" + propertyName, new Class[]{}); // Object value is null Object value = getter.invoke(bean, new Object[]{}); String annotationValue = AnnotationUtils.getAnnotationValue(annotation); values.put(annotationValue, new BeanPair(value, m.getParameterAnnotations()[0]));
Methods such handleHeaders, handleCookies has useless condition that is
always true (BeanPair is never null)
ClientProxyImpl.java
// line 585 for (Map.Entry<String, BeanPair> entry : values.entrySet()) { if (entry.getValue() != null) { headers.add(entry.getKey(), convertParamValue(entry.getValue().getValue(), entry.getValue().getAnns())); } }
That couses unintended behaviour on server side when server receives BeanParam objects with fields with String value equal to "null".
I've sent no headers but servers received header with "null" String.