[JBoss JIRA] (ISPN-6386) Remove max-entries from the documentation
by sw0x2A sw0x2A (JIRA)
[ https://issues.jboss.org/browse/ISPN-6386?page=com.atlassian.jira.plugin.... ]
sw0x2A sw0x2A commented on ISPN-6386:
-------------------------------------
This also applies for ISPN 8.2.1. max-entries is mentioned in [docs|http://infinispan.org/docs/8.2.x/user_guide/user_guide.html] but ISPN throws exception when max-entries is used in config:
{code}
16:09:28,709 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed
to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_111]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[144,21]
Message: WFLYCTL0197: Unexpected attribute 'max-entries' encountered
at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseEviction(InfinispanSubsystemXMLReader.java:1108)
at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseCacheElement(InfinispanSubsystemXMLReader.java:932)
at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseDistributedCache(InfinispanSubsystemXMLReader.java:804)
at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseContainer(InfinispanSubsystemXMLReader.java:281)
at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:95)
at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:68)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]
... 3 more
{code}
Works if I replace max-entries attribute with size.
> Remove max-entries from the documentation
> -----------------------------------------
>
> Key: ISPN-6386
> URL: https://issues.jboss.org/browse/ISPN-6386
> Project: Infinispan
> Issue Type: Task
> Components: Documentation-Core
> Reporter: Sebastian Łaskawiec
> Assignee: Adrian Nistor
> Fix For: 9.0.0.CR1
>
>
> In ISPN 9 we use size instead.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (ISPN-7426) Upgrade to Hibernate Search 5.7.0.CR1 and Hibernate ORM 5.2.7.Final
by Sanne Grinovero (JIRA)
Sanne Grinovero created ISPN-7426:
-------------------------------------
Summary: Upgrade to Hibernate Search 5.7.0.CR1 and Hibernate ORM 5.2.7.Final
Key: ISPN-7426
URL: https://issues.jboss.org/browse/ISPN-7426
Project: Infinispan
Issue Type: Component Upgrade
Components: Build process, Embedded Querying
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 9.0.0.CR1, 9.0.0.Final
The main goal of this issue is to upgrade to the Hibernate Search 5.7.x family.
Hibernate ORM needs to be aligned as we use the combination in some tests; they don't strictly need to be aligned for our functional purposes but it makes the upgrade much simpler.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (ISPN-7425) Enable admins to delete configuration subsections
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7425?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7425:
--------------------------------------
Motivation: we need to resolve JDG-695 but in a consistent approach
> Enable admins to delete configuration subsections
> -------------------------------------------------
>
> Key: ISPN-7425
> URL: https://issues.jboss.org/browse/ISPN-7425
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 9.0.0.Beta2
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.CR1
>
>
> We need to add the ability to remove configuration subsections (locking, expiration etc) and make it consistent across configuration screens.
> UI perspective: We could have a delete icon (red cross or trash can etc) in the "panel-title" div of the section that a user is editing. If the user chooses to delete this sections config, then they should be presented with a message screen saying "<section> has not been defined, would you like to define this now?" similar to how we ask users to define container security when they click on the security section. Similarly, if a user loads an existing config with a section undefined, the aforementioned message should be displayed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (ISPN-7425) Enable admins to delete configuration subsections
by Vladimir Blagojevic (JIRA)
Vladimir Blagojevic created ISPN-7425:
-----------------------------------------
Summary: Enable admins to delete configuration subsections
Key: ISPN-7425
URL: https://issues.jboss.org/browse/ISPN-7425
Project: Infinispan
Issue Type: Enhancement
Components: Console
Affects Versions: 9.0.0.Beta2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 9.0.0.CR1
We need to add the ability to remove configuration subsections (locking, expiration etc) and make it consistent across configuration screens.
UI perspective: We could have a delete icon (red cross or trash can etc) in the "panel-title" div of the section that a user is editing. If the user chooses to delete this sections config, then they should be presented with a message screen saying "<section> has not been defined, would you like to define this now?" similar to how we ask users to define container security when they click on the security section. Similarly, if a user loads an existing config with a section undefined, the aforementioned message should be displayed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months