[
https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17700:
-------------------------------------
The code that is being run to find the class is:
{code}
public static synchronized KeyManager getInstance() {
if (keyManager != null)
return keyManager;
final String cn = System.getProperty(
"de.schlichtherle.key.KeyManager",
getDefaultKeyManagerClassName());
try {
final Class c = Thread.currentThread()
.getContextClassLoader().loadClass(cn);
keyManager = (KeyManager) c.newInstance();
} catch (RuntimeException ex) {
throw ex;
} catch (Exception ex) {
throw new UndeclaredThrowableException(ex);
}
return keyManager;
}
{code}
I can't know for sure why this is happening, but, let's assume that the publish
event is starting in a Job, and jobs are run by workers. Perhaps archives.core should be
sure to 'start' when any of its classes are referenced, and archives.core's
start method should be sure to initialize the framework properly?
Cannot deploy jsf war with eclipse luna and jboss 7.1.x
-------------------------------------------------------
Key: JBIDE-17700
URL:
https://issues.jboss.org/browse/JBIDE-17700
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
Reporter: Oliver Pfau
Priority: Critical
When I publish my war to jboss 7.1 the following error occurs:
An internal error occurred during: "Publishing to JBoss AS 7.1...".
Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)