- have some Exceptions pre-defined and shared (e.g. for inheritance) while also pre-defining business logic semantics
The concrete issue:
- Create a plain-vanilla OSGi bundle containing service contracts as well as exceptions (annotate one of them)
- Create a hybrid OSGi/JavaEE bundle containing an implementation and try to use the annotated exception
- defined behaviour of the @ApplicationException is not applied
This is due to the fact that the BaseContainer does not find the exception in the list of application-exceptions.
We know that there exists workarounds but that involves modifying probably a lot of artifacts, esp. in a multi-layered, highly modularised application setup where only one of a few very basic shared Exception classes are deemed to provide specific semantics for all implementations.