Robotics Systems Types

When working with debian package librstconverters-amarsi0.9 I have to manually resolve the ambiguity for .rst.geometry.Pose and .rst.vision.Image (only those two).

Excerpt from the converter registry:

...                                                                                       
1369818603231 rsb.converter.repository [INFO]: Registering converter *rsb::converter::ProtocolBufferConverter<rst::geometry::Pose>[wireType = std::string, wireSchema = .rst.geometry.Pose, dataType = rst::geometry::Pose] at 0x10036e0
...
1369818603231 rsb.converter.repository [INFO]: Registering converter *rst::converters::boost::TransformationPoseConverter[wireType = std::string, wireSchema = .rst.geometry.Pose, dataType = boost::multi_array<double, 2ul, std::allocator<double> >] at 0x1004580
1369818603231 rsb.converter.repository [INFO]: Registering converter *rst::converters::boost::TwoDPoseConverter[wireType = std::string, wireSchema = .rst.geometry.Pose, dataType = boost::multi_array<double, 1ul, std::allocator<double> >] at 0x1004b40
terminate called after throwing an instance of 'std::runtime_error'
  what():  Ambiguous converter set for wire-type `std::string' and wire-schema `.rst.geometry.Pose': candidate data-types are {boost::multi_array<double, 2ul, std::allocator<double> >, rst::geometry::Pose, boost::multi_array<double, 1ul, std::allocator<double> >}; hint: add a configuration option `transport.<name>.converter.cpp.".rst.geometry.Pose" = <one of {boost::multi_array<double, 2ul, std::allocator<double> >, rst::geometry::Pose, boost::multi_array<double, 1ul, std::allocator<double> >}>' to resolve the ambiguity.
Aborted (core dumped)

So as for Pose, there are three converters for the wire-schema .rst.geometry.Pose.

1. First of all: Is this erroneous behavior / configuration?
2. If this is intended behavior, can be somehow change the default behavior? It doesn't seem very convenient, that you have to manually resolve ambiguity before working with the rst converters.