[jboss-jira] [JBoss JIRA] (WFLY-7395) Allow to provide deployment dependency to JNDI resource

Andrew Schmidt (Jira) issues at jboss.org
Thu May 23 10:51:00 EDT 2019


    [ https://issues.jboss.org/browse/WFLY-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737844#comment-13737844 ] 

Andrew Schmidt edited comment on WFLY-7395 at 5/23/19 10:50 AM:
----------------------------------------------------------------

Any update on this issue?   We are experiencing  the same problem.    

Is there possibly a workaround?


was (Author: gabboflabbo):
Any update on this issue?   We are experience  the same problem.    

Is there possibly a workaround?

> Allow to provide deployment dependency to JNDI resource
> -------------------------------------------------------
>
>                 Key: WFLY-7395
>                 URL: https://issues.jboss.org/browse/WFLY-7395
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 10.1.0.Final
>            Reporter: Miroslav Novak
>            Assignee: Jason Greene
>            Priority: Major
>              Labels: user_experience
>
> For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly 10.x
> For example if EJB contains dependency to queue registered in JNDI:
> {code}
> @Resource(mappedName = "java:/jms/queue/OutQueue")
> private Queue outQueue;
> {code}
> then it would not get deployed when OutQueue is not present. Purpose of this feature request is to add possibility to provide such dependency in the way as @org.jboss.annotation.ejb.Depends did.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list