[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3174:
-----------------------------------
Description:
When I went through JDG7 materialization creation I noticed that MXD 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 MXD 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 MXD for JDG7 source model automatically.
So after finish wizard, the designer set infinispan-hotrod MXD for this model. If infinispan-hotrod MXD is not imported yet, designer shows a error dialog.
When I generate source model for JDG6.6, MXD is set correctly (because MXD is built-in).
was:
When I went through JDG7 materialization creation I noticed that MXD 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 MXD 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*.
When I generate source model for JDG6.6, MXD is set correctly (because MXD is built-in).
> 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 MXD 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 MXD 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 MXD for JDG7 source model automatically.
> So after finish wizard, the designer set infinispan-hotrod MXD for this model. If infinispan-hotrod MXD is not imported yet, designer shows a error dialog.
> When I generate source model for JDG6.6, MXD is set correctly (because MXD is built-in).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard
by Matej Kralik (JIRA)
Matej Kralik created TEIIDDES-3174:
--------------------------------------
Summary: 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 MXD 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 MXD 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*.
When I generate source model for JDG6.6, MXD is set correctly (because MXD is built-in).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-2092) Consolidate Data Source connection management into a single view
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2092?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2092:
-----------------------------------
Labels: release_notes (was: )
> Consolidate Data Source connection management into a single view
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2092
> URL: https://issues.jboss.org/browse/TEIIDDES-2092
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Datatools Integration, Teiid Integration, Views
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: release_notes
> Fix For: 11.1.1
>
> Attachments: data-sources-view-draft.png, new-model-editor-and-data-sources-view.png
>
>
> Teiid Designer, and JBoss Tools in general, suffers from the lack of a centralized view of workspace datasource/connection information.
> This feature may include:
> * Data Sources view
> ** Tree containing datasource category/type folders (i.e. JDBC, WS, File, Spreadsheet etc.... ) and instances of Datasource Definitions
> ** Property table to show/edit properties for selected Datasource Definitions
> ** Toolbar to allow creating DDs, creating/deploying datasources from selected DDs
> ** Actions would include: Create Data Source, Import > JDBC or through Teiid Connection
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-2092) Consolidate Data Source connection management into a single view
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2092?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2092.
----------------------------------
Resolved in [TEIIDDES-3044|https://issues.jboss.org/browse/TEIIDDES-3044]. The view name is Connections.
> Consolidate Data Source connection management into a single view
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2092
> URL: https://issues.jboss.org/browse/TEIIDDES-2092
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Datatools Integration, Teiid Integration, Views
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: release_notes
> Fix For: 11.1.1
>
> Attachments: data-sources-view-draft.png, new-model-editor-and-data-sources-view.png
>
>
> Teiid Designer, and JBoss Tools in general, suffers from the lack of a centralized view of workspace datasource/connection information.
> This feature may include:
> * Data Sources view
> ** Tree containing datasource category/type folders (i.e. JDBC, WS, File, Spreadsheet etc.... ) and instances of Datasource Definitions
> ** Property table to show/edit properties for selected Datasource Definitions
> ** Toolbar to allow creating DDs, creating/deploying datasources from selected DDs
> ** Actions would include: Create Data Source, Import > JDBC or through Teiid Connection
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3130) Designer manually created REST War errors with large resultset
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3130?page=com.atlassian.jira.plu... ]
Matej Kralik commented on TEIIDDES-3130:
----------------------------------------
I am not able to connect to DB from the attached project (Name or service not known). [~dsteigne] Can you please try it?
> Designer manually created REST War errors with large resultset
> --------------------------------------------------------------
>
> Key: TEIIDDES-3130
> URL: https://issues.jboss.org/browse/TEIIDDES-3130
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1
> Environment: Tested in Teiid Designer 11.1, 11.0.1. JDV 6.3.8
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 11.1.1
>
> Attachments: REST_POC.vdb, REST_POC_1.war, myrestpoc.zip
>
>
> Using "Generate REST War" on a VDB and deploying it with your VDB and testing with a large resultset, gives the below error :
> 09:26:18,587 SEVERE [org.teiid.rest] (http-127.0.0.1:8080-1) Exception in execute: {0}: java.lang.Throwable: java.sql.SQLException: java.lang.IllegalArgumentException: Null charset name
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:116) [classes:]
> at org.teiid.rest.services.REST_Views.MV_AUDIT(REST_Views.java:94) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_60]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:583) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:565) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:130) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.14.Final-redhat-2.jar:7.5.14.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:656) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> Caused by: java.sql.SQLException: java.lang.IllegalArgumentException: Null charset name
> at org.teiid.rest.services.TeiidRSProviderPost.handleResult(TeiidRSProviderPost.java:167) [classes:]
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:112) [classes:]
> ... 29 more
> Caused by: java.lang.IllegalArgumentException: Null charset name
> at java.nio.charset.Charset.lookup(Charset.java:457) [rt.jar:1.8.0_60]
> at java.nio.charset.Charset.forName(Charset.java:528) [rt.jar:1.8.0_60]
> at org.teiid.query.function.source.XMLSystemFunctions.serialize(XMLSystemFunctions.java:1278) [org.teiid.runtime.client_11.1.0.v20170906-1613.jar:]
> at org.teiid.rest.services.TeiidRSProviderPost.handleResult(TeiidRSProviderPost.java:165) [classes:]
> ... 30 more
> 09:26:18,591 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (http-127.0.0.1:8080-1) RESTEASY000105: Failed to execute: javax.ws.rs.WebApplicationException
> at org.teiid.rest.services.TeiidRSProviderPost.createWebApplicationException(TeiidRSProviderPost.java:194) [classes:]
> at org.teiid.rest.services.TeiidRSProviderPost.execute(TeiidRSProviderPost.java:117) [classes:]
> at org.teiid.rest.services.REST_Views.MV_AUDIT(REST_Views.java:94) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_60]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_60]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:583) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:565) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:130) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.17.Final-redhat-1.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.14.Final-redhat-2.jar:7.5.14.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:656) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.21.Final-redhat-2.jar:7.5.21.Final-redhat-2]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> If the "Auto-generate WAR" box is checked instead it works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3173) Teiid Designer "Problem Occurred" error message on DV start
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3173?page=com.atlassian.jira.plu... ]
Andrej Podhradsky closed TEIIDDES-3173.
---------------------------------------
Fix Version/s: 11.1.1
Resolution: Cannot Reproduce
> Teiid Designer "Problem Occurred" error message on DV start
> -----------------------------------------------------------
>
> Key: TEIIDDES-3173
> URL: https://issues.jboss.org/browse/TEIIDDES-3173
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.0.1
> Environment: Installed JBDS 10.4 then installed Fuse, DV, and BPMS integration tooling from Red Hat Central. Empty workspace folder as well. DV 6.3.5 installed. Mac OSX 10.11.6 and Java 1.8.0_131
> Reporter: Rich Lucente
> Priority: Minor
> Fix For: 11.1.1
>
> Attachments: Screen Shot 2017-05-24 at 6.07.27 PM.png
>
>
> Define server for DV 6.3.5 within JBDS and attempt to start that server. Get the attached message everytime DV 6.3.5 is started from within JBDS.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3173) Teiid Designer "Problem Occurred" error message on DV start
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3173?page=com.atlassian.jira.plu... ]
Andrej Podhradsky moved JBTIS-1114 to TEIIDDES-3173:
----------------------------------------------------
Project: Teiid Designer (was: JBoss Tools Integration Stack)
Key: TEIIDDES-3173 (was: JBTIS-1114)
Workflow: classic default workflow (was: GIT Pull Request workflow )
Component/s: (was: teiid)
Affects Version/s: 11.0.1
(was: 10.3.0.GA)
> Teiid Designer "Problem Occurred" error message on DV start
> -----------------------------------------------------------
>
> Key: TEIIDDES-3173
> URL: https://issues.jboss.org/browse/TEIIDDES-3173
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.0.1
> Environment: Installed JBDS 10.4 then installed Fuse, DV, and BPMS integration tooling from Red Hat Central. Empty workspace folder as well. DV 6.3.5 installed. Mac OSX 10.11.6 and Java 1.8.0_131
> Reporter: Rich Lucente
> Priority: Minor
> Attachments: Screen Shot 2017-05-24 at 6.07.27 PM.png
>
>
> Define server for DV 6.3.5 within JBDS and attempt to start that server. Get the attached message everytime DV 6.3.5 is started from within JBDS.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3151) OData4 specific MXD is not found
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3151?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-3151:
-----------------------------------
Labels: release_notes (was: )
> OData4 specific MXD is not found
> ---------------------------------
>
> Key: TEIIDDES-3151
> URL: https://issues.jboss.org/browse/TEIIDDES-3151
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 11.1
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes
> Fix For: 11.1.1
>
> Attachments: my_custom_med.mxd, odata4.mxd
>
>
> While working on the case I found that there is no "odata4" specific MXD nor the current odata MXD is updated with newer properties for the V4. Since server uses the same namespace the current one needs to be updated.
> A sample MXD (minus the namespace) is attached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months