[JBoss JIRA] (JBIDE-26688) "jaxws-retail" quickstart from Red Hat Central shows errors after import
by Zbyněk Červinka (Jira)
Zbyněk Červinka created JBIDE-26688:
---------------------------------------
Summary: "jaxws-retail" quickstart from Red Hat Central shows errors after import
Key: JBIDE-26688
URL: https://issues.jboss.org/browse/JBIDE-26688
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.12.0.AM1
Environment: OS X 10.14.5
Reporter: Zbyněk Červinka
Assignee: Jeff MAURY
*"jaxws-retail" quickstart from Red Hat Central shows errors after import*
*jboss-jaxws-retail-client -> Client.java [unresolvable imports]:*
import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.Customer;
import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.DiscountRequest;
import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.DiscountResponse;
import org.jboss.quickstarts.ws.jaxws.samples.retail.profile.ProfileMgmt;
*jboss-jaxws-retail-service -> ProfileMgmtBean.java:*
*DiscountResponse* cannot be resolved to a type
*jboss-jaxws-retail-service - > pom.xml:*
Error while running wsconsume.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26685) Create Hibernate Console Configuration wizard doesnt Finish
by Koen Aers (Jira)
[ https://issues.jboss.org/browse/JBIDE-26685?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-26685:
-----------------------------------
Hi [~snarff], would it be possible to attach a minimal program for which this happens? Also, can you specify the version of Java and the platform that you are using?
> Create Hibernate Console Configuration wizard doesnt Finish
> -----------------------------------------------------------
>
> Key: JBIDE-26685
> URL: https://issues.jboss.org/browse/JBIDE-26685
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.11.0.Final
> Reporter: Izak van Langevelde
> Assignee: Koen Aers
> Priority: Major
> Fix For: 4.12.x
>
>
> When filling out the main wizard form, pressing Finish generates an unhandled event loop exception if the Hibernate version is set too high: nothing happens. This renders creating the cfg.xml file impossible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-20346) Jts and jts-distributed-crash-rec quickstarts (EAP 6.4) contains XML validation errors
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-20346:
------------------------------------
Summary: Jts and jts-distributed-crash-rec quickstarts (EAP 6.4) contains XML validation errors (was: Jts quickstart (EAP 6.4) contains XML validation errors)
> Jts and jts-distributed-crash-rec quickstarts (EAP 6.4) contains XML validation errors
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.jboss.org/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.12.x
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26685) Create Hibernate Console Configuration wizard doesnt Finish
by Izak van Langevelde (Jira)
[ https://issues.jboss.org/browse/JBIDE-26685?page=com.atlassian.jira.plugi... ]
Izak van Langevelde commented on JBIDE-26685:
---------------------------------------------
File>New>Hibernate Configuration File (cfg.xml).
Next screen (Create Hibernate Configuration file (cfg.xml)): select project and leave the file name hibernate.cfg.xml as is. Select Next >
Next screen (Hibernate Configuration File (cfg.xml): leave Hibernate version (5.4) as is, select Get values from Connection, after which Driver class, Connection URL, Username and Password are correctly filled by the wizard. The Database dialect needs to be filled manually (My SQL).
Press Finish.
Nothing happens.
The screen Hibernate Configuration File remains visible.
The eclipse Error Log tab shows a red mark with "Unhandled event loop exception.", whenever Finish is pressed.
> Create Hibernate Console Configuration wizard doesnt Finish
> -----------------------------------------------------------
>
> Key: JBIDE-26685
> URL: https://issues.jboss.org/browse/JBIDE-26685
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.11.0.Final
> Reporter: Izak van Langevelde
> Assignee: Koen Aers
> Priority: Major
> Fix For: 4.12.x
>
>
> When filling out the main wizard form, pressing Finish generates an unhandled event loop exception if the Hibernate version is set too high: nothing happens. This renders creating the cfg.xml file impossible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26408) Server adapter: debugging fails for nodejs-mongo-persistent template based application
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26408:
------------------------------------------
There's currently no support for Node.js > 7 in Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907
Given this situation we should inform the users that if they're using a newer Node.js debugging wont work. Otherwise they have it just failing without any clue why it doesnt and what to do about it. I thus added a warning (that one can decide not to get bothered any more about): https://github.com/jbosstools/jbosstools-openshift/pull/1848
> Server adapter: debugging fails for nodejs-mongo-persistent template based application
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-26408
> URL: https://issues.jboss.org/browse/JBIDE-26408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Environment: cdk-3.6.0+
> Reporter: André Dietisheim
> Assignee: Jeff MAURY
> Priority: Major
> Labels: node, server_adapter
> Fix For: 4.12.x
>
> Attachments: change-nodejs-version.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: have cdk 3.6.0
> # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it
> # EXEC: start the server adapter
> # ASSERT: server adapter is *[Started, Synchronized]*
> # EXEC: Restart the adapter into debugging
> Result:
> You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect.
> !screenshot-1.png!
> The debugger is therefore stopped, debugging wont work.
> !screenshot-2.png!
> Trying to restart it reproduces the error that we already have.
> In the Eclipse log you'll find the following:
> {code}
> java.io.IOException: Timed out waiting for handshake
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:134)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> Caused by: java.util.concurrent.TimeoutException
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26408) Server adapter: debugging fails for nodejs-mongo-persistent template based application
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26408:
-------------------------------------
Bugzilla References: https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907
Environment: cdk-3.6.0+ (was: cdk-3.6.0)
> Server adapter: debugging fails for nodejs-mongo-persistent template based application
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-26408
> URL: https://issues.jboss.org/browse/JBIDE-26408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Environment: cdk-3.6.0+
> Reporter: André Dietisheim
> Assignee: Jeff MAURY
> Priority: Major
> Labels: node, server_adapter
> Fix For: 4.12.x
>
> Attachments: change-nodejs-version.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: have cdk 3.6.0
> # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it
> # EXEC: start the server adapter
> # ASSERT: server adapter is *[Started, Synchronized]*
> # EXEC: Restart the adapter into debugging
> Result:
> You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect.
> !screenshot-1.png!
> The debugger is therefore stopped, debugging wont work.
> !screenshot-2.png!
> Trying to restart it reproduces the error that we already have.
> In the Eclipse log you'll find the following:
> {code}
> java.io.IOException: Timed out waiting for handshake
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:134)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> Caused by: java.util.concurrent.TimeoutException
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4774) User creates Camel REST definition he can't start, errors are thrown.
by Aurélien Pupier (Jira)
[ https://issues.jboss.org/browse/JBDS-4774?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier reassigned JBDS-4774:
-------------------------------------
Assignee: (was: Aurélien Pupier)
> User creates Camel REST definition he can't start, errors are thrown.
> ---------------------------------------------------------------------
>
> Key: JBDS-4774
> URL: https://issues.jboss.org/browse/JBDS-4774
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: fusetools
> Affects Versions: 12.11.0.GA
> Environment: I'm assuming this affects all environments.
> Reporter: Bruno Meseguer
> Priority: Minor
> Fix For: 12.x
>
>
> UI experience:
> > customer/user can't run the route.
> > he does not understand what he did wrong
> > he doesn't know how to fix it
> expected:
> > REST Configuration always defined before REST operations in XML.
> workaround:
> > manually switch order of elements
> > (or) don't delete default route before REST is defined.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26685) Create Hibernate Console Configuration wizard doesnt Finish
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26685?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-26685:
------------------------------------------
[~snarff] Could you please provide the exception that you see? Ideally also the steps (with the values that you provide) so that we can reproduce this? Unless this always happens in any case it's almost impossible for us to reproduce and fix this.
> Create Hibernate Console Configuration wizard doesnt Finish
> -----------------------------------------------------------
>
> Key: JBIDE-26685
> URL: https://issues.jboss.org/browse/JBIDE-26685
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.11.0.Final
> Reporter: Izak van Langevelde
> Assignee: Koen Aers
> Priority: Major
> Fix For: 4.12.x
>
>
> When filling out the main wizard form, pressing Finish generates an unhandled event loop exception if the Hibernate version is set too high: nothing happens. This renders creating the cfg.xml file impossible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months