[
https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu...
]
Matej Kralik updated TEIIDDES-3174:
-----------------------------------
Workaround Description:
# Set up and run server if you don't have any server (infinispan-hotrod MED will be
imported)
# Left-click on generated JDG source model and select Modeling -> Manage Model
Extension Definition
# Click to Add... and select infinispan-hotrod
# click to ok and finish button (now, model has set extension and property
infinispan-hotrod:CACHE is set)
was:
# Set up and run server if you don't have any server (infinispan-hotrod MXD will be
imported)
# Left-click on generated JDG source model and select Modeling -> Manage Model
Extension Definition
# Click to Add... and select infinispan-hotrod
# click to ok and finish button (now, model has set extension and property
infinispan-hotrod:CACHE is set)
Infinispan-hotrod MXD is not set after JDG materialization wizard
-----------------------------------------------------------------
Key: TEIIDDES-3174
URL:
https://issues.jboss.org/browse/TEIIDDES-3174
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 11.1.1
Reporter: Matej Kralik
Priority: Critical
When I went through JDG7 materialization creation I noticed that MED for JDG7 source
model is not set automatically. So I don't see Primary cache name and staging cache
name which I set in the 'Generate Materialized JDG Module' wizard.
I must set MED for this model manually (Modeling -> Manage Model Extension Definition
-> Add -> infinispan-hotrod).
After that, I see infinispan-hotrod:CACHE which I defined in the wizard.
Typ of infinispan-hotrod is *imported* so I must have set up a server *before*.
In my points of view, the designer should set MED for JDG7 source model automatically.
My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If
infinispan-hotrod MED is not imported yet, the designer should show an error dialog that
server is not defined yet and MED is not available.
When I generate source model for JDG6.6, MED is set correctly (because MED is built-in).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)