[JBoss JIRA] (JBIDE-21341) Credentials: Allow to show password even if you choose to save it
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21341?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21341.
---------------------------------
Resolution: Done
fixed it
> Credentials: Allow to show password even if you choose to save it
> -----------------------------------------------------------------
>
> Key: JBIDE-21341
> URL: https://issues.jboss.org/browse/JBIDE-21341
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: AddCredential.png, credentials-password.png
>
>
> When you add credentials for access.redhat.com account to be used with CDK adapter, you can choose to only save your username and enter password each time. In that case when that happens, you can choose to show the password as you type (i.e. no ****). I think to be consistent you should allow the same when you're creating the credentials and enter the password there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21733) Docker connection does not work with CDK build 2016-02-19
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21733?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21733:
---------------------------------------
I noticed that if I have two cdk servers (with the same host url), then when you start server1, stop it, start server2, the docker explorer will only contain a connection for server1 because the tooling only checks the host url and if it matches, it will assume it's already there - I reported JBIDE-21744 for it. So I was thinking that it might cause this issue also - if the cert file is reused from the first cdk server, this would break it. But then I tried that with a new workspace and only the raw cdk server and the docker connection still wouldn't work.
> Docker connection does not work with CDK build 2016-02-19
> ---------------------------------------------------------
>
> Key: JBIDE-21733
> URL: https://issues.jboss.org/browse/JBIDE-21733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> Today I tried cdk build 2016-02-19 in JBDS 9.1.0.Beta2:
> When I started this from JBDS, it worked, but the Docker connection could not be established.
> It gives me this error:
> {code}
> com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:779)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:742)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerImagesContentProvider$1$1.run(DockerImagesContentProvider.java:71)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:1141)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1072)
> at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:354)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:772)
> ... 27 more
> Caused by: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1070)
> ... 29 more
> Caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:517)
> at org.glassfish.jersey.apache.connector.ApacheConnector$1.run(ApacheConnector.java:527)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at jersey.repackaged.com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:49)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:45)
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:523)
> at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:169)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:320)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:201)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1506)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:469)
> ... 20 more
> Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:352)
> at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:260)
> at sun.security.validator.Validator.validate(Validator.java:260)
> at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
> at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1488)
> ... 39 more
> Caused by: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135)
> at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219)
> at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140)
> at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79)
> at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292)
> at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347)
> ... 45 more
> Caused by: java.security.SignatureException: Signature does not match.
> at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:449)
> at sun.security.provider.certpath.BasicChecker.verifySignature(BasicChecker.java:166)
> at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:147)
> at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125)
> ... 50 more
> {code}
> To be sure, I also tried the other cdk from https://github.com/redhat-developer-tooling/openshift-vagrant and that worked. Then I tried back the official cdk and that didn't work.
> I'm pretty sure that this worked for me with the previous build. Not sure what changed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21743) no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21743?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-21743:
------------------------------------
This error is already mentioned in JBIDE-21695, but I think it's better to have it reported separately.
> no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21743
> URL: https://issues.jboss.org/browse/JBIDE-21743
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples
> Affects Versions: 4.3.1.CR1
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.3.x
>
>
> Importing "spring-kitchensink-basic" EAP7 quickstart raises an error:
> {noformat}Description Resource Path Location Type
> cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'context:component-scan'. jboss-as-spring-mvc-context.xml /jboss-spring-kitchensink-basic/src/main/webapp/WEB-INF line 26 XML Problem
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21744) cdk-created docker connection can have wrong name if you have multiple cdk server adapters
by Martin Malina (JIRA)
Martin Malina created JBIDE-21744:
-------------------------------------
Summary: cdk-created docker connection can have wrong name if you have multiple cdk server adapters
Key: JBIDE-21744
URL: https://issues.jboss.org/browse/JBIDE-21744
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.3.1.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
I noticed that if I have two cdk server adapters, start the first one, stop it, start the second, then docker explorer will only show a connection of the first server name, not the second.
This is probably because the connection will stay there after the first server start and on second server start, the tooling only checks if the docker host url matches. If it does, it will just reuse it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21743) no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-21743:
----------------------------------
Summary: no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart
Key: JBIDE-21743
URL: https://issues.jboss.org/browse/JBIDE-21743
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: project-examples
Affects Versions: 4.3.1.CR1
Reporter: Radim Hopp
Assignee: Rob Stryker
Importing "spring-kitchensink-basic" EAP7 quickstart raises an error:
{noformat}Description Resource Path Location Type
cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'context:component-scan'. jboss-as-spring-mvc-context.xml /jboss-spring-kitchensink-basic/src/main/webapp/WEB-INF line 26 XML Problem
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBTIS-561) Add SwitchYard feature to Fuse category
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-561?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-561:
--------------------------------
Assignee: Paul Leacu
> Add SwitchYard feature to Fuse category
> ---------------------------------------
>
> Key: JBTIS-561
> URL: https://issues.jboss.org/browse/JBTIS-561
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 9.0.0.Beta1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> Since there is only one product called JBoss Fuse which also includes SwitchYard I suggest to extend JBoss Fuse Development category by SwitchYard tooling. The category JBoss Integration and SOA Development can be removed (BPEL and BPMN2 modelers are installed together with SwitchYard tooling).
> If we extend the Fuse category then please extend com.jboss.devstudio.integration-stack.fuse.feature as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month