[JBoss JIRA] (JBIDE-21049) Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21049?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21049:
-------------------------------------
https://github.com/jbosstools/jbosstools-server/pull/385/files - pull request
> Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog
> ------------------------------------------------------------------
>
> Key: JBIDE-21049
> URL: https://issues.jboss.org/browse/JBIDE-21049
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Rob Stryker
> Priority: Minor
>
> WildFly 10 introduced a new schema "wildfly-messaging-activemq-deployment_1_0.xsd" for configuration of e.g. an ActiveMQ queue as part of a deployable archive, e.g. an EAR file (a file with the extension "...-jms.xml").
> This schema file is missing in the XSD catalog.
> Here is a sample xml instance:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <messaging-deployment xmlns="urn:jboss:messaging-activemq-deployment:1.0">
> <server>
> <jms-destinations>
> <jms-queue name="MessageBeanQueue">
> <entry name="jms/queue/MessageBeanQueue"/>
> </jms-queue>
> </jms-destinations>
> </server>
> </messaging-deployment>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21065:
--------------------------------
Component/s: upstream
> Server host name address should not be defaulted during server adapter creation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21065
> URL: https://issues.jboss.org/browse/JBIDE-21065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Final
>
>
> I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}.
> This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address.
> Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21065:
--------------------------------
Fix Version/s: 4.4.0.Final
> Server host name address should not be defaulted during server adapter creation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21065
> URL: https://issues.jboss.org/browse/JBIDE-21065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Final
>
>
> I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}.
> This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address.
> Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-21065:
-----------------------------------
Assignee: Rob Stryker
> Server host name address should not be defaulted during server adapter creation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21065
> URL: https://issues.jboss.org/browse/JBIDE-21065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.0.Final
>
>
> I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}.
> This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address.
> Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21100) start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21100:
-------------------------------------
As discussed in the forums, The web port seems accurately detected to be 8080, and your pollers are all set to check the web port. The mechanism used to check the web port is a very simple url connection... ex:
{code}
URL pingUrl = new URL("http://" + host + ":" + 8080);
conn = pingUrl.openConnection();
((HttpURLConnection)conn).getResponseCode();
{code}
If an exception is thrown, the server is deemed to not be up yet. If the code completes normally, it is decided that the server is up and responsive.
I am unable to replicate this at this time.
> start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21100
> URL: https://issues.jboss.org/browse/JBIDE-21100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)
> Reporter: carl zhang
> Assignee: Rob Stryker
>
> please refer to
> https://developer.jboss.org/thread/265726?start=0&tstart=0
> refer to the picture of 28-Oct-2015 9:46 AM (layer 3)
> In the left panel: WildFly 8.x is configured to connect to localhost
> WildFly 8.x(1) is configured to connect to remote host (Linux)
> The localhost cannot finish start process. WildFly 8.x(1) (remote) can.
> What ports, or temp files, or anything else are checked when changing from starting to started state?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21080) Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21080?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21080:
------------------------------------------
[~fbricon] Thanks!
> Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21080
> URL: https://issues.jboss.org/browse/JBIDE-21080
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: explorer, import_wizard, openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> There is a context menu item to import an existing OpenShift 3 application available on every tree item placed under OpenShift 3 connection. Even "folder" for any resource has it (e.g. Routes, Services) and any resource too (e.g. specific pod, service, replication controller).
> I think this is not good because it go against concept of *context* menu. We could have it for a project and build config (maybe also for a connection) that would be sufficient.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21155) fix test failures
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21155?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21155:
------------------------------------------
merged and pushed to upstream/jbosstools-4.3.x and cherry picked to upstream/master
> fix test failures
> -----------------
>
> Key: JBIDE-21155
> URL: https://issues.jboss.org/browse/JBIDE-21155
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> {code}
> Tests in error:
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21155) fix test failures
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21155?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21155:
------------------------------------------
jenkins is blue again.
> fix test failures
> -----------------
>
> Key: JBIDE-21155
> URL: https://issues.jboss.org/browse/JBIDE-21155
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> {code}
> Tests in error:
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21155) fix test failures
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21155?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-21155.
------------------------------------
clsoing, nothing for QE to verify
> fix test failures
> -----------------
>
> Key: JBIDE-21155
> URL: https://issues.jboss.org/browse/JBIDE-21155
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> {code}
> Tests in error:
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPropertySourceTest.setup:29 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionPersistencyTest.setup:36 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> ConnectionTest.setup:52 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument
> OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21156) Remove LazySSLCertificateCallback and LazyCredentialsPrompter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21156?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21156:
-------------------------------------
Description: In JBIDE-21153 we introduced extension points that openshift.core can reach out to in order to present UI elements. We thus theoretically dont need the lazy loading patterns for those that were used when there were no extension points yet. (was: In JBIDE-21155 we introduced extension points that openshift.core can reach out to in order to present UI elements. We thus theoretically dont need the lazy loading patterns for those that were used when there were no extension points yet.)
> Remove LazySSLCertificateCallback and LazyCredentialsPrompter
> -------------------------------------------------------------
>
> Key: JBIDE-21156
> URL: https://issues.jboss.org/browse/JBIDE-21156
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Fix For: 4.3.x, 4.4.0.Alpha1
>
>
> In JBIDE-21153 we introduced extension points that openshift.core can reach out to in order to present UI elements. We thus theoretically dont need the lazy loading patterns for those that were used when there were no extension points yet.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month