[JBoss JIRA] (IPROTO-87) Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass
by Adrian Nistor (Jira)
[ https://issues.jboss.org/browse/IPROTO-87?page=com.atlassian.jira.plugin.... ]
Adrian Nistor reassigned IPROTO-87:
-----------------------------------
Assignee: Adrian Nistor
> Prevent auto-import of java classes that are not explicitly added to ProtoSchemaBuilder.addClass
> -------------------------------------------------------------------------------------------------
>
> Key: IPROTO-87
> URL: https://issues.jboss.org/browse/IPROTO-87
> Project: Infinispan ProtoStream
> Issue Type: Enhancement
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Priority: Major
> Fix For: 4.3.0.Alpha1
>
>
> The classes of the fields of already added classes are also automatically picked up now even if they are not explicitly added with addClass. This behaviour is usually very helpful but there might be use cases where we want explicit control of classes and everything that was not added explicitly should cause an exception. A config flag should be added for this. The current behaviour should remain the default is the flag is not specified.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9965) HotRodRemoteCache*IT.testDataConversionsWithDefaultRemoteCache failures
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-9965:
-------------------------------------
Summary: HotRodRemoteCache*IT.testDataConversionsWithDefaultRemoteCache failures
Key: ISPN-9965
URL: https://issues.jboss.org/browse/ISPN-9965
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Server
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 10.0.0.Beta1
expected:<<[]string>Hello!</strin...> but was:<<[?xml version='1.0' encoding='UTF-8'?><]string>Hello!</strin...>
Using the StAX driver with xstream has added the xml prolog to the xml responses.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of Wildfly
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9964:
-------------------------------
Sprint: Sprint 10.0.0.Beta1
> Logging incompatibility when deploying modules on older versions of Wildfly
> ---------------------------------------------------------------------------
>
> Key: ISPN-9964
> URL: https://issues.jboss.org/browse/ISPN-9964
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final
>
>
> Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of Wildfly
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9964:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6676
> Logging incompatibility when deploying modules on older versions of Wildfly
> ---------------------------------------------------------------------------
>
> Key: ISPN-9964
> URL: https://issues.jboss.org/browse/ISPN-9964
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final
>
>
> Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of Wildfly
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9964:
-------------------------------
Status: Open (was: New)
> Logging incompatibility when deploying modules on older versions of Wildfly
> ---------------------------------------------------------------------------
>
> Key: ISPN-9964
> URL: https://issues.jboss.org/browse/ISPN-9964
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final
>
>
> Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of Wildfly
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9964:
-------------------------------
Description: Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists. (was: Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.)
> Logging incompatibility when deploying modules on older versions of Wildfly
> ---------------------------------------------------------------------------
>
> Key: ISPN-9964
> URL: https://issues.jboss.org/browse/ISPN-9964
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final
>
>
> Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ISPN-9963) Restructure Documentation Titles
by Don Naro (Jira)
Don Naro created ISPN-9963:
------------------------------
Summary: Restructure Documentation Titles
Key: ISPN-9963
URL: https://issues.jboss.org/browse/ISPN-9963
Project: Infinispan
Issue Type: Enhancement
Components: Documentation-Core
Affects Versions: 10.0.0.Beta1
Reporter: Don Naro
Assignee: Don Naro
This enhancement is to restructure the layout of the documentation directory and set up the titles for the 10.0 community release.
The goal is to have a buildable set of titles created from existing content. The current chapter files from ISPN 9.x books are moved into the /topics directory where they can start to be broken down into sections and smaller units of reusable information.
Definition of done for this issue:
- Community and productized titles build successfully.
- Community website updated to handle new titles.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months