July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17860) Custom components in components.xml yield XML validation problem in JBDS in a Seam project

by Ron Šmeral (JIRA)

Ron Šmeral created JBIDE-17860: ---------------------------------- Summary: Custom components in components.xml yield XML validation problem in JBDS in a Seam project Key: JBIDE-17860 URL: https://issues.jboss.org/browse/JBIDE-17860 Project: Tools (JBoss Tools) Issue Type: Bug Components: seam2 Environment: JBDS 8.0.0.Beta3 Reporter: Ron Šmeral For a components.xml file which contains custom components which define their namespace using the {{@Namespace}} annotation, JBDS shows XML Problems: {code:java|title=src/main/java/org/jboss/seam/example/quartz/package-info.java} @Namespace(value="http://jboss.org/schema/seam/examples/quartz") package org.jboss.seam.example.quartz; import org.jboss.seam.annotations.*; {code} {code:java|title=PaymentHome.java} @Name("paymentHome") public class PaymentHome extends EntityHome<Payment> { ... {code} {code:xml|title=components-test.xml} <?xml version="1.0" encoding="UTF-8"?> <components xmlns="http://jboss.org/schema/seam/components" xmlns:pay="http://jboss.org/schema/seam/examples/quartz" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://jboss.org/schema/seam/components http://jboss.org/schema/seam/components-2.3.xsd"> <pay:payment-home name="paymentHome" new-instance="#{newPayment}" created-message="Created a new payment to #{newPayment.payee}" /> ... </components> {code} JBDS shows: {noformat} cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'pay:payment-home'. components-test.xml /quartz-ejb/src/test/resources line 18 XML Problem {noformat} This does not happen when the schemaLocation of components is not included. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17840) Eclipse Thym release should be able to replace JBDS hybrid mobile tools

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17840?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-17840: ------------------------------------ Assignee: Gorkem Ercan > Eclipse Thym release should be able to replace JBDS hybrid mobile tools > ----------------------------------------------------------------------- > > Key: JBIDE-17840 > URL: https://issues.jboss.org/browse/JBIDE-17840 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.2.0.CR1 > > > Releases from Eclipse Thym should be able to update JBDS 4.2.0 Beta3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17262) Visual Preview Throws socket exceptions on visual part resize

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17262?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17262. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > Visual Preview Throws socket exceptions on visual part resize > ------------------------------------------------------------- > > Key: JBIDE-17262 > URL: https://issues.jboss.org/browse/JBIDE-17262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta3 > > > VpvSocketProcessor catches IOException in > {code}private void sendOkResponse(String header, DataOutputStream outputToclient, String text){code} > method during visual part resize. It happens obviously because of browser.setUrl call. It drops current connection and opens new one leading to failures in all opened streams for previous socket. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17572) 404 not found in VPE / HTML preview for projects which names have spaces

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17572?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17572. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > 404 not found in VPE / HTML preview for projects which names have spaces > -------------------------------------------------------------------------- > > Key: JBIDE-17572 > URL: https://issues.jboss.org/browse/JBIDE-17572 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta3 > > > Need to properly escape special characters on server side such as *%20* -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17724: ------------------------------------- > Rob - if there is no way for wtp to detect #4 has changed and thus #3 need to publish - how does an #1 know it needs to publish when #2 changes ? Or is this the same problem ? WTP detects in advance what the situation is for each module and submodule. The problem is, when it calls me, it only calls one module at a time. So WTP knows in advance that the utility project has no change, and util2 has changes, but *I* don't know that. Now, if all 4 projects were exploded, this wouldn't be a problem. I could make no changes to project 3, and then make changes to project 4. But in this case, project 4 must live inside project 3, which means project 3 must know about the changes in it. I believe I have utilities somewhere to discover the flags for child modules, or its burried inside the zip runner... but there *is* a way. It's not impossible. I need to work on the test cases, though. > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta3, 4.2.0.CR1 > > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17467) Visual Page Editor: CoreException Caused by ClassCastException

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17467?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17467. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > Visual Page Editor: CoreException Caused by ClassCastException > -------------------------------------------------------------- > > Key: JBIDE-17467 > URL: https://issues.jboss.org/browse/JBIDE-17467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Environment: Ubutnu 64bit > Reporter: Daniel Azarov > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Beta3 > > > Test Case: > 1. Create project > 2. Create html file > 3. Open file in Visual Page Editor > 4. Select any text in the Editor > 5. Right Click on selected text > FAIL: > {code} > !ENTRY org.eclipse.ui 4 4 2014-05-28 11:13:43.858 > !MESSAGE Class load Failure: 'org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem' > !ENTRY org.eclipse.ui 4 0 2014-05-28 11:13:43.858 > !MESSAGE Class load Failure: 'org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem' > !STACK 1 > org.eclipse.core.runtime.CoreException: Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem". > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:873) > at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.createContributionItem(DynamicMenuContributionItem.java:156) > at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.getContributionItem(DynamicMenuContributionItem.java:149) > at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:128) > at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:780) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:861) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:721) > at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:609) > at org.eclipse.ui.internal.PopupMenuExtender.addMenuContributions(PopupMenuExtender.java:423) > at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:393) > at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:352) > at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:492) > at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:487) > at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:519) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462) > 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:1393) > at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198) > at org.eclipse.swt.widgets.Display.runPopups(Display.java:3848) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3406) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578) > 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:379) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233) > 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:601) > 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) > Caused by: java.lang.ClassCastException: org.jboss.tools.vpe.preview.editor.VpvEditorPart cannot be cast to org.jboss.tools.vpe.editor.VpeEditorPart > at org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem.<init>(SetupTemplateContributionItem.java:56) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) > ... 48 more > !SUBENTRY 1 org.eclipse.equinox.registry 4 1 2014-05-28 11:13:43.859 > !MESSAGE Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem". > !STACK 0 > java.lang.ClassCastException: org.jboss.tools.vpe.preview.editor.VpvEditorPart cannot be cast to org.jboss.tools.vpe.editor.VpeEditorPart > at org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem.<init>(SetupTemplateContributionItem.java:56) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:873) > at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.createContributionItem(DynamicMenuContributionItem.java:156) > at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.getContributionItem(DynamicMenuContributionItem.java:149) > at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:128) > at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:780) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:861) > at org.eclipse.jface.action.MenuManager.update(MenuManager.java:721) > at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:609) > at org.eclipse.ui.internal.PopupMenuExtender.addMenuContributions(PopupMenuExtender.java:423) > at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:393) > at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:352) > at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:492) > at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:487) > at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:519) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462) > 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:1393) > at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198) > at org.eclipse.swt.widgets.Display.runPopups(Display.java:3848) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3406) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578) > 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:379) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233) > 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:601) > 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.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17563) Visual part of VPE is blank when JSP page opened

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17563?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17563. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > Visual part of VPE is blank when JSP page opened > ------------------------------------------------ > > Key: JBIDE-17563 > URL: https://issues.jboss.org/browse/JBIDE-17563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Environment: JBDS Beta2-v20140608-1040-B121, Linux > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.Beta3 > > > 1. Create JSF12 Kick start project > 2. Open inputUserName.jsp in JBoss Tools JSP Editor > ERROR: Visual part of editor is blank > 3. Add some text to source of page > ERROR: Visual part of editor is blank -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17846) Seam configurator doesnt set seam runtime

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17846?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-17846: ----------------------------------- Assignee: Fred Bricon > Seam configurator doesnt set seam runtime > ----------------------------------------- > > Key: JBIDE-17846 > URL: https://issues.jboss.org/browse/JBIDE-17846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.2.0.Beta2 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17859) XML validation error for a web service configuration XML file in a Seam project

