[JBoss JIRA] (JBDS-3197) Cannot connect to server running on localhost from internal web browser with org.jboss.tools.vpe.loadxulrunner=false
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3197?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3197:
-------------------------------
Summary: Cannot connect to server running on localhost from internal web browser with org.jboss.tools.vpe.loadxulrunner=false (was: Cannot connect to server running on localhost from internal web browser in JBDS8)
> Cannot connect to server running on localhost from internal web browser with org.jboss.tools.vpe.loadxulrunner=false
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3197
> URL: https://issues.jboss.org/browse/JBDS-3197
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: server
> Affects Versions: 8.0.0.GA
> Environment: RHEL 6
> JBDS 8.0 GA
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Attachments: JBDS.png, JBT.png
>
>
> To recreate the problem:
> * Install JBDS 8 with the embedded EAP server
> * Create a new project - such as "start from scratch html5 kitchensink"
> * Start the embeded EAP server
> * Deploy the project to the server
> * Open the project URL - http://localhost:8080/jboss-as-kitchensink-html5-mobile/ in the internal web browser
> * This error is displayed in the internal browser view: Cannot connect to destination
> * Nothing is written to the eclipse .log
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3198) HHH000389: Unsuccessful: drop sequence hibernate_sequence - deploying new "from scratch" HRML5 project
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3198?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3198:
------------------------------------
This is a known issue - https://issues.jboss.org/browse/WFLY-811 - we should document this for JBDS users.
> HHH000389: Unsuccessful: drop sequence hibernate_sequence - deploying new "from scratch" HRML5 project
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3198
> URL: https://issues.jboss.org/browse/JBDS-3198
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
>
> Seeing this error when a newly created (default) HTML5 is created from Central and deployed to EAP.
> 10:23:12,277 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000227: Running hbm2ddl schema export
> 10:23:12,281 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: drop sequence hibernate_sequence
> 10:23:12,281 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
> drop sequence hibernate_sequence [90036-168]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3198) HHH000389: Unsuccessful: drop sequence hibernate_sequence - deploying new "from scratch" HRML5 project
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-3198:
----------------------------------
Summary: HHH000389: Unsuccessful: drop sequence hibernate_sequence - deploying new "from scratch" HRML5 project
Key: JBDS-3198
URL: https://issues.jboss.org/browse/JBDS-3198
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: central
Affects Versions: 8.0.0.GA
Reporter: Len DiMaggio
Assignee: Fred Bricon
Seeing this error when a newly created (default) HTML5 is created from Central and deployed to EAP.
10:23:12,277 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000227: Running hbm2ddl schema export
10:23:12,281 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: drop sequence hibernate_sequence
10:23:12,281 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
drop sequence hibernate_sequence [90036-168]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3198) HHH000389: Unsuccessful: drop sequence hibernate_sequence - deploying new "from scratch" HRML5 project
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3198?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3198:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
CDW pm_ack: ?
CDW qa_ack: ?
CDW release: ?
> HHH000389: Unsuccessful: drop sequence hibernate_sequence - deploying new "from scratch" HRML5 project
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3198
> URL: https://issues.jboss.org/browse/JBDS-3198
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
>
> Seeing this error when a newly created (default) HTML5 is created from Central and deployed to EAP.
> 10:23:12,277 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000227: Running hbm2ddl schema export
> 10:23:12,281 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) HHH000389: Unsuccessful: drop sequence hibernate_sequence
> 10:23:12,281 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 48) Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
> drop sequence hibernate_sequence [90036-168]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18703) Browsersim: Need to add javaFx web engine support for standalone mode
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18703?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18703:
------------------------------------------------
Proof of concept is already created. Unfortunately, it doesn't work under Linux with openjdk, but works fine with Oracle jdk.
> Browsersim: Need to add javaFx web engine support for standalone mode
> ---------------------------------------------------------------------
>
> Key: JBIDE-18703
> URL: https://issues.jboss.org/browse/JBIDE-18703
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.2.0.Final
> Reporter: Ilya Buziuk
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> What need to be done here:
> 1. add all required jetty dependencies to build
> 2. Change Browsersim code a bit
> 3. Add javafx mocks only in case if javafx is not available(openjdk case)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18572:
------------------------------------------------
[~xcoulon], [~andrei.ivanov] I just install 4.2.0.Final to 64bit Luna sr1 on windows, run it with 64bit java, then import a project(downloaded from github), make some local changes and call "Compare With" HEAD revision. Everything is OK. Am I doing smth wrong?
> NPE while calling a diff between 2 versions of a JS file
> --------------------------------------------------------
>
> Key: JBIDE-18572
> URL: https://issues.jboss.org/browse/JBIDE-18572
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.3.0.Alpha1
>
>
> Not sure if the error is related {{summarry}}, but here's the stacktrace:
> I did compare my current JS file with the first version in my history, which was an empty file, then I called the diff with the next version and I got this error. I kept having this error when comparing the current version with any other version of the file (if that can help to reproduce/identify the problem)
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:572)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.access$0(VpvEditor.java:551)
> at org.jboss.tools.vpe.preview.editor.VpvEditor$EditorListener.partInputChanged(VpvEditor.java:674)
> at org.eclipse.ui.internal.WorkbenchPage$28.run(WorkbenchPage.java:5151)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartInputChanged(WorkbenchPage.java:5148)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$4.propertyChanged(CompatibilityPart.java:369)
> at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:132)
> at org.eclipse.compare.internal.CompareEditor.doSetInput(CompareEditor.java:313)
> at org.eclipse.compare.internal.CompareEditor.setInput(CompareEditor.java:254)
> at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:546)
> at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1413)
> at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:567)
> at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:537)
> at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:526)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:199)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:180)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.openInCompare(CompareRevisionAction.java:139)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.run(CompareRevisionAction.java:102)
> at org.eclipse.team.internal.ui.history.LocalHistoryPage$9.open(LocalHistoryPage.java:414)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:853)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:850)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1142)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1249)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:484)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (TOOLSDOC-553) Step 2 in this section refers to incorrect package name
by Len DiMaggio (JIRA)
Len DiMaggio created TOOLSDOC-553:
-------------------------------------
Summary: Step 2 in this section refers to incorrect package name
Key: TOOLSDOC-553
URL: https://issues.jboss.org/browse/TOOLSDOC-553
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Environment: Build Name: 22960, Start Developing-8.0
Build Date: 22-10-2014 11:29:36
Topic ID: 13791-717241 [Latest]
Reporter: Len DiMaggio
Assignee: Michelle Murray
Title: Add an Entity Using Forge Tools
Describe the issue:
Step 2 in this section refers to:
Click org.jboss.jdf.example.ticketmonster and press Ctrl+4 (Cmd+4).
The correct package name is:
org.jboss.jdf.example.ticketmonster.model
Suggestions for improvement:
Additional information:
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-293?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-293.
-----------------------------------
Verified with JBDS 8.0.0.GA + JBDS-IS 8.0.0.Beta1
> Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTIS-293
> URL: https://issues.jboss.org/browse/JBTIS-293
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE
> Affects Versions: 4.2.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 8.0.0.Alpha2, 4.2.0.Alpha2
>
>
> If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don't get this error.
> SESSION 2014-07-30 09:22:59.386 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_60-ea
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975]
> Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model
> -> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"
> org.fusesource.ide.camel.model [977]
> No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> require: (osgi.wiring.bundle=org.eclipse.core.runtime)
> |
> provide: osgi.wiring.bundle: org.eclipse.core.runtime
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"]
> Chain 2:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> import: (osgi.wiring.package=org.fusesource.camel.tooling.util)
> |
> export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model
> io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"]
> import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0))))
> |
> export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters
> org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"]
> import: (osgi.wiring.package=javax.xml.bind.annotation.adapters)
> |
> export: osgi.wiring.package: javax.xml.bind.annotation.adapters
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months