[JBoss JIRA] (AS7-2171) Revisit deployment triggering subsystem startup
by Thomas Diesler (Created) (JIRA)
Revisit deployment triggering subsystem startup
-----------------------------------------------
Key: AS7-2171
URL: https://issues.jboss.org/browse/AS7-2171
Project: Application Server 7
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Currently the RestEasyIntegrationTestCase deploys a JAXRS endpoint that integrates with an OSGi service. The endoint deployment does not trigger the OSGi subsystem to start up, but depends on the compendium being deployed. The compendium gets deployed during OSGi subsystem startup.
There is currently no way for a deployment foo to declare a dependency on deployment bar when bar gets deployed during subsystem startup, which gets triggered by deployment foo.
OSGi has the notion of dynamic package import which seems to be required here for non-osgi deployments
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-5074) @Inject'ed bean at another @Singleton is null on @PostConstruct (both with @Startup)
by Bruno Borges (JIRA)
Bruno Borges created AS7-5074:
---------------------------------
Summary: @Inject'ed bean at another @Singleton is null on @PostConstruct (both with @Startup)
Key: AS7-5074
URL: https://issues.jboss.org/browse/AS7-5074
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld, EJB
Affects Versions: 7.1.1.Final
Reporter: Bruno Borges
Assignee: Stuart Douglas
module-a.jar and module-b.jar are both TL (top-level) delpoyments on JBoss AS 7.1.1
* module-a.jar has a @Singleton/@Startup named SharedBean
* module-b.jar has a @Singleton/@Startup named Bootstrap
module-b.jar depends on module-a.jar through jboss-deployment-structure.xml:
<jboss-deployment-structure>
<delpoyment>
<dependencies>
<module name="deployment.module-a.jar" />
</dependencies>
</deployment>
</jboss-deployment-structure>
When I enable module-a.jar, SharedBean is started fine (it has a @PostConstruct that logs its state)
When I enable module-b.jar, Bootstrap fails checking the @Inject'ed SharedBean on its @PostConstruct
Files:
-------------------------
# module-a.jar
@Startup
@Singleton
public class SharedBean {
@PostConstruct
public void started() {
LOGGER.info("SharedBean has started");
}
}
-------------------------
# module-b.jar
@Startup
@Singleton
public class Bootstrap {
@Inject
private SharedBean sharedBean;
@PostConstruct
public void started() {
LOGGER.info("sharedBean is null? " + (sharedBean == null));
}
}
There's no ClassNotFoundException or NoClassDefFoundError. The bean is just not injected correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-5088) Weblogic EJB Lookup fails from JBoss AS
by Badal Pradhan (JIRA)
Badal Pradhan created AS7-5088:
----------------------------------
Summary: Weblogic EJB Lookup fails from JBoss AS
Key: AS7-5088
URL: https://issues.jboss.org/browse/AS7-5088
Project: Application Server 7
Issue Type: Bug
Environment: JBoss AS 7.1.0.Final
EJB Deployed in Weblogic 10
OS - Windows XP
JDK - jdk160_05 (Used by jboss)
Reporter: Badal Pradhan
I am trying to access EJB deployed in Weblogic 10 by its RemoteInterface from JBoss.
My initial context config for lookup is as below:
Hashtable<String,String> wlContextEnv = new Hashtable<String,String>();
wlContextEnv.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
wlContextEnv.put(Context.PROVIDER_URL, "t3://localhost:7001");
wlInitialContext = new InitialContext(wlContextEnv);
During access the bean it throws the below exception:
java.lang.LinkageError: Failed to link weblogic/corba/client/cluster/ORBSocketFactory
.....
Caused by: java.lang.ClassNotFoundException: com.sun.corba.se.spi.legacy.connection.ORBSocketFactory
Since the above class belongs to jdk rt.jar then what is the issue here? Am I missed any config for it.
Note: I have wlclient.jar in my ear/lib.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months