Patrick Forhan wrote:
We're getting ready to roll out a new set of core bundles for our
application platform... updating to the following:
Felix core 1.0.4
shell 1.0.1
bundlerepository 1.0.3
scr 1.04
eventadmin 1.0.0
(... and pax-confman and pax-logging)
Everything went pretty smoothly, except for Felix core. We had three
issues, possibly all related:
- RepositoryAdmin got set, the removed, then set, which caused an NPE
in one of our declared service classes
Not sure I have enough information to comment on this. Can you explain
it more?
- logging seemed to be going through a mix of PAX-logging and the
default Felix logger
Well, we were running into some deadlocking issues when Felix was
calling out to external Log Services, so for now we disabled that
feature since it was causing difficulties for people.
- we could no longer load images from a Class.getResource() URL like
bundle://56.0:1/org/bjc/pt2/i18n/mock/background.png
Not sure why that would be the case. Again, we probably need more
specific details.
We rolled felix back to 1.0.3 and these problems went away. Is there
some reason for this? Do we need 1.0.4?
I would say upgrading definitely makes sense. You probably even should
consider Felix 1.2.0 which is currently under vote for release now.
-> richard
Thanks,
Pat.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
