Bug 312091

Description Jeff McAffer 2010-05-07 11:45:27 EDT

From time to time bundles have optional dependencies. Often the code in the bundle directly references the optional classes and is structured to either optionally fallback if the requested class is not available or to simply not try to access the optional classes when it should not.

It would be interesting to have some PDE help on ensuring that the optional dependencies really are optional.  For example, I recently had an issue in ECF where a class returned IProxyData in the method signature.  IProxyData came from the o.e.core.net.proxy package which was optionally imported. Since the  proxy type was referenced in the method signature, the class would not load at all if IProxyData was not around. This was a programming error that was not caught because the team always had proxy support available.

It may be hard to distinquish real references from optoinal (for example, if the referencing type was simply not used when proxy support was not around, the reference would be fine).  However, perhaps with some markup developers would be able to explicitly mark a class as optionally referencing a type (i.e., constructs that would prevent the class from loading would be errors).  There may be more error states we can detect in the tooling...

The value in adding this sort of tooling is that the problems that arise are often very difficult to find when they are happening and challenging to prevent without running in all manner of different configurations (which admittedly the test cases should catch but...)