by Ron Šmeral (JIRA)

Ron Šmeral created JBIDE-17859: ---------------------------------- Summary: XML validation error for a web service configuration XML file in a Seam project Key: JBIDE-17859 URL: https://issues.jboss.org/browse/JBIDE-17859 Project: Tools (JBoss Tools) Issue Type: Bug Components: seam2 Environment: JBDS 8.0.0.Beta3 Reporter: Ron Šmeral {noformat} cvc-elt.1: Cannot find the declaration of element 'handler-chains'. soap-handlers.xml /seambay-ejb/src/main/resources/org/jboss/seam/example/seambay line 2 XML Problem {noformat} The file is valid and satisfies the webservices schema in the javaee namespace: http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_...: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <handler-chains xmlns="http://java.sun.com/xml/ns/javaee"> <handler-chain> <handler> <handler-name>SOAP Request Handler</handler-name> <handler-class>org.jboss.seam.webservice.SOAPRequestHandler</handler-class> </handler> </handler-chain> </handler-chains> {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17447) VPE doesn't show properly UTF characters with diacritics

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17447?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17447. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > VPE doesn't show properly UTF characters with diacritics > -------------------------------------------------------- > > Key: JBIDE-17447 > URL: https://issues.jboss.org/browse/JBIDE-17447 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104 Linux 64 bit > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.2.0.Beta3 > > > 1. Open HTML page and add some characters with diacritics for example ľščťž using source pane > ERROR: characters are not properly displayed within visual pane -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 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 July 2014