Thank you Vyacheslav,
Case closed. It works fine in 2.8.0 if service extended Test class
implements Serializable.
/Keep up good work "Igniters"/
-
Regards
Cristian Gheorghe Florescu
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Now I see.
Your parent class (called Test in your example) *should implement
'Serializable' interface*, this will help for your case.
We changed default marshaller for services in 2.8, because they have to
be 'Serializable' according to API. 'JdkMarshaller' is default marshaller
for services
Thank you Vyacheslav,
Still reproduced in 2.8.0 and in 2.7.6 is not.
Please take a look carefully at the gist example code.
public class TestServiceImpl extends *Test* implements Service,TestService
-
Regards
Cristian Gheorghe Florescu
--
Sent from:
Sorry, wrong link in previous email.
Here is an example:
https://github.com/apache/ignite/blob/master/modules/spring/src/test/java/org/apache/ignite/spring/injection/spring-bean.xml
On Tue, Apr 21, 2020 at 8:02 PM Vyacheslav Daradur
wrote:
> Hi, I looked through your example and can't
Hi, I looked through your example and can't reproduce it.
Properties injection works fine.
I suppose that you have run Ignite out of Spring context.
Please check your Spring context configuration file once again.
Here is an example:
So igniters,
There are any issue on this ?
Should I wait for further release ?
-
--
Regards
Cristian Gheorghe Florescu
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi Ilya,
Only for testing purpose, I'd tried ignite-core 2.8.0 with ignite-spring
2.7.6 but results are the same, fields are null.
My environment contain spring version is 5.2.4.RELEASE
Using same environment (java 11.0.4, spring 5.2.4) all works fine in 2.7.6
Please let me know if you find
Hello!
I think it is a Spring issue, not Ignite issue. We have bumped Spring
version in 2.8.
Regards,
--
Ilya Kasnacheev
пн, 30 мар. 2020 г. в 22:56, myset :
> Stripped ...
>
> Please check the gist with code snippets
>
> https://gist.github.com/myset/696461e135d9c8a32588ff2a534d7eb8
>
>
>
Stripped ...
Please check the gist with code snippets
https://gist.github.com/myset/696461e135d9c8a32588ff2a534d7eb8
Thank you Nikolay
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hello.
Sorry, I can’t see any code.
Can you create a gist and sent us link to it?
> 30 марта 2020 г., в 20:19, myset написал(а):
>
> Please see the code bellow:
>
> *Ignite service definition
> ...
>
> ...
> *TestService interface*
>
>
> *Test class*
>
>
> *TestServiceImpl class*
>
>
Please see the code bellow:
*Ignite service definition
...
...
*TestService interface*
*Test class*
*TestServiceImpl class*
*Exceptions @ runtime with ignite 2.8.0*
Thank you
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hello.
Sill lack of information.
Please, send stack trace and piece of code that produce the error.
> 30 марта 2020 г., в 18:33, myset написал(а):
>
> Thank you for answer Nikolay,
> I receive various null pointer exceptions @ runtime on TestServiceImpl for
> all fields extended from Test
Thank you for answer Nikolay,
I receive various null pointer exceptions @ runtime on TestServiceImpl for
all fields extended from Test class
My class TestServiceImpl class is defined by the following pice of code
/public class TestServiceImpl extends Test implements Service, TestService/
Test -
Hello.
Can you, please, clarify your issue?
Is there any stack trace of logs that can make issue more clear.
Can you, please, show us the code that is cause error?
> 28 марта 2020 г., в 21:43, myset написал(а):
>
> Hi everybody,
> Some body encountered similar issue ?
> It is a matter of
Hi everybody,
Some body encountered similar issue ?
It is a matter of serialization ?
It is possible to switch any service compatibility mode flag ?
--
Thank you
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Thank you for help ezhuravl,
Your proposal sample it is OK.
In my example tests.TestServiceImpl class extends another class with all the
fields (geters and seters) and work methods inside.
In 2.7.6 works in 2.8.0 @ runtime all fields are null on the same
conditions/environment (java 11.0.4).
If
Hi,
I tried to reproduce the behaviour you described, but everything works fine
for me. Please check if I missed something:
https://github.com/ezhuravl/ignite-code-examples/tree/master/src/main/java/examples/service/parameters
Hi,
In 2.8.0 maven version of ignite-core, I encountered one issue within spring
service configuration.
All service properties fields are null (Ex. testField1, testField2) at
runtime on TestServiceImpl - init() or execute().
In 2.7.6 version everything works well.
Ex.
...
18 matches
Mail list logo