[JBoss JIRA] (JBTIS-175) Test Teiid Designer Server Management and Integration to JBDS/JBT
by Lucie Fabrikova (JIRA)
Lucie Fabrikova created JBTIS-175:
-------------------------------------
Summary: Test Teiid Designer Server Management and Integration to JBDS/JBT
Key: JBTIS-175
URL: https://issues.jboss.org/browse/JBTIS-175
Project: JBoss Tools Integration Stack
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Lucie Fabrikova
Assignee: Lucie Fabrikova
- focus on feature-related improvements
- area of server management, integrating to JBDS/JBT
- create AS5.1 + teiid 7.7.x, EAP 6.1 + Teiid 8.4.x servers, switching between them to preview data (tables) and execute VDB's. Open/close projects
- performing preview/execute/deploy actions when 1) NO server defined 2) Server defined but not started
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-14929) Verbose application type type dissapears after refreshing the connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14929?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14929 at 9/12/13 7:37 AM:
-------------------------------------------------------------------
Fixing JBIDE-14514 does not resolve this issue. The cause for the verbose labels to disappear is limited information when a standalone catridge object is created from the application listing:
{code}
{
"data":{
"aliases":[
"jbosstools.org"
],
"app_url":"http://springeap6-foobarz.rhcloud.com/",
...
"framework":"jbossas-7",
...
"type":"application",
"version":"1.2"
}
{code}
Whereas when we list the available cartridges we have the full set of informations:
{code}
{
"data":[
{
"current_scale":0,
"description":"The leading open source Java EE6 application server for enterprise Java applications. Popular development frameworks include Seam, CDI, Weld, and Spring.",
"display_name":"JBoss Application Server 7.1",
"help_topics":{
"Developer Center":"https://openshift.redhat.com/community/developers"
},
"license":"ASL 2.0",
"license_url":"",
"name":"jbossas-7",
"scales_from":1,
"scales_to":-1,
"scales_with":"haproxy-1.4",
"supported_scales_from":1,
"supported_scales_to":-1,
"tags":[
"service",
"web_framework",
"java",
"jboss"
],
"type":"standalone",
"usage_rates":[
],
"version":7,
"website":"http://www.jboss.org"
},
...
"type":"cartridges",
"version":"1.2"
}
To resolve this issue, we'd have to look up the "framework" (see "framework":"jbossas-7") cartridge in the listing of the available cartridges.
{code}
was (Author: adietish):
Fixing JBIDE-14514 does not resolve this issue. The cause for the verbose labels to disappear is limited information when a standalone catridge object is created from the application listing:
{code}
{
"data":{
"aliases":[
"jbosstools.org"
],
"app_url":"http://springeap6-foobarz.rhcloud.com/",
...
"framework":"jbosseap-6.0",
...
"type":"application",
"version":"1.2"
}
{code}
Whereas when we list the available cartridges we have the full set of informations:
{code}
{
"data":[
{
"current_scale":0,
"description":"The leading open source Java EE6 application server for enterprise Java applications. Popular development frameworks include Seam, CDI, Weld, and Spring.",
"display_name":"JBoss Application Server 7.1",
"help_topics":{
"Developer Center":"https://openshift.redhat.com/community/developers"
},
"license":"ASL 2.0",
"license_url":"",
"name":"jbossas-7",
"scales_from":1,
"scales_to":-1,
"scales_with":"haproxy-1.4",
"supported_scales_from":1,
"supported_scales_to":-1,
"tags":[
"service",
"web_framework",
"java",
"jboss"
],
"type":"standalone",
"usage_rates":[
],
"version":7,
"website":"http://www.jboss.org"
},
...
"type":"cartridges",
"version":"1.2"
}
{code}
> Verbose application type type dissapears after refreshing the connection
> ------------------------------------------------------------------------
>
> Key: JBIDE-14929
> URL: https://issues.jboss.org/browse/JBIDE-14929
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: shorthand-label.png, type1.png, type2.png, verbose-application-type.png
>
>
> !type1.png! -> !type2.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15430) Chrome regression because of invalid content-lenght returned with special characters
by Jakub Niedermertl (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15430?page=com.atlassian.jira.plugi... ]
Jakub Niedermertl commented on JBIDE-15430:
-------------------------------------------
LiveReload with special characters works ok even in Chrome in JBDS Version: 7.1.0.Alpha1 Build id: Alpha1-v20130909-0132-B378 .
Aforementioned steps to reproduce in 4.1.0.Final lead to page that is rendered in all browsers however special character are replaced with '?' char. I.e. I can't reproduce it. If it doesn't matter, feel free to close.
> Chrome regression because of invalid content-lenght returned with special characters
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-15430
> URL: https://issues.jboss.org/browse/JBIDE-15430
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Alpha1
>
>
> When the HTML entity in the HTTP response contains special characters and the livereload script is injected in that entity, the computed content-lenght header is invalid, which causes Chrome to not render the returned HTML page *at all*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15392:
---------------------------------------------
This jira was created to create a good api - that might require changes on both sides.
Maybe this should only be done in master and 4.1.x just continue using hardcoded lookups since this API change would require a version bump on 4.1.x for server ?
And yes, specific integration for specific containers would be in separate plugins and when not available just fallback to use the hardcoded approach.
You don't loose any features, but you avoid having to add tons of custom server type specific logic.
> Add api in server needed for source lookup
> ------------------------------------------
>
> Key: JBIDE-15392
> URL: https://issues.jboss.org/browse/JBIDE-15392
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha1
>
>
> As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes.
> We need to define a stable api that can be used here.
> lets outline what api is actually needed and then subjiras for the specifics.
> For me it looks like server lookup needs a few things:
> 0. know exact version of server
> 1. know the file structure of a certain server
> 2. get dir or directories that contain jar that is the "runtime"
> My guess is that #2 might just be sufficient for source code lookup.
> Any comments ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months