5:51
À : user@karaf.apache.org<mailto:user@karaf.apache.org>
Objet : Re: Troubles when creating a builder with blueprint.
A Javabean is manipulated by a builder, a Javabean isn't a builder itself.
I gave builder pattern implementation and did not duplicated any method of the
bean (I
: user@karaf.apache.org
Objet : Re: Troubles when creating a builder with blueprint.
When this happens to me, it's because I'm using PropertyDescriptor - it's
methods getReadMethod and getSetterMethod follow the JavaBeans spec very
closely, so for example you can't have a boxed
esult list contains one signature, then this is the resulting
> signature.
> 11 Otherwise, the disambiguation fails
>
> JP
>
> De : CLEMENT Jean-Philippe [mailto:jean-philippe.clem...@fr.thalesgroup.com]
> Envoyé : mardi 24 juin 2014 17:03
> À : user@karaf.apache.org
> Objet
rax.net<mailto:j...@nanthrax.net>]
Envoyé : mardi 24 juin 2014 14:53
À : user@karaf.apache.org<mailto:user@karaf.apache.org>
Objet : Re: Troubles when creating a builder with blueprint.
Hi JP,
you can using a wrapper bean or a factory.
Regards
JB
On 06/24/2014 12:20 PM, CLEMENT Jean-Philipp
..@nanthrax.net]
> Envoyé : mardi 24 juin 2014 14:53
> À : user@karaf.apache.org
> Objet : Re: Troubles when creating a builder with blueprint.
>
> Hi JP,
>
> you can using a wrapper bean or a factory.
>
> Regards
> JB
>
> On 06/24/2014 12:20 PM, CLEMENT Jean-Phil
x.net]
Envoyé : mardi 24 juin 2014 14:53
À : user@karaf.apache.org
Objet : Re: Troubles when creating a builder with blueprint.
Hi JP,
you can using a wrapper bean or a factory.
Regards
JB
On 06/24/2014 12:20 PM, CLEMENT Jean-Philippe wrote:
> A builder usually returns itself to cumulates cha
nvoyé : lundi 23 juin 2014 17:49
À : user@karaf.apache.org
Objet : Re: Troubles when creating a builder with blueprint.
Hi Christophe,
in JavaBeans (following by Blueprint), a setter is void, and a getter doesn't
have argument.
So it should be:
public void setMaxValue(float maxValue) {
thi
;>> language perspective there is nothing which prevents this as a method is
>>> identified via its name and arguments; it is not tied to its return type.
>>>
>>> Is the return type really prohibited from the Blueprint spec or is it
>>> left unspecified?
&
me and arguments; it is not tied to its return type.
>>
>> Is the return type really prohibited from the Blueprint spec or is it
>> left unspecified?
>>
>> JP
>>
>>
>> -----Message d'origine-
>> De : Jean-Baptiste Onofré [mailto:j...@nanthra
rax.net]
> Envoyé : lundi 23 juin 2014 17:49
> À : user@karaf.apache.org
> Objet : Re: Troubles when creating a builder with blueprint.
>
> Hi Christophe,
>
> in JavaBeans (following by Blueprint), a setter is void, and a getter
> doesn't have argument.
> So it should be:
>
&g
the return type really prohibited from the Blueprint spec or is it left
unspecified?
JP
-Message d'origine-
De : Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
Envoyé : lundi 23 juin 2014 17:49
À : user@karaf.apache.org
Objet : Re: Troubles when creating a builder with blueprint
Hi Christophe,
in JavaBeans (following by Blueprint), a setter is void, and a getter
doesn't have argument.
So it should be:
public void setMaxValue(float maxValue) {
this.maxValue=maxValue;
}
public float getMaxValue() {
return this.maxValue;
}
Regards
JB
On 06/23/2014 05:34 PM, Lasse
Hello,
I wrote a builder containing the following setter which does not return void
(see following sample).
/**
* @param maxValue
*Maximal value for compression law attributes
* @return the builder.
*/
public CompressionLawBuilder setMaxValue(final float m
13 matches
Mail list logo