[infinispan-issues] [JBoss JIRA] Commented: (ISPN-348) Generated Infinispan configs from EHCache and Coherence translators leave out the <transport /> element
[
https://jira.jboss.org/jira/browse/ISPN-348?page=com.atlassian.jira.plugi...
]
Manik Surtani commented on ISPN-348:
------------------------------------
So this does not work then, since generated Infinispan configurations fail to declare a
<transport /> element under <global />, and then when you try and start a
named cache in a clustered mode, you get a ConfigurationException.
See my comment above, "The transport element should be added if the EHCache config is
clustered.". What I mean by "... if the EHCache config is clustered..." is
that if at least 1 clustered cache is defined in the EHCache xml file.
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