|
Hi!
In ULC 6.0.x when implementing an own container,
one had to sublcass ULCContainer and override createDefaultContstraints and
internalConvertFromConstraints. Adding new components to the container had
to be done via add and setConstraintsImpl. Is this still true for ULC
6.1?
I'm asking because internalConvertFromConstraints
returns an Anything and ULC 6.1 seems to replace the need to handle Anythings in
extensions by the usage of core reflection and coders. I just have the feeling
that I miss something and that it should be much simpler now.
On the client side there's the counterpart to
internalConvertFromConstraints that unpacks the Anything. Strangely
Anything.get(String, String) is deprecated and annotated with the remark "Use
getDouble(String) instead", but the value I'm getting here is a String and not a
double. There's no getString method here either.
It still works, but I want to get rid of the
deprecated warnings and do it the right way.
Cheers,
Robert
|
- [ULC-developer] Extending ULCContainer in ULC 6.1 ulc rbeeger
