BundleB
import javax.security.auth.login.*;
class Serviceb {
public void methodB() {
Configuration.setConfiguration(b);
}
}
--
View this message in context:
http://www.nabble.com/Static-member-question-tp23450349p23450349.html
Sent from the Apach
There is only one singleton because there is only one copy of the
Configuration class in BundleA...assuming both Main and BundleB both
import javax.security.auth.login (i.e., they don't have a private copy
in their bundle) and they are both wired to the same provider of the
package.
-> richar
Just to expand on Richard's explanation a little -
* statics are global within the scope of their classloader
So as Richard says, in your case since the class was loaded by one
classloader, you'll still have a singleton across your JVM
In a case where the same class appears in different bu
Hello everybody,
Recently embedding Felix (Karaf) I ran into the exactly same issue:
http://www.mail-archive.com/d...@felix.apache.org/msg04908.html
While the solution with setting TCL to null works I was wondering
whether this solution remains recommended one?
The issue looks to be fixed also by
4 matches
Mail list logo