Commentary: OASIS is on the wrong path with the SCA standardization effort
I am sort of on an SCA kick here. I just saw this post from Dick Weisinger of Formtek. In it he questions the approach OASIS is taking with the SCA family of specifications. Dick implies that SOA is already too complex for most people, and creating six new standards isn't going to simplify anything. I would take that one further and question the very structure of SCA itself. It seems that there are a couple of loosely-related technology areas covered in the SCA specs, why are they all smashed together?
Why isn't the portable communications API for Java being specified in the JCP, where such things are "supposed to' be specified?
Why is that portable API combined in a single spec with a description language for composite artifacts (SCDL)?