[JBoss JIRA] (TEIIDDES-2174) Hard Coded teiid jdbc server port 31000
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2174?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2174:
-----------------------------------
Attachment: teiid-instance-editor-page.png
This is what the server editor page looks like. Note the captured tooltip.
So, for an 8.+ Teiid server, Designer discovers the server port on connection. That's what'll be displayed in the PORT field (non-editable) and can be used for reference if user wishes to return to the exact Teiid JDBC port value.
> Hard Coded teiid jdbc server port 31000
> ---------------------------------------
>
> Key: TEIIDDES-2174
> URL: https://issues.jboss.org/browse/TEIIDDES-2174
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.3.2
> Reporter: Jason Marley
> Assignee: Barry LaFond
> Attachments: teiid-instance-editor-page.png
>
>
> There is no where to change the port the teiid server is talking with. I will provide a video to show.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2028:
---------------------------------------------------
nshendye(a)redhat.com changed the Status of [bug 1056756|https://bugzilla.redhat.com/show_bug.cgi?id=1056756] from ASSIGNED to MODIFIED
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Ted Jones
> Fix For: Future
>
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2174) Hard Coded teiid jdbc server port 31000
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2174?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2174:
----------------------------------------
K, so maybe the solution here is to:
# add a JDBC Port override field
# persist the override in Designer's Teiid server registry
# Keep the *discovered* PORT for reference
# Display *<not-connected>* in the discovered PORT field if server not connected .... to prevent confusion
> Hard Coded teiid jdbc server port 31000
> ---------------------------------------
>
> Key: TEIIDDES-2174
> URL: https://issues.jboss.org/browse/TEIIDDES-2174
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.3.2
> Reporter: Jason Marley
> Assignee: Barry LaFond
>
> There is no where to change the port the teiid server is talking with. I will provide a video to show.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2174) Hard Coded teiid jdbc server port 31000
by Jeff Bride (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2174?page=com.atlassian.jira.plu... ]
Jeff Bride edited comment on TEIIDDES-2174 at 1/22/15 11:06 AM:
----------------------------------------------------------------
Thanks Barry.
Even with this JDBC port discovery feature, the inability to manually modify the port in the Teiid Designer is going to remain a problem in some use cases.
As an example, in support of JDV training, i have JDV 6.1 running as a docker containers for students on remote hosts.
Because Docker sets up its own internal network, selective EAP and JDV ports are proxied through the remote host operating system.
ie: in my case, 31000 is proxied through port 32000. In this case, remote JDBC clients connect through 32000 and not 31000 .
There is no way that jdbc port discovery running within the EAP/JDV runtime would be aware of the port proxying that is occurring.
Requesting the ability to manually over-ride (through the Teiid Deisgner GUI and not the underlying XML in the user's JBDS workspace) the JDBC port.
thanks again. jeff
was (Author: jbride):
Thanks Barry.
Even with this JDBC port discovery feature, the inability to manually modify the port in the Teiid Designer is going to remain a problem in some use cases.
As an example, in support of JDV training, i have JDV 6.1 running as a docker containers for students on remote hosts.
Because Docker sets up its own internal network, selective EAP and JDV ports are proxied through the remote host operating system.
ie: in my case, 31000 is proxied through port 32000. In this case, remote JDBC clients connect through 32000 and not 31000 .
Requesting the ability to manually over-ride (through the Teiid Deisgner GUI and not the underlying XML in the user's JBDS workspace) the JDBC port.
thanks again. jeff
> Hard Coded teiid jdbc server port 31000
> ---------------------------------------
>
> Key: TEIIDDES-2174
> URL: https://issues.jboss.org/browse/TEIIDDES-2174
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.3.2
> Reporter: Jason Marley
> Assignee: Barry LaFond
>
> There is no where to change the port the teiid server is talking with. I will provide a video to show.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2174) Hard Coded teiid jdbc server port 31000
by Jeff Bride (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2174?page=com.atlassian.jira.plu... ]
Jeff Bride commented on TEIIDDES-2174:
--------------------------------------
Thanks Barry.
Even with this JDBC port discovery feature, the inability to manually modify the port in the Teiid Designer is going to remain a problem in some use cases.
As an example, in support of JDV training, i have JDV 6.1 running as a docker containers for students on remote hosts.
Because Docker sets up its own internal network, selective EAP and JDV ports are proxied through the remote host operating system.
ie: in my case, 31000 is proxied through port 32000. In this case, remote JDBC clients connect through 32000 and not 31000 .
Requesting the ability to manually over-ride (through the Teiid Deisgner GUI and not the underlying XML in the user's JBDS workspace) the JDBC port.
thanks again. jeff
> Hard Coded teiid jdbc server port 31000
> ---------------------------------------
>
> Key: TEIIDDES-2174
> URL: https://issues.jboss.org/browse/TEIIDDES-2174
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.3.2
> Reporter: Jason Marley
> Assignee: Barry LaFond
>
> There is no where to change the port the teiid server is talking with. I will provide a video to show.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2174) Hard Coded teiid jdbc server port 31000
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2174?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2174 at 1/22/15 10:40 AM:
------------------------------------------------------------------
Designer's Teiid Server editor is currently set-up to discover the Teiid JDBC port value, rather than a user configuring it separately.
Testing with 9.0 code-base (and 8.6.x), by *changing the JDBC port in the standalone-teiid.xml file and re-starting the server*, Designer correctly discovers the port and sets it to the correct value. I've tested both with local server started in JBDS and connecting to a "remote" instance started outside of Eclipse.
Note that the PORT value is editable if setting up a Teiid 7.x servers instance, bot not for Teiid 8.+ servers.
This is consistent with the JBDS server configuration management of defined ports. The Server Editor's *Server Ports* section states *The ports entered here are which ports the tools will poll on the server. Changing these fields will not change the ports the server itself listens on.*
was (Author: blafond):
Designer's Teiid Server editor is currently set-up to discover the Teiid JDBC port value, rather than a user configuring it separately.
Testing with 9.0 code-base (and 8.6.x), by *changing the JDBC port in the standalone-teiid.xml file and re-starting the server*, Designer correctly discovers the port and sets it to the correct value. I've tested both with local server started in JBDS and connecting to a "remote" instance started outside of Eclipse.
Note that the PORT value is editable if setting up a Teiid 7.x servers instance, bot not for Teiid 8.+ servers.
> Hard Coded teiid jdbc server port 31000
> ---------------------------------------
>
> Key: TEIIDDES-2174
> URL: https://issues.jboss.org/browse/TEIIDDES-2174
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.3.2
> Reporter: Jason Marley
> Assignee: Barry LaFond
>
> There is no where to change the port the teiid server is talking with. I will provide a video to show.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2174) Hard Coded teiid jdbc server port 31000
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2174?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2174:
----------------------------------------
Designer's Teiid Server editor is currently set-up to discover the Teiid JDBC port value, rather than a user configuring it separately.
Testing with 9.0 code-base (and 8.6.x), by *changing the JDBC port in the standalone-teiid.xml file and re-starting the server*, Designer correctly discovers the port and sets it to the correct value. I've tested both with local server started in JBDS and connecting to a "remote" instance started outside of Eclipse.
Note that the PORT value is editable if setting up a Teiid 7.x servers instance, bot not for Teiid 8.+ servers.
> Hard Coded teiid jdbc server port 31000
> ---------------------------------------
>
> Key: TEIIDDES-2174
> URL: https://issues.jboss.org/browse/TEIIDDES-2174
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.3.2
> Reporter: Jason Marley
> Assignee: Barry LaFond
>
> There is no where to change the port the teiid server is talking with. I will provide a video to show.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months