Sergey's issues with JAX-RS have started me looking at how Aegis maps types. The following temptation now occurs: allow the fundamental aegis type mechanism to map generics. Somene could thus add a mapping from any X<y,x,q> -> XML via a custom type. Of course, with type erasure, this only will pay attention to the declared type, not the dynamic type.
Somehow, I feel as if this is a slippery slope we don't want to start down. However, the defined APIs for JAX-RS have started us there, with their extra arguments for generic type specs. Apparently, someone thinks that it's so important to be able to write a Collection<X> to the top of JAX-RS to justify adding an asymmetry. Anybody else got a thought here?
