[JBoss JIRA] (ISPN-10456) Remove ExternalPojo Interface and ExternallyMarshallable
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-10456:
-----------------------------------
Summary: Remove ExternalPojo Interface and ExternallyMarshallable
Key: ISPN-10456
URL: https://issues.jboss.org/browse/ISPN-10456
Project: Infinispan
Issue Type: Sub-task
Components: Core
Affects Versions: 10.0.0.Beta4
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 10.0.0.Beta5
ExternallyMarshallable & ExternalPojo don't really make sense with the latest marshaller changes (ISPN-10354), as the Global & Persistence marshallers can only handle types they know about. Unknown types are always handled by the user marshaller and when JavaSerializationMarshaller is used (the default now) the user has to explicitly add classes to the white list.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (ISPN-10450) ServerNG: improve the initial experience
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10450?page=com.atlassian.jira.plugin... ]
Ryan Emerson resolved ISPN-10450.
---------------------------------
Resolution: Done
> ServerNG: improve the initial experience
> ----------------------------------------
>
> Key: ISPN-10450
> URL: https://issues.jboss.org/browse/ISPN-10450
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> A list of various items to improve the initial serverng experience:
> * Localizable help messages for server and user-tool
> * Stack selection via the command-line (-j)
> * Port binding via the command-line (-p)
> * Make default configuration (infinispan.xml) clustered
> * Add non-clustered configuration infinispan-local.xml
> * Disable TLS/keystore and memcached connector in default config
> * Refactor shells scripts extracting common logic to common.sh
> * Add a README.md file to get users started
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (IPROTO-101) Enum values with same name in different classes clash
by Nistor Adrian (Jira)
[ https://issues.jboss.org/browse/IPROTO-101?page=com.atlassian.jira.plugin... ]
Nistor Adrian resolved IPROTO-101.
----------------------------------
Fix Version/s: 4.3.0.Alpha10
Resolution: Rejected
Rejecting it, works as designed. See the other comments.
> Enum values with same name in different classes clash
> -----------------------------------------------------
>
> Key: IPROTO-101
> URL: https://issues.jboss.org/browse/IPROTO-101
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Affects Versions: 4.3.0.Alpha6
> Reporter: Ryan Emerson
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 4.3.0.Alpha10
>
>
> {code:java}
> @ProtoName("TakeSiteOfflineResponse")
> public enum TakeSiteOfflineResponse {
> @ProtoEnumValue(number = 1)
> NO_SUCH_SITE,
> @ProtoEnumValue(number = 2)
> ALREADY_OFFLINE,
> @ProtoEnumValue(number = 3)
> TAKEN_OFFLINE
> }
> @ProtoName("BringSiteOnlineResponse")
> public enum BringSiteOnlineResponse {
> @ProtoEnumValue(number = 1)
> NO_SUCH_SITE,
> @ProtoEnumValue(number = 2)
> ALREADY_ONLINE,
> @ProtoEnumValue(number = 3)
> BROUGHT_ONLINE
> }
> {code}
> Results in:
> {code:java}
> Enum value org.infinispan.test.TakeSiteOfflineResponse.NO_SUCH_SITE clashes with enum value org.infinispan.test.BringSiteOnlineResponse.NO_SUCH_SITE
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (IPROTO-101) Enum values with same name in different classes clash
by Nistor Adrian (Jira)
[ https://issues.jboss.org/browse/IPROTO-101?page=com.atlassian.jira.plugin... ]
Nistor Adrian commented on IPROTO-101:
--------------------------------------
And you will be delighted to see the output of this ...
{code}
package test_enums_package;
enum TestEnum1 {
YES = 1;
NO = 0;
MAYBE = 10;
}
enum TestEnum2 {
TestEnum1 = 4;
}
{code}
> Enum values with same name in different classes clash
> -----------------------------------------------------
>
> Key: IPROTO-101
> URL: https://issues.jboss.org/browse/IPROTO-101
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Affects Versions: 4.3.0.Alpha6
> Reporter: Ryan Emerson
> Assignee: Nistor Adrian
> Priority: Major
>
> {code:java}
> @ProtoName("TakeSiteOfflineResponse")
> public enum TakeSiteOfflineResponse {
> @ProtoEnumValue(number = 1)
> NO_SUCH_SITE,
> @ProtoEnumValue(number = 2)
> ALREADY_OFFLINE,
> @ProtoEnumValue(number = 3)
> TAKEN_OFFLINE
> }
> @ProtoName("BringSiteOnlineResponse")
> public enum BringSiteOnlineResponse {
> @ProtoEnumValue(number = 1)
> NO_SUCH_SITE,
> @ProtoEnumValue(number = 2)
> ALREADY_ONLINE,
> @ProtoEnumValue(number = 3)
> BROUGHT_ONLINE
> }
> {code}
> Results in:
> {code:java}
> Enum value org.infinispan.test.TakeSiteOfflineResponse.NO_SUCH_SITE clashes with enum value org.infinispan.test.BringSiteOnlineResponse.NO_SUCH_SITE
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (IPROTO-101) Enum values with same name in different classes clash
by Nistor Adrian (Jira)
[ https://issues.jboss.org/browse/IPROTO-101?page=com.atlassian.jira.plugin... ]
Nistor Adrian commented on IPROTO-101:
--------------------------------------
Please test with this proto file by running it through protoc: {quote}protoc test_enums.proto -o/tmp/protoc_out.bin {quote}
{code}
// File test_enums.proto
package test_enums_package;
enum TestEnum1 {
YES = 1;
NO = 0;
MAYBE = 10;
}
enum TestEnum2 {
YES = 4;
NOPE = 5;
}
{code}
The output is self-explanatory (C++ scoping rules, the 80's are calling...):
{quote}
test_enums.proto:11:3: "YES" is already defined in "test_enums_package".
test_enums.proto:11:3: Note that enum values use C++ scoping rules, meaning that enum values are siblings of their type, not children of it. Therefore, "YES" must be unique within "test_enums_package", not just within "TestEnum2".
{quote}
> Enum values with same name in different classes clash
> -----------------------------------------------------
>
> Key: IPROTO-101
> URL: https://issues.jboss.org/browse/IPROTO-101
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Affects Versions: 4.3.0.Alpha6
> Reporter: Ryan Emerson
> Assignee: Nistor Adrian
> Priority: Major
>
> {code:java}
> @ProtoName("TakeSiteOfflineResponse")
> public enum TakeSiteOfflineResponse {
> @ProtoEnumValue(number = 1)
> NO_SUCH_SITE,
> @ProtoEnumValue(number = 2)
> ALREADY_OFFLINE,
> @ProtoEnumValue(number = 3)
> TAKEN_OFFLINE
> }
> @ProtoName("BringSiteOnlineResponse")
> public enum BringSiteOnlineResponse {
> @ProtoEnumValue(number = 1)
> NO_SUCH_SITE,
> @ProtoEnumValue(number = 2)
> ALREADY_ONLINE,
> @ProtoEnumValue(number = 3)
> BROUGHT_ONLINE
> }
> {code}
> Results in:
> {code:java}
> Enum value org.infinispan.test.TakeSiteOfflineResponse.NO_SUCH_SITE clashes with enum value org.infinispan.test.BringSiteOnlineResponse.NO_SUCH_SITE
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (IPROTO-101) Enum values with same name in different classes clash
by Nistor Adrian (Jira)
[ https://issues.jboss.org/browse/IPROTO-101?page=com.atlassian.jira.plugin... ]
Nistor Adrian commented on IPROTO-101:
--------------------------------------
I could not find where in the protobuf spec is this specified, but I do know that this works as intended so I will reject this bug.
> Enum values with same name in different classes clash
> -----------------------------------------------------
>
> Key: IPROTO-101
> URL: https://issues.jboss.org/browse/IPROTO-101
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Affects Versions: 4.3.0.Alpha6
> Reporter: Ryan Emerson
> Assignee: Nistor Adrian
> Priority: Major
>
> {code:java}
> @ProtoName("TakeSiteOfflineResponse")
> public enum TakeSiteOfflineResponse {
> @ProtoEnumValue(number = 1)
> NO_SUCH_SITE,
> @ProtoEnumValue(number = 2)
> ALREADY_OFFLINE,
> @ProtoEnumValue(number = 3)
> TAKEN_OFFLINE
> }
> @ProtoName("BringSiteOnlineResponse")
> public enum BringSiteOnlineResponse {
> @ProtoEnumValue(number = 1)
> NO_SUCH_SITE,
> @ProtoEnumValue(number = 2)
> ALREADY_ONLINE,
> @ProtoEnumValue(number = 3)
> BROUGHT_ONLINE
> }
> {code}
> Results in:
> {code:java}
> Enum value org.infinispan.test.TakeSiteOfflineResponse.NO_SUCH_SITE clashes with enum value org.infinispan.test.BringSiteOnlineResponse.NO_SUCH_SITE
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months
[JBoss JIRA] (ISPN-9865) Query is failing if custom classes are used inside of the cache
by Nistor Adrian (Jira)
[ https://issues.jboss.org/browse/ISPN-9865?page=com.atlassian.jira.plugin.... ]
Nistor Adrian commented on ISPN-9865:
-------------------------------------
By looking at the provide code I believe this is not really a bug (but did not test that to confirm); it may just be a case of forgetting to add the jar containing the user classes to the <modules> element under the <cache-container> in config. This is something introduced in 9.2 I believe. Read about the <modules> tag here: https://infinispan.org/docs/stable/user_guide/user_guide.html. The jar in question has to be added to the deployment dir of the server manually. I believe that can also be done with CLI also.
> Query is failing if custom classes are used inside of the cache
> ---------------------------------------------------------------
>
> Key: ISPN-9865
> URL: https://issues.jboss.org/browse/ISPN-9865
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, WildFly modules
> Affects Versions: 9.4.5.Final
> Environment: Wildfly server with ISPN modules and ISPN subsystem to configure caches
> Reporter: Wolf-Dieter Fink
> Assignee: Nistor Adrian
> Priority: Major
> Attachments: install1-standalone-local.cli, install2-standalone-local.cli
>
>
> A simple query for a cache which contains User classes will fail for queries with the error below.
> UserData class for the cache:
> public class Test implements Serializable {
> private int testId;
> public Test(){}
> public Test(int myId) {this.testId = myId;}
> public int getTestId() {return animalId;}
> public void setTestId(int testId) { this.testId = testId;}
> }
> Simple EJB for test
> @Singleton
> @Startup
> public class TestInfinispanQuery4EAPConfig {
> @Resource(lookup = "java:jboss/datagrid-infinispan/container/jdg-container/cache/EAPcache")
> private Cache<String, Object> cache;
>
> @PostConstruct
> public void LoadDBToMemory() {
> cache.put("1", new Test(2, 0));
> cache.put("2", new Test(2, 0));
> cache.put("3", new Test(1, 0));
> QueryFactory queryFactory = Search.getQueryFactory(cache);
>
> Query q = queryFactory.from(Test.class).having("testId").eq(2).build();
>
> int size = q.getResultSize();
> System.out.println("result = " + size);
> }
> }
> Caused by: java.lang.IllegalStateException: ISPN028510: Unknown entity name org.infinispan.wfink.web.Test
> at org.infinispan.objectfilter.impl.syntax.parser.QueryResolverDelegateImpl.registerPersisterSpace(QueryResolverDelegateImpl.java:60)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.entityName(QueryResolver.java:6683)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.persisterSpaceRoot(QueryResolver.java:1302)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.persisterSpace(QueryResolver.java:1203)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.persisterSpaces(QueryResolver.java:1144)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.fromClause(QueryResolver.java:1060)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.selectFrom(QueryResolver.java:969)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.querySpec(QueryResolver.java:487)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.queryStatement(QueryResolver.java:388)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.queryStatementSet(QueryResolver.java:308)
> at org.infinispan.objectfilter.impl.ql.parse.QueryResolver.statement(QueryResolver.java:241)
> at org.infinispan.objectfilter.impl.ql.QueryParser.resolve(QueryParser.java:81)
> at org.infinispan.objectfilter.impl.ql.QueryParser.parseQuery(QueryParser.java:69)
> at org.infinispan.objectfilter.impl.syntax.parser.IckleParser.parse(IckleParser.java:19)
> at org.infinispan.query.dsl.embedded.impl.QueryEngine.lambda$parse$1(QueryEngine.java:695)
> at org.infinispan.query.dsl.embedded.impl.QueryCache.lambda$get$ab3121d1$1(QueryCache.java:73)
> at org.infinispan.compat.FunctionMapper.apply(FunctionMapper.java:40)
> at org.infinispan.commands.write.ComputeIfAbsentCommand.perform(ComputeIfAbsentCommand.java:104)
> at org.infinispan.interceptors.impl.CallInterceptor.visitCommand(CallInterceptor.java:29)
> at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextThenAccept(BaseAsyncInterceptor.java:100)
> at org.infinispan.interceptors.impl.EntryWrappingInterceptor.setSkipRemoteGetsAndInvokeNextForDataCommand(EntryWrappingInterceptor.java:672)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 5 months