[JBoss JIRA] (TEIIDDES-1923) Create a connection profile for a Infinispan/JDG Cache
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1923?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1923:
----------------------------------------
[~van.halbert] [~rareddy] We'll need the details (i.e. properties, url template etc....) in order to create this profile as well as what Teiid-specific properties required to create the data source.
> Create a connection profile for a Infinispan/JDG Cache
> ------------------------------------------------------
>
> Key: TEIIDDES-1923
> URL: https://issues.jboss.org/browse/TEIIDDES-1923
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Datatools Integration, Extension Framework, Import/Export, VDB & Execution
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 10.0.2
>
>
> Create a connection profile for Infinispan/JDG Cache.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIIDDES-2712) Support GET & POST methods together on REST procedures
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2712?page=com.atlassian.jira.plu... ]
Matus Makovy edited comment on TEIIDDES-2712 at 5/4/16 7:47 AM:
----------------------------------------------------------------
[~sdir]
The way to model this is to have 2 procedures with 2 different methods (GET,POST) and use 1 URI for both of them.
was (Author: mmakovy):
The way to model this is to have 2 procedures with 2 different methods (GET,POST) and use 1 URI for both of them.
> Support GET & POST methods together on REST procedures
> ------------------------------------------------------
>
> Key: TEIIDDES-2712
> URL: https://issues.jboss.org/browse/TEIIDDES-2712
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Patch Release, Web Services Support
> Reporter: Matus Makovy
> Assignee: Ted Jones
> Fix For: 10.0.2
>
>
> Copied from BZ:
> Description of request:
> We can choose only one HTTP Request type for REST virtual procedures. Is it possible to combine GET & POST as one type ?
> Rationale:
> POST requests are more easy to create for client programmers.On the other hand GET method simplifies testing. Since it's easy to handle both request types on the server side, supporting both method at the same time may help to improve usability of services.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ]
Ramesh Reddy updated TEIIDDES-2812:
-----------------------------------
Priority: Blocker (was: Major)
> Add ability to reverse engineer into a Pojo object from a table or view
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2812
> URL: https://issues.jboss.org/browse/TEIIDDES-2812
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Usability
> Affects Versions: 9.0.6
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 10.0.2
>
>
> The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output.
> Label of action: Create Pojo (or something to indicates the process)
> Dialog title: Create Pojo from Table [tableName]
> Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source.
> Options:
> - file chooser option to select folder to save pojo jar
> - drop-down: <select option>
> Access JDG in Library Mode
> Access JDG via Hot Rod Client
> - pojo package name (default = org.teiid.pojo)
> - pojo jar name (default = pojo.jar)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2487:
----------------------------------------
We will test this once, to be sure that the example works.
> Teidd Designer Import SOAP Relational Model Mapping No Columns defined
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2487
> URL: https://issues.jboss.org/browse/TEIIDDES-2487
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export, Patch Release
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Assignee: Ted Jones
> Fix For: 9.2
>
> Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png
>
>
> issue
> ====
> Create Relational Model from SOAP service validation failed with "No Columns defined error"
> Reproduce
> ========
> 1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
> 2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
> Enhancement
> ==========
> 1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
> 2. Simplify XML document modeling related operation - current wizard not user-friendly, web should do some enhancement in request/response xml document modeling.
> 3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier.
> [1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
> [2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2487:
-----------------------------------
Fix Version/s: 9.2
(was: 9.2.2)
> Teidd Designer Import SOAP Relational Model Mapping No Columns defined
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2487
> URL: https://issues.jboss.org/browse/TEIIDDES-2487
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export, Patch Release
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Assignee: Ted Jones
> Fix For: 9.2
>
> Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png
>
>
> issue
> ====
> Create Relational Model from SOAP service validation failed with "No Columns defined error"
> Reproduce
> ========
> 1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
> 2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
> Enhancement
> ==========
> 1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
> 2. Simplify XML document modeling related operation - current wizard not user-friendly, web should do some enhancement in request/response xml document modeling.
> 3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier.
> [1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
> [2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (TEIIDDES-1809) WAR File (REST, SOAP) Creation usability enhancements
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1809?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1809:
-----------------------------------
Fix Version/s: 10.0.2
(was: 9.2.2)
> WAR File (REST, SOAP) Creation usability enhancements
> ------------------------------------------------------
>
> Key: TEIIDDES-1809
> URL: https://issues.jboss.org/browse/TEIIDDES-1809
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Patch Release, Web Services Support
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 10.0.2
>
>
> I have seen so many time in the community, where users are confused in asking them to create JNDI file to VDB and deploy the VDB and WAR file. I have two suggestions in this regard to help improve the situation
> 1) Instead of (or in addition) asking to enter {REPLACE_WITH_VDB_JNDI_NAME}, offer to create data source to the VDB. If the server is attached, you have all details, or pop up create datasource dialog to create.
> 2) Instead of (or in addition) to saving the WAR file, offer to deploy directly to the server, that will save time and would seem seamless operation we can provide.
> 3) I often find myself struck in figuring out what is WSDL Endpoint or what are REST endpoints exposed by the WAR deployed, it there is any help we can show at the end of this dialog box (if they choose to deploy) that would save time in them figuring out (going to documentation etc).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months