[
https://issues.apache.org/jira/browse/IGNITE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702791#comment-14702791
]
Pavel Konstantinov commented on IGNITE-1262:
--------------------------------------------
I'm faced with issue related to this ticket
{code}
Failed to serialize object: CacheJdbcPojoStoreFactory
{code}
To reproduce:
1) Use H2
2) create table person (id int primary key, name varchar(100))
3) generate java- and xml-files using ignite-schema-import (ISI) utility
4) prepare cache using Ignite Web Control Center (WCC) (http://104.197.2.239)
5) replace cacheTypeMetadata in cache configuration generated by WCC with
cacheTypeMetadata generated with ISI
6) create runnable example and put to the cache some Persons
7) select * from Person in H2 should return all Persons
> CacheJdbcPojoStoreFactory issues
> --------------------------------
>
> Key: IGNITE-1262
> URL: https://issues.apache.org/jira/browse/IGNITE-1262
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.1.4
> Reporter: Valentin Kulichenko
> Assignee: Andrey Gura
> Labels: usability
> Fix For: ignite-1.4
>
>
> # {{appContext}} should be transient.
> # {{dataSrc}} in factory looks incorrect. It's transient and is always null
> on remote nodes. How is it supposed to be used?
> # Really strange thing with dialects. They are not serializable for no good
> reason, but can be set in factory. Moreover, there is
> {{CacheJdbcPojoStoreFactorySelfTest.testSerializable()}} which checks that H2
> dialect can't be used (???). I think we should make {{JdbcDialect}} implement
> {{Serializable}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
