[ 
https://issues.apache.org/jira/browse/IGNITE-17541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Shishkov updated IGNITE-17541:
-----------------------------------
    Description: 
IGNITE-13389 introduces 
{{ThinClientConfiguration#sendServerExceptionStackTraceToClient()}}, but name 
of the method does not allow to set up this option in XML configuration, 
because Spring expects "set" prefix for setters.
As you can see below, there is a workaround, but it would be more convenient to 
set up this property directly.
Workaround:
{code:xml|title=Add extra ThinClientConfiguration bean with necessary 
parameters}
<bean id="thinClientCfg" 
class="org.apache.ignite.configuration.ThinClientConfiguration">
    <property name="maxActiveTxPerConnection" value="15"/>
</bean>
{code}
{code:xml|title=Set up thinClientConfiguration by means of SpEL}
<property name="clientConnectorConfiguration">
    <bean class="org.apache.ignite.configuration.ClientConnectorConfiguration">
        <property name="thinClientConfiguration"
                  
value="#{thinClientCfg.sendServerExceptionStackTraceToClient(true)}"/>
    </bean>
</property>
{code}

We should add "set" and "get" prefix to setter and getter methods respectively 
or add extra methods with such prefixes from the point of possible 
compatibility issues (see IGNITE-16549).

  was:
IGNITE-13389 introduces 
{{ThinClientConfiguration#sendServerExceptionStackTraceToClient()}}, but name 
of the method does not allow to set up this option in XML configuration, 
because Spring expects "set" prefix for setters.
As you can see below, there is a workaround, but it would be more convenient to 
set up this property directly:
{code:xml|title=Add extra ThinClientConfiguration bean with necessary 
parameters}
<bean id="thinClientCfg" 
class="org.apache.ignite.configuration.ThinClientConfiguration">
    <property name="maxActiveTxPerConnection" value="15"/>
</bean>
{code}
{code:xml|title=Set up thinClientConfiguration by means of SpEL}
<property name="clientConnectorConfiguration">
    <bean class="org.apache.ignite.configuration.ClientConnectorConfiguration">
        <property name="thinClientConfiguration"
                  
value="#{thinClientCfg.sendServerExceptionStackTraceToClient(true)}"/>
    </bean>
</property>
{code}

We should add "set" and "get" prefix to setter and getter methods respectively 
or add extra methods with such prefixes from the point of possible 
compatibility issues (see IGNITE-16549).


> Add "set" prefix to 
> ThinClientConfiguration#sendServerExceptionStackTraceToClient()
> -----------------------------------------------------------------------------------
>
>                 Key: IGNITE-17541
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17541
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>    Affects Versions: 2.13
>            Reporter: Ilya Shishkov
>            Priority: Minor
>              Labels: ise, newbie
>
> IGNITE-13389 introduces 
> {{ThinClientConfiguration#sendServerExceptionStackTraceToClient()}}, but name 
> of the method does not allow to set up this option in XML configuration, 
> because Spring expects "set" prefix for setters.
> As you can see below, there is a workaround, but it would be more convenient 
> to set up this property directly.
> Workaround:
> {code:xml|title=Add extra ThinClientConfiguration bean with necessary 
> parameters}
> <bean id="thinClientCfg" 
> class="org.apache.ignite.configuration.ThinClientConfiguration">
>     <property name="maxActiveTxPerConnection" value="15"/>
> </bean>
> {code}
> {code:xml|title=Set up thinClientConfiguration by means of SpEL}
> <property name="clientConnectorConfiguration">
>     <bean 
> class="org.apache.ignite.configuration.ClientConnectorConfiguration">
>         <property name="thinClientConfiguration"
>                   
> value="#{thinClientCfg.sendServerExceptionStackTraceToClient(true)}"/>
>     </bean>
> </property>
> {code}
> We should add "set" and "get" prefix to setter and getter methods 
> respectively or add extra methods with such prefixes from the point of 
> possible compatibility issues (see IGNITE-16549).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to