[infinispan-issues] [JBoss JIRA] Commented: (ISPN-348) Generated Infinispan configs from EHCache and Coherence translators leave out the <transport /> element

[Mircea Markus (JIRA)]

    [ https://jira.jboss.org/jira/browse/ISPN-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12515930#action_12515930 ] 

Mircea Markus commented on ISPN-348:
------------------------------------

Current transformer implementation behaves correctly. In EHCache, it is possible to configure the transport per cache level, and the way the transport works (i.e. async, timeouts) is configured for each transport/cache. In ISPN we only configure transport once (in global) and then for each cache we define the way it is using the transport: e.g. distributed sync, replicated etc. Current impl looks at each EHCache cache and adapts the transport config to ISPN: e.g. sets it to invalidation or distribution, sync or async. This happens for each cache.
Also, I haven't seen any place where one can configure the transport name, a lka jgroups. 



> Generated Infinispan configs from EHCache and Coherence translators leave out the <transport /> element
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-348
>                 URL: https://jira.jboss.org/jira/browse/ISPN-348
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Migration tools
>    Affects Versions: 4.0.0.CR4
>            Reporter: Manik Surtani
>            Assignee: Mircea Markus
>             Fix For: 4.0.0.Final
>
>
> EHCache2InfinispanTransformerTest tests for a clustered config and this fails due to a missing transport element.  The transport element should be added if the EHCache config is clustered.  Also, attribs such as node name should be filled in.
> The same is the case for generated configs using the Coherence transformer, however the Coherence test does not test for a clustered config.  Coherence2InfinispanTransformerTest should be enhanced and the XSLT fixed accordingly.
> Finally, the wiki should state that this applies to EHCache 1.7 and 1.8 as well (perhaps just 1.x?)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira