February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19168) Exception thrown when external HTML opened in VPE

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19168?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19168. ------------------------------- Verified with JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Exception thrown when external HTML opened in VPE > ------------------------------------------------- > > Key: JBIDE-19168 > URL: https://issues.jboss.org/browse/JBIDE-19168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.1.CR1 > Environment: JBDS 8.0.1.CR1-v20141124-0632-B333 Linux 64bit > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Fix For: 4.3.0.Alpha1 > > > 1. Install AngulaJS for Eclipse from JBoss Central > 2. Open external HTML file in VPE > ERROR: > {noformat} > IFile parameter can not be null > org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: IFile parameter can not be null > at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1272) > at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:126) > at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:118) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) > at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) > at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) > at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18584) New beans.xml should let the user choose the CDI version

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18584?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-18584. ------------------------------------ Verified in JBDS 9.0.0.Alpha1-v20150216-1042-B11 > New beans.xml should let the user choose the CDI version > --------------------------------------------------------- > > Key: JBIDE-18584 > URL: https://issues.jboss.org/browse/JBIDE-18584 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: NewBeansXMLWizard.png, scr.png > > > The "New beans.xml" wizard generates the following content: > {code} > <?xml version="1.0"?> > <beans xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://jboss.org/schema/cdi/beans_1_0.xsd"/> > {code} > but Java EE 7 includes CDI 1.1 which is like > {code} > <beans xmlns="http://xmlns.jcp.org/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd" > version="1.1" bean-discovery-mode="annotated"> > </beans> > {code} > It would be nice if the wizard supported multiple versions of CDI (with the default value based on the CDI project facet ?) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17394) Add New>Maven Project in the menus

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17394?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-17394. ------------------------------------ verified in JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Add New>Maven Project in the menus > ---------------------------------- > > Key: JBIDE-17394 > URL: https://issues.jboss.org/browse/JBIDE-17394 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.2.0.Beta2 > Reporter: Xavier Coulon > Assignee: Fred Bricon > Fix For: 4.3.0.Alpha1 > > Attachments: NewProjectMenu.png > > > in the JBoss and JavaEE perspectives, could we have "File>New>Maven Project" and "New>Maven Project" along with other types of project ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18879) Replace With -> Local History ... doesn't change editor content.

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18879?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18879. ------------------------------- Veriified > Replace With -> Local History ... doesn't change editor content. > ---------------------------------------------------------------- > > Key: JBIDE-18879 > URL: https://issues.jboss.org/browse/JBIDE-18879 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Final > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha1 > > > "Replace With -> Local History ... " change content of the file, but opened editor content is not updated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17632) Support rendering of JSF widgets in preview mode of VPE editor

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17632?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17632. ------------------------------- Verified > Support rendering of JSF widgets in preview mode of VPE editor > -------------------------------------------------------------- > > Key: JBIDE-17632 > URL: https://issues.jboss.org/browse/JBIDE-17632 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Environment: Mac OS X Mavericks, Oracle JDK 7u60, Oracle JDK 8u5 > Reporter: Vineet Reynolds > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha1 > > Attachments: PreviewMode-JBDS8.jpg, visual_page_editor.png > > > JSF input widgets in XHTML files are rendered as plain text, when viewed in Visual mode of the JBoss Tools HTML editor. > This is a side-effect of using tha WebKit engine in Mac, to perform the rendering: > {noformat} > kmarmaliykov: vineetr: Now everything is rendered using modern webkit engine. It works perfect for HTML5 pages but hasn't support jsf tags > {noformat} > This is being raised as a tracker issue for JBDS 8, since: > {noformat} > kmarmaliykov: vineetr: For JBDS8 the main goal was to provide good preview for html5 pages > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19210) Visual Editor New and Noteworthy for 4.3.0.Alpha1

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19210?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19210. ------------------------------- Verified on GitHub > Visual Editor New and Noteworthy for 4.3.0.Alpha1 > ------------------------------------------------- > > Key: JBIDE-19210 > URL: https://issues.jboss.org/browse/JBIDE-19210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core, visual-page-editor-templates > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Visual Editor is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Visual Editor by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18809) Visual Editor: Need to handle external html / htm files

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18809?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18809. ------------------------------- Verified with JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Visual Editor: Need to handle external html / htm files > ------------------------------------------------------- > > Key: JBIDE-18809 > URL: https://issues.jboss.org/browse/JBIDE-18809 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Reporter: Ilya Buziuk > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha1 > > > Now VPE / HTML Preview can handle only workspace's files. Need to add external files support > When I open html pages outside eclipse workspace I get an error stating VPE preview cannot open the file. > That is not ok. > preview should be able to just fine preview the html no matter where the content is from and if it is because some current limitation about preview then users should at least be able to edit files even if external to the workspace. > by external to workspace I mean what is opened with File > Open File... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18784) Remove macosx/cocoa/c86 feature from VPE requirements

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18784?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18784. ------------------------------- Verified > Remove macosx/cocoa/c86 feature from VPE requirements > ----------------------------------------------------- > > Key: JBIDE-18784 > URL: https://issues.jboss.org/browse/JBIDE-18784 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Alpha1 > > > With adoption of Mars M3, we drop macosx/cocoa/x86 (non-64 bits) platform, VPE fails at resolving its dependencies because it contains a reference to a macosx/cocoa/x86 feature. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18600) NPE occurs in EclipseResourceUtil in case Project navigator contains elements that doesn't map to local file system

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18600?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18600. ------------------------------- Verified with JBDS 9.0.0.Alpha1-v20150216-1042-B11 > NPE occurs in EclipseResourceUtil in case Project navigator contains elements that doesn't map to local file system > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18600 > URL: https://issues.jboss.org/browse/JBIDE-18600 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.CR2 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > {code}java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:367) > at org.jboss.tools.jst.web.ui.navigator.XContentProvider.hasChildren(XContentProvider.java:96) > at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.hasChildren(SafeDelegateTreeContentProvider.java:110) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.callNormalHasChildren(NavigatorContentServiceContentProvider.java:430) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.access$4(NavigatorContentServiceContentProvider.java:425) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$3.run(NavigatorContentServiceContentProvider.java:395) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:381) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:422) > at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2133) > at org.eclipse.jface.viewers.TreeViewer.isExpandable(TreeViewer.java:553) > at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2171) > at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2863) > at org.eclipse.jface.viewers.TreeViewer.updatePlus(TreeViewer.java:804) > at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:844) > at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:818) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791) > at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762) > at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1495) > at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:903) > at org.eclipse.jface.viewers.AbstractTreeViewer$4.treeExpanded(AbstractTreeViewer.java:1507) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:132) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) > at org.eclipse.swt.widgets.Tree.gtk_test_expand_row(Tree.java:2084) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2130) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4706) > at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18548) Image dropped to VPE is not rendered on server

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18548?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-18548. ------------------------------- Verified with JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Image dropped to VPE is not rendered on server > ---------------------------------------------- > > Key: JBIDE-18548 > URL: https://issues.jboss.org/browse/JBIDE-18548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.CR2 > Environment: JBT 4.2.0.CR2-v20141005-0541-B267 > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Open index.html page > 3. Drag&drop some image from img subdirectory to source part of VPE > ASSERT: Image is displayed in visual part of VPE > 4. Run project on server > ERROR: Dropped Image is not rendered in web browser > Once leading "/" is removed from img tag source attribute droped image is rendered on web page deployed to server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2015