[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-18950:
-----------------------------------------
I like this wizard but I'd appreciate the possibility to select abstract class (of course it would be a descendant of the proper abstract class) or interface. I'll create separate issue for that.
Other than that, wizard looks OK.
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
> Attachments: artifact.png, BatchArtifact.png, BatchArtifactWizBan.png
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Name: [text]
> - Artifact: [combo]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> - Artifact loader: [radio] @Named [radio] batch.xml [radio] Class loader
> - Artifact name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [list editor with 'Add' and 'Remove' buttons]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
> !artifact.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-18950.
-----------------------------------
Verified JBDS 9.0.0.beta1
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
> Attachments: artifact.png, BatchArtifact.png, BatchArtifactWizBan.png
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Name: [text]
> - Artifact: [combo]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> - Artifact loader: [radio] @Named [radio] batch.xml [radio] Class loader
> - Artifact name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [list editor with 'Add' and 'Remove' buttons]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
> !artifact.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19954) Connection wizard: connecting to a server configured for basic auth with Oauth scheme provides no indication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19954?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19954:
-------------------------------------
Summary: Connection wizard: connecting to a server configured for basic auth with Oauth scheme provides no indication (was: Connecting to a server configured for basic auth with Oauth scheme provides no indication)
> Connection wizard: connecting to a server configured for basic auth with Oauth scheme provides no indication
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19954
> URL: https://issues.jboss.org/browse/JBIDE-19954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: connection-wiazrd.png
>
>
> # ASSERT: make sure you have an openshift server configured to basic auth (only, no oauth)
> # EXEC: Launch connection wizard, create a new connection, use url of this server in "Server Url" and server type to "OpenShift v3".
> # EXEC: in "Authentication" details pane hit the "retrieve link"
> Result:
> The progress bar shows up for a short time and disappears right afterwards. There's no info in the wizard that tells you why retrieval didnt show up the browser.
> Expected result:
> There's an error that tells you that the local server doesnt support oauth and that you should use basic auth.
> !connection-wiazrd.png!
> It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19954) Connection wizard: connecting to a server configured for basic auth with Oauth scheme provides no indication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19954?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19954:
-------------------------------------
Labels: connection_wizard openshift_v3 (was: )
> Connection wizard: connecting to a server configured for basic auth with Oauth scheme provides no indication
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19954
> URL: https://issues.jboss.org/browse/JBIDE-19954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: connection-wiazrd.png
>
>
> # ASSERT: make sure you have an openshift server configured to basic auth (only, no oauth)
> # EXEC: Launch connection wizard, create a new connection, use url of this server in "Server Url" and server type to "OpenShift v3".
> # EXEC: in "Authentication" details pane hit the "retrieve link"
> Result:
> The progress bar shows up for a short time and disappears right afterwards. There's no info in the wizard that tells you why retrieval didnt show up the browser.
> Expected result:
> There's an error that tells you that the local server doesnt support oauth and that you should use basic auth.
> !connection-wiazrd.png!
> It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19996) [FeedHenry] Cannot create App in FH Cloud - Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19996?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-19996:
-------------------------------
Steps to Reproduce:
1) Create a Hybrid Mobile Application
2) Run the Create FH app wizard
3) in the wizard, select the app created in step 1,
4) Select FH project
5) Hit finish
> [FeedHenry] Cannot create App in FH Cloud - Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19996
> URL: https://issues.jboss.org/browse/JBIDE-19996
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.0.Beta1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: screen-fh.png
>
>
> {code}
> org.jboss.tools.feedhenry.ui.model.FeedHenryException: Unexpected error while communicating with aerogear-t.sandbox.feedhenry.com
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.doPostAPICall(FeedHenry.java:162)
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.importBareRepo(FeedHenry.java:110)
> at org.jboss.tools.feedhenry.ui.cordova.internal.wizards.NewApplicationWizard$1.run(NewApplicationWizard.java:99)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.feedhenry.ui.cordova.internal.wizards.NewApplicationWizard.performFinish(NewApplicationWizard.java:80)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> 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:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
> at java.net.InetAddress.getAllByName0(InetAddress.java:1259)
> at java.net.InetAddress.getAllByName(InetAddress.java:1171)
> at java.net.InetAddress.getAllByName(InetAddress.java:1105)
> at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
> at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:259)
> at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:159)
> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
> at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.doPostAPICall(FeedHenry.java:138)
> ... 65 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19996) [FeedHenry] Cannot create App in FH Cloud - Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19996?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-19996:
-------------------------------
Attachment: screen-fh.png
> [FeedHenry] Cannot create App in FH Cloud - Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19996
> URL: https://issues.jboss.org/browse/JBIDE-19996
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.0.Beta1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: screen-fh.png
>
>
> {code}
> org.jboss.tools.feedhenry.ui.model.FeedHenryException: Unexpected error while communicating with aerogear-t.sandbox.feedhenry.com
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.doPostAPICall(FeedHenry.java:162)
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.importBareRepo(FeedHenry.java:110)
> at org.jboss.tools.feedhenry.ui.cordova.internal.wizards.NewApplicationWizard$1.run(NewApplicationWizard.java:99)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.feedhenry.ui.cordova.internal.wizards.NewApplicationWizard.performFinish(NewApplicationWizard.java:80)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> 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:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
> at java.net.InetAddress.getAllByName0(InetAddress.java:1259)
> at java.net.InetAddress.getAllByName(InetAddress.java:1171)
> at java.net.InetAddress.getAllByName(InetAddress.java:1105)
> at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
> at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:259)
> at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:159)
> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
> at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.doPostAPICall(FeedHenry.java:138)
> ... 65 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19996) [FeedHenry] Cannot create App in FH Cloud - Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-19996:
----------------------------------
Summary: [FeedHenry] Cannot create App in FH Cloud - Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
Key: JBIDE-19996
URL: https://issues.jboss.org/browse/JBIDE-19996
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.3.0.Beta1
Reporter: Pavol Srna
Priority: Blocker
Fix For: 4.3.0.Beta1
{code}
org.jboss.tools.feedhenry.ui.model.FeedHenryException: Unexpected error while communicating with aerogear-t.sandbox.feedhenry.com
at org.jboss.tools.feedhenry.ui.model.FeedHenry.doPostAPICall(FeedHenry.java:162)
at org.jboss.tools.feedhenry.ui.model.FeedHenry.importBareRepo(FeedHenry.java:110)
at org.jboss.tools.feedhenry.ui.cordova.internal.wizards.NewApplicationWizard$1.run(NewApplicationWizard.java:99)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
at org.jboss.tools.feedhenry.ui.cordova.internal.wizards.NewApplicationWizard.performFinish(NewApplicationWizard.java:80)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
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:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.combox
at java.net.InetAddress.getAllByName0(InetAddress.java:1259)
at java.net.InetAddress.getAllByName(InetAddress.java:1171)
at java.net.InetAddress.getAllByName(InetAddress.java:1105)
at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:259)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:159)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
at org.jboss.tools.feedhenry.ui.model.FeedHenry.doPostAPICall(FeedHenry.java:138)
... 65 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19971:
------------------------------------------
[~mlabuda] To find out what really happens for you I'd love you to jstack Eclipse while it's waiting for the prompt in the command line. This would hopefully show me what thread in Eclipse is causing the prompt. Could you do that please?
> OSE v2 prompts user to enter kerberos credentials from command line while importing an application
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19971
> URL: https://issues.jboss.org/browse/JBIDE-19971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Blocker
> Attachments: authorized.png, creds_prompt.png, jstack.txt
>
>
> Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) the importing job in IDE is hanging. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
> Prompt from CLI looks like:
> Kerberos username [mlabuda]:
> Kerberos password for mlabuda:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19971:
-------------------------------------
Description:
Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) the importing job in IDE is hanging. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
Prompt from CLI looks like:
Kerberos username [mlabuda]:
Kerberos password for mlabuda:
was:
Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
Prompt from CLI looks like:
Kerberos username [mlabuda]:
Kerberos password for mlabuda:
> OSE v2 prompts user to enter kerberos credentials from command line while importing an application
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19971
> URL: https://issues.jboss.org/browse/JBIDE-19971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Blocker
> Attachments: authorized.png, creds_prompt.png, jstack.txt
>
>
> Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) the importing job in IDE is hanging. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
> Prompt from CLI looks like:
> Kerberos username [mlabuda]:
> Kerberos password for mlabuda:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months