ok, thanks
Richard S. Hall wrote:
These messages are purely informational, which is why they are DEBUG.
For normal bundle resolution, these messages will get logged if there
is a "uses" constraint violation detected and we will try a different
candidate. If all candidates result in "uses" constraint violations,
then you will get a BundleException saying the bundle could not resolve.
For dynamic imports, you may also see these messages, but in this case
if no candidates can be resolved then it is ignored and the dynamic
import is not satisfied.
-> richard
Pierre De Rop wrote:
Hi all,
I discovered the following traces with the fwk debugger (I use the
latest trunk + felix.log.level=4)
DEBUG: Constraint violation for 91.0 detected; module can see
javax.servlet.http from [45.0] and javax.servlet.http from [54.0]
DEBUG: Constraint violation for 91.0 detected; module can see
javax.servlet.http from [45.0] and javax.servlet.http from [54.0]
Could you please describe the conditions when the fwk logs such
messages ?
I guess this is a story of dynamic import resolution and the "uses"
clause ...
Is it just an informational/debug message, or does this message bring
to light a real problem from my bundles import/export headers ?
Many thanks;
/pierre
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
