Hi,
while creating a RTT toolkit for BFL I observed the following behavior when
calling writePoperty for one of my types:
marshalling.writeProperty("matrix","cpf/prop.cpf")
this call results in a decomposition of ALL properties in my component
(luckily only one is written).
This looks like a bug for me.
Tinne
writeProperty decomposes ALL properties but only writes one
On Wednesday 18 March 2009 13:13:59 Tinne De Laet wrote:
> Hi,
>
> while creating a RTT toolkit for BFL I observed the following behavior when
> calling writePoperty for one of my types:
>
> marshalling.writeProperty("matrix","cpf/prop.cpf")
>
> this call results in a decomposition of ALL properties in my component
> (luckily only one is written).
>
> This looks like a bug for me.
Do you mean that the behaviour is buggy or that the algorithm is inefficient ?
Peter
writeProperty decomposes ALL properties but only writes one
On Wednesday 18 March 2009 23:24:16 Peter Soetens wrote:
> On Wednesday 18 March 2009 13:13:59 Tinne De Laet wrote:
> > Hi,
> >
> > while creating a RTT toolkit for BFL I observed the following behavior
> > when calling writePoperty for one of my types:
> >
> > marshalling.writeProperty("matrix","cpf/prop.cpf")
> >
> > this call results in a decomposition of ALL properties in my component
> > (luckily only one is written).
> >
> > This looks like a bug for me.
>
> Do you mean that the behaviour is buggy or that the algorithm is
> inefficient ?
You can call it inefficient if you want, I believe decomposing all properties
when you only want to write one, can be that inefficient that it becomes buggy.
Tinne
writeProperty decomposes ALL properties but only writes one
On Thursday 19 March 2009 09:06:42 Tinne De Laet wrote:
> On Wednesday 18 March 2009 23:24:16 Peter Soetens wrote:
> > On Wednesday 18 March 2009 13:13:59 Tinne De Laet wrote:
> > > Hi,
> > >
> > > while creating a RTT toolkit for BFL I observed the following behavior
> > > when calling writePoperty for one of my types:
> > >
> > > marshalling.writeProperty("matrix","cpf/prop.cpf")
> > >
> > > this call results in a decomposition of ALL properties in my component
> > > (luckily only one is written).
> > >
> > > This looks like a bug for me.
> >
> > Do you mean that the behaviour is buggy or that the algorithm is
> > inefficient ?
>
> You can call it inefficient if you want, I believe decomposing all
> properties when you only want to write one, can be that inefficient that it
> becomes buggy.
Then this should become a bug report such that we can track and resolve it.
Peter