[JBoss JIRA] (JBDS-3937) NPE in Web Service Tester
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3937?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBDS-3937:
------------------------------------
Affects Version/s: 10.0.0.GA
> NPE in Web Service Tester
> -------------------------
>
> Key: JBDS-3937
> URL: https://issues.jboss.org/browse/JBDS-3937
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 10.0.0.GA
> Environment: Version: 10.0.0.GA
> Build id: GA-v20160603-1025-B5510
> Reporter: Andrej Podhradsky
>
> NPE in Web Service Tester when calling SOAP WS.
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1909)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1809)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1726)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> Note that this works fine in JBDS 9.1.0.GA
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22362:
------------------------------------------
I can replicate this with yesterdays CDK (rhel-7-cdk-vagrant-scratch-7.2.07062016-1.x86_64.vagrant-libvirt.box).
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.Alpha1
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3834) Install fail - what next?
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3834:
---------------------------------
I was just testing the 10.0 GA Platform installer and came across the same issue again. Is there any resolution coming for the GA build or do we need to advice users about in docs what to do if one part fails, since there is no apparent graceful way to exit or retry yet.
> Install fail - what next?
> -------------------------
>
> Key: JBDS-3834
> URL: https://issues.jboss.org/browse/JBDS-3834
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.0.0.GA
>
> Attachments: fail_install.PNG
>
>
> Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22362:
-------------------------------------
Fix Version/s: 4.4.1.Alpha1
(was: 4.4.x)
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.Alpha1
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-742) Update Teiid Designer in Devstudio IS 10.0.0.Alpha1
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-742:
---------------------------------------
Summary: Update Teiid Designer in Devstudio IS 10.0.0.Alpha1
Key: JBTIS-742
URL: https://issues.jboss.org/browse/JBTIS-742
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: build, teiid
Affects Versions: 4.4.0.Alpha1
Reporter: Andrej Podhradsky
Assignee: Paul Leacu
Please update the version of Teiid Designer to 10.0.1.Beta1 in Devstudio IS 10.0.0.Alpha1-SNAPSHOT. My point is not to have older version of TD in Neon (TD 10.0.0.Beta3) than in Mars (TD 10.0.1.Beta1).
Moreover, this will help QE to use the same tests for both Mars and Neon at the moment. Currently, this is not possible since there is a different 'New Project' wizard in TD 10.0.1.Beta1.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ]
Radim Hopp commented on JBDS-3924:
----------------------------------
I tried to reproduce it on my Fedora23 machine with openjdk version "1.8.0_91" with no success.
btw. Misha, you say you have Fedora 23, but the java package is for fedora 22 (notice the f22 in the package). But anyway... I don't think this could matter.
> Installation looks incomplete but is actually completed
> -------------------------------------------------------
>
> Key: JBDS-3924
> URL: https://issues.jboss.org/browse/JBDS-3924
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.GA
> Environment: Fedora 23
> Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
> jvm: java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Labels: install, installation, installer
> Fix For: 10.x
>
> Attachments: devstudio10install.png, incomplete_install.png
>
>
> Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months