[
https://issues.apache.org/jira/browse/DELTASPIKE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798983#comment-15798983
]
Mark Struberg commented on DELTASPIKE-1228:
-------------------------------------------
But 8.5.5.9 is still shipped with OWB. Or do you use Liberty? Liberty provides
both Weld and OWB.
In any case it sadly won't work anyway I fear :(
Reason is that you not only need to start the CDI context but also various
ThreadLocals like the EJB SessionContext, TransactionSynchronisationRegistry,
etc.
In case of WAS I suggest you use a @Singleton EJB with an @Asynchronous method
and inside of it you can call CDI beans without any problems.
Please note that @SessionScoped is not applicable for non-Servlet threads
anyway. It will almost always give you a ContextNotActiveException. This has
nothing to do with WAS and not even with CDI (the same restriction exists for
e.g. JSF @SessionScoped and EJBs).
> ContextControl does not work in Websphere AS
> --------------------------------------------
>
> Key: DELTASPIKE-1228
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1228
> Project: DeltaSpike
> Issue Type: Bug
> Affects Versions: 1.7.1
> Environment: Websphere 8.5.5.9
> Reporter: Matthias Wronka
>
> I´m getting an Exception in Websphere Application Server 8.5.5.9 when I try
> to start the SessionScope like this using ContextControl:
> {code:java}
> @Inject
> private ContextControl contextControl
> private void doSth() {
> contextControl.startContext(SessionScoped.class);
> }
> {code}
> The exception is:
> {code}
> java.lang.NoClassDefFoundError: org/apache/webbeans/config/WebBeansContext at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.getContextsService(OpenWebBeansContextControl.java:242)
> at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.startSessionScope(OpenWebBeansContextControl.java:154)
> at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.startContext(OpenWebBeansContextControl.java:80)
>
> {code}
> I think this is because of a rather old owb-implementations, that Websphere
> uses. I found the missing class in another package:
> org/apache/webbeans/*context*/WebBeansContext.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)