[JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plug... ]
Eric Wittmann updated OVERLORD-140:
-----------------------------------
Assignee: David virgil naranjo (was: Eric Wittmann)
> Ensure consistent fav icon for all overlord apps
> ------------------------------------------------
>
> Key: OVERLORD-140
> URL: https://issues.jboss.org/browse/OVERLORD-140
> Project: Overlord
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
>
> Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page:
> {code}
> <link rel="icon" type="image/png" href="images/favicon.png"></link>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps
by Eric Wittmann (JIRA)
Eric Wittmann created OVERLORD-140:
--------------------------------------
Summary: Ensure consistent fav icon for all overlord apps
Key: OVERLORD-140
URL: https://issues.jboss.org/browse/OVERLORD-140
Project: Overlord
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page:
{code}
<link rel="icon" type="image/png" href="images/favicon.png"></link>
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RTGOV-552) EAP JMS connection factory not available
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-552?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-552.
------------------------------
Resolution: Done
> EAP JMS connection factory not available
> ----------------------------------------
>
> Key: RTGOV-552
> URL: https://issues.jboss.org/browse/RTGOV-552
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> With the new approach for obtaining services via ServiceRegistry, and the initialisation being done via annotations, periodically the JMSEPNManagerImpl attempts to obtain the JMS connection factory from JNDI before it is available.
> The initConsumers property can be used to determine whether a server based solution (i.e. using MDBs) is being used - possibly if initConsumers is false, then get the MDB to explicitly trigger the initialization?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (SRAMP-545) Provide ability to delete ontology via UI
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-545?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-545:
-----------------------------------
>From Eric:
{quote}
Note that ontology delete may fail if there are artifacts that use it
(referential integrity). Brett you might want to check on that, I can't
remember!
{quote}
> Provide ability to delete ontology via UI
> -----------------------------------------
>
> Key: SRAMP-545
> URL: https://issues.jboss.org/browse/SRAMP-545
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: UI
> Affects Versions: 0.5.0.Final
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Critical
> Fix For: 0.6.0
>
>
> There is no way how to delete ontology in S-RAMP UI. One would expect such functionality in Ontology Management section.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months