[embjopr-issues] [JBoss JIRA] Assigned: (EMBJOPR-225) Service Binding Manager / Config tab / Active Binding Set Name: JOPR description used.

[Ondrej Zizka (JIRA)]

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

Ondrej Zizka reassigned EMBJOPR-225:
------------------------------------

    Assignee: Charles Crouch


Will this get fixed?

> Service Binding Manager  / Config tab / Active Binding Set Name: JOPR description used.
> ---------------------------------------------------------------------------------------
>
>                 Key: EMBJOPR-225
>                 URL: https://issues.jboss.org/browse/EMBJOPR-225
>             Project: Embedded Jopr
>          Issue Type: Bug
>         Environment: Test: testServiceBindingManagerConfigurationTest()
>            Reporter: Ondrej Zizka
>            Assignee: Charles Crouch
>            Priority: Minor
>
> (23:07:42) ozizka: ips, this description does not apply to EmbJopr: 
> To be able to monitor the server again after the restart you have to update the "Naming Provider Url" in the "Connection" subtab in the "Inventory" of the Application Server
> (23:08:29) ozizka: Perhaps there should be some optional emb-jopr specific description.
> (23:08:46) ozizka: and when not set,  description for JOPR would be used
> 23:10
> (23:10:11) ips: ozizka: yeah, we could either add something like that or we could just update the description. eg:
> (23:11:12) ips: If you are using RHQ, Jopr, or JON, then to be able to...
> (23:12:20) ips: i don't love either solution. the 1st is bad because it requires the plugin developer to know about the environments it might be running in
> (23:12:45) ips: and the 2nd makes the descriptions complicated and overly verbose..

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira