Yep, this works differently on 2.2 and 2.3+ (c5439801ccea8ea6f0203181679d7831f3e2ffc1). The question is what's the correct behaviour? I would say the deployment should fail (following the way CDI handles unsatisfied dependencies) but with more appropriate message though.
|