[
https://issues.apache.org/jira/browse/OPENEJB-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534217#comment-13534217
]
Romain Manni-Bucau commented on OPENEJB-1969:
---------------------------------------------
changed a bit the producer (used another scope) can you test it please? not
sure why we would need to create two initial contexts...
about java:global if you can't bind inside that's not a bug (well we don't want
to prevent it but that's not in the spec). It is standard ONLY for EJBs. It
means even datasources doesn't have to respect it (yes yes, i agree that's a
pity :p)
if you need i force a deployment just ask otherwise it will be done tomorrow.
If you build from sources only arquillian-openejb-embedded-4 was updated
> OpenEJBDeployableContainer has InstanceProducer<Context>
> --------------------------------------------------------
>
> Key: OPENEJB-1969
> URL: https://issues.apache.org/jira/browse/OPENEJB-1969
> Project: OpenEJB
> Issue Type: Improvement
> Components: arquillian
> Affects Versions: 4.5.1
> Reporter: Trevor Baker
> Priority: Minor
> Fix For: 4.5.2
>
> Attachments: OPENEJB-1969.patch
>
>
> Nice to have
> In OpenEJBDeployableContainer
> Change this:
> private InitialContext initialContext;
> To this:
> @Inject
> @DeploymentScoped // I'm assuming DeploymentScoped .. is there a better
> one to use?
> private InstanceProducer<Context> initialContext;
> So other Arquillian stuff can access the context with:
> @Inject
> private Instance<Context> ctx;
>
> Instead of new InitialContext().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
