[JBoss JIRA] (ISPN-6559) Provide module for Infinispan Directory that satisfies the slot "for-hibernatesearch-5.5"
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6559?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6559:
------------------------------------
Fix Version/s: 8.2.2.Final
> Provide module for Infinispan Directory that satisfies the slot "for-hibernatesearch-5.5"
> -----------------------------------------------------------------------------------------
>
> Key: ISPN-6559
> URL: https://issues.jboss.org/browse/ISPN-6559
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 8.1.3.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 8.2.2.Final
>
>
> Wildfly 10.0.0 internal hibernate search engine has an optional dependency to
> {code:xml}
> <!-- Infinispan extensions - provided as separate download by the Infinispan project -->
> <module name="org.infinispan.hibernate-search.directory-provider" slot="for-hibernatesearch-5.5" services="import" optional="true"/>
> {code}
> But as described in ISPN-6537 this dependency is not correctly satisfied by the modules zip, forcing users who depends on hibernate from wildfly to use the ispn-8.1 slot and thus another version of hibernate search
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (ISPN-6559) Provide module for Infinispan Directory that satisfies the slot "for-hibernatesearch-5.5"
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6559?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reassigned ISPN-6559:
---------------------------------------
Assignee: Gustavo Fernandes
> Provide module for Infinispan Directory that satisfies the slot "for-hibernatesearch-5.5"
> -----------------------------------------------------------------------------------------
>
> Key: ISPN-6559
> URL: https://issues.jboss.org/browse/ISPN-6559
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 8.1.3.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> Wildfly 10.0.0 internal hibernate search engine has an optional dependency to
> {code:xml}
> <!-- Infinispan extensions - provided as separate download by the Infinispan project -->
> <module name="org.infinispan.hibernate-search.directory-provider" slot="for-hibernatesearch-5.5" services="import" optional="true"/>
> {code}
> But as described in ISPN-6537 this dependency is not correctly satisfied by the modules zip, forcing users who depends on hibernate from wildfly to use the ispn-8.1 slot and thus another version of hibernate search
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (ISPN-6540) Management console doesn't display cache containers correctly if there are two containers with the same name
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6540?page=com.atlassian.jira.plugin.... ]
Roman Macor updated ISPN-6540:
------------------------------
Attachment: config_with_remoteSite.zip
[~vblagojevic] about the PR, if you add remote site to one container, both containers display the same site in cache container view. Sometimes N/A sometimes BRN - the name of the remote site.
I've added configuration with remote site.
> Management console doesn't display cache containers correctly if there are two containers with the same name
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6540
> URL: https://issues.jboss.org/browse/ISPN-6540
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: configs.zip, config_with_remoteSite.zip, Screenshot-containersWithSameName.png, Screenshot-detalPageForBothContainers.png
>
>
> When we have two containers with the same name on different clusters some values are displayed correctly - #caches, name, clustering-info, but some are not - endpoints, sites.
> Additionally, clicking on either of containers display the same information, even though containers are configured differently.
> Please see the screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month