[jboss-jira] [JBoss JIRA] (JBADMCON-174) Add feature in management console to define JNDI bindings from management console

Anurag Debnath (JIRA) jira-events at lists.jboss.org
Wed Nov 6 06:32:02 EST 2013


     [ https://issues.jboss.org/browse/JBADMCON-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anurag Debnath deleted JBADMCON-174:
------------------------------------

    
> Add feature in management console to define JNDI bindings from management console
> ---------------------------------------------------------------------------------
>
>                 Key: JBADMCON-174
>                 URL: https://issues.jboss.org/browse/JBADMCON-174
>             Project: JBoss Admin Console
>          Issue Type: Feature Request
>            Reporter: Abhijit Humbe
>
> . Proposed title of this feature request
> Grant access permission for sub packages to role 'package.admin'
> 2. Who is the customer behind the request?
> Account:Biomerieux (acct #643034)
> TAM customer: No
> SRM customer: No
> Strategic: No
> 3. What is the nature and description of the request?
> Customer want to define specific JNDI bindings from management console.
> Through the management interface, the Profile ==> Container ==> Naming does not show up.
> 4. Why does the customer need this? (List the business requirements here)
> Customer dont want to use CLI command for this,running CLI command remotely means there is a component deployed on remote machine.
> There are several dependencies on this like Java being the biggest one, network...etc
> customer want to perform all task from admin console only.
> 5. How would the customer like to achieve this? (List the functional requirements here)
> Add "Naming" field(like EJB 3, EE,..etc) under "Profile ==> Container" in management console to specify JNDI bindings.
> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
> 7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
> 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
> TODO
> 9. Is the sales team involved in this request and do they have any additional input?
>  
> 10. List any affected packages or components.
> JBoss Admin console
> 11. Would the customer be able to assist in testing this functionality if implemented?
>  

--
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


More information about the jboss-jira mailing list