July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17242) HTML validation should allow the 'role' attribute.

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17242?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17242. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > HTML validation should allow the 'role' attribute. > -------------------------------------------------- > > Key: JBIDE-17242 > URL: https://issues.jboss.org/browse/JBIDE-17242 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Joshua Wilson > Assignee: Victor Rubezhny > Priority: Minor > Fix For: 4.2.0.Beta3 > > > I found this out when trying to implement jQuery Mobile 1.4.2. There is over 20 different docs where they use the attribute 'role'. After looking into it, this is something that should be allowed by the HTML validator. The validator produces this warning, "Undefined attribute name (role)." > http://www.w3.org/TR/html5/dom.html#global-attributes states "To enable assistive technology products to expose a more fine-grained interface than is otherwise possible with HTML elements and attributes, a set of http://www.w3.org/TR/html5/dom.html#wai-aria can be specified (the ARIA http://www.w3.org/TR/html5/infrastructure.html#attr-aria-role and aria-* attributes). http://www.w3.org/TR/html5/references.html#refsARIA" > this is how it is linked to HTML5 : http://www.w3.org/TR/html5/dom.html#sec-implicit-aria-semantics > also see: http://www.w3.org/WAI/PF/aria/usage#usage_intro > A working example can be found in [contacts-mobile-basic|https://github.com/joshuawilson/jboss-wfk-quickstar...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17858) Can't resolve context variable of a built-in Seam component in imported Seam project

by Ron Šmeral (JIRA)

Ron Šmeral created JBIDE-17858: ---------------------------------- Summary: Can't resolve context variable of a built-in Seam component in imported Seam project Key: JBIDE-17858 URL: https://issues.jboss.org/browse/JBIDE-17858 Project: Tools (JBoss Tools) Issue Type: Bug Components: seam2 Environment: JBDS 8.0.0.Beta3 Reporter: Ron Šmeral Unknown context variable name: "topicPublisher" ChatRoomAction.java /chatroom-ejb/src/main/java/org/jboss/seam/example/remoting/chatroom line 26 Seam Problem -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17858) Can't resolve context variable of a built-in Seam component in imported Seam project

by Ron Šmeral (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17858?page=com.atlassian.jira.plugi... ] Ron Šmeral updated JBIDE-17858: ------------------------------- Steps to Reproduce: Import https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/remoting/chatroom (was: https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/remoting/chatroom) > Can't resolve context variable of a built-in Seam component in imported Seam project > ------------------------------------------------------------------------------------ > > Key: JBIDE-17858 > URL: https://issues.jboss.org/browse/JBIDE-17858 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Environment: JBDS 8.0.0.Beta3 > Reporter: Ron Šmeral > > Unknown context variable name: "topicPublisher" > ChatRoomAction.java > /chatroom-ejb/src/main/java/org/jboss/seam/example/remoting/chatroom > line 26 > Seam Problem -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17641) livereload server keeps telling me it cannot find a matching server when it should not matter

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17641?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17641. ------------------------------- > livereload server keeps telling me it cannot find a matching server when it should not matter > --------------------------------------------------------------------------------------------- > > Key: JBIDE-17641 > URL: https://issues.jboss.org/browse/JBIDE-17641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.2.Final > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > > Start livereload > run something like awestruct or some other external thing that is not a server in eclpse and open a browser with livereload enable in it. > Now everytime you change you get a warning printed in workspace log: > "could not identify server from client location <url>" > see http://screencast.com/t/9AsTuZ6uFT > Any chance of this simply not being logged or only log once per new url so it does not fill up and constantly trigger the workspace log ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17857) Can't resolve array subscript in EL expression in a Seam project

by Ron Šmeral (JIRA)

Ron Šmeral created JBIDE-17857: ---------------------------------- Summary: Can't resolve array subscript in EL expression in a Seam project Key: JBIDE-17857 URL: https://issues.jboss.org/browse/JBIDE-17857 Project: Tools (JBoss Tools) Issue Type: Bug Components: seam2 Environment: JBDS 8.0.0.Beta3 Reporter: Ron Šmeral In seambay example, this warning is shown: {noformat} "0" cannot be resolved AuctionTest.java /seambay-ejb/src/test/java/org/jboss/seam/example/seambay/test line 227 EL Knowledge Base Problem {noformat} for the following code: {code:java} Contexts.getEventContext().set("auction", getValue("#{auctionSearch.auctions[0]}")); {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17416) Livereload source plugin shouldn't embed external jars

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17416?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17416. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > Livereload source plugin shouldn't embed external jars > ------------------------------------------------------ > > Key: JBIDE-17416 > URL: https://issues.jboss.org/browse/JBIDE-17416 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.2.0.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.0.Beta3 > > > Livereload source plugin shouldn't embed external jars, this adds 1.0+MB unnecessary jars to the JBDS installer -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17681) Exception in static HTML project using angular.js

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17681?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17681. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > Exception in static HTML project using angular.js > ------------------------------------------------- > > Key: JBIDE-17681 > URL: https://issues.jboss.org/browse/JBIDE-17681 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.0.Beta2 > Environment: JBT 4.2.0.Beta2, Linux > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.2.0.Beta3 > > > 1. Create static html project > 2. Create index.html page with this content > {code:xml|title=WebContent/index.html|borderStyle=solid} > <!doctype html> > <html lang="en" ng-app="phonecatApp"> > <script src="js/angular.js"></script> > <script src="js/controllers.js"></script> > </head> > <body> > <body ng-controller="PhoneListCtrl"> > <ul> > <li ng-repeat="phone in phones"> > {{phone.name}} > <p>{{phone.snippet}}</p> > </li> > </ul> > </body> > </html> > {code} > 3. Create controllers.js file like this > {code:javascript|title=js/controllers.js|borderStyle=solid} > 'use strict'; > /* Controllers */ > var phonecatApp = angular.module('phonecatApp', []); > phonecatApp.controller('PhoneListCtrl', function ($scope) { > $scope.phones = [ > {'name': 'Nexus SS', > 'snippet': 'Fast just got faster with Nexus S.'}, > {'name': 'Motorola XOOM™ with Wi-Fi', > 'snippet': 'The Next, Next Generation tablet.'}, > {'name': 'MOTOROLA XOOM™', > 'snippet': 'The Next, Next Generation tablet.'} > ]; > }); > {code} > 4. Open index.html with VPE editor > 5. Open controllers.js with JavaScript editor > 6. Invoke code assist for {{phone.| within index.html > ERROR: Lot of errors in error log > {noformat} > Could not load ternDescriptor: [...] > java.lang.NullPointerException > at tern.eclipse.ide.ui.ImageResource.registerImageDescriptor(ImageResource.java:161) > at tern.eclipse.ide.internal.ui.descriptors.TernDescriptor.getImageKey(TernDescriptor.java:38) > at tern.eclipse.ide.internal.ui.descriptors.TernDescriptor.<init>(TernDescriptor.java:21) > at tern.eclipse.ide.internal.ui.descriptors.TernDescriptorManager.addTernDescriptors(TernDescriptorManager.java:116) > at tern.eclipse.ide.internal.ui.descriptors.TernDescriptorManager.loadTernDescriptors(TernDescriptorManager.java:101) > at tern.eclipse.ide.internal.ui.descriptors.TernDescriptorManager.getTernDescriptor(TernDescriptorManager.java:82) > at tern.eclipse.ide.internal.ui.descriptors.TernDescriptorManager.getImage(TernDescriptorManager.java:72) > at tern.eclipse.ide.ui.contentassist.JSTernCompletionProposal.getDefaultImage(JSTernCompletionProposal.java:61) > at tern.eclipse.jface.contentassist.TernCompletionProposal.<init>(TernCompletionProposal.java:56) > at tern.eclipse.ide.ui.contentassist.JSTernCompletionProposal.<init>(JSTernCompletionProposal.java:50) > at tern.eclipse.ide.ui.contentassist.JSTernCompletionCollector.addProposal(JSTernCompletionCollector.java:38) > at tern.server.AbstractTernServer.addProposal(AbstractTernServer.java:103) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:246) > at tern.eclipse.ide.core.IDETernProject.request(IDETernProject.java:511) > at tern.eclipse.ide.core.IDETernProject.request(IDETernProject.java:505) > at tern.eclipse.ide.jsdt.internal.contentassist.TernCompletionProposalComputer.computeCompletionProposals(TernCompletionProposalComputer.java:80) > at org.eclipse.wst.jsdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:298) > at org.eclipse.wst.jsdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:258) > at org.eclipse.wst.jsdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:244) > at org.eclipse.wst.jsdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:213) > at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1861) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499) > at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1687) > at org.eclipse.wst.jsdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:168) > at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:519) > at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:122) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:378) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:324) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1574) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1387) > 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.Widget.sendKeyEvent(Widget.java:1424) > at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:824) > at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3269) > at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:777) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4701) > 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: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: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) > {noformat} -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen 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 ? > 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-17674) Remove 'wrong Node.js install' workaround

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17674?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-17674. ------------------------------- > Remove 'wrong Node.js install' workaround > ------------------------------------------ > > Key: JBIDE-17674 > URL: https://issues.jboss.org/browse/JBIDE-17674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta3 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.2.0.Beta3 > > > Since the 'Node.js install' is fixed in Tern.java we need to remove the workaround regarding the Node.js embedded install set up > - https://github.com/angelozerr/tern.java/pull/80 - An embedded install of Node.js should be used by default -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16096) JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16096?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-16096. ------------------------------- Verified with JBDS 8.0.0.Beta3-v20140706-0939-B172 > JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces > -------------------------------------------------------------------------- > > Key: JBIDE-16096 > URL: https://issues.jboss.org/browse/JBIDE-16096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.2.0.Beta3 > > > 1. Create a JSF 2.2 KickStart project with WildFly 8 target server. > 2. Open inputname.xhtml with JBoss XHTML editor. > 3. FAILURE: inputname uses http://java.sun.com/jsf/* namespaces instead of http://xmlns.jcp.org/jsf/* > 4. Replace all http://java.sun.com/jsf/* by http://xmlns.jcp.org/jsf/*: > {code} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ez="http://xmlns.jcp.org/jsf/composite/demo"> > {code} > 5. FAILURE: Content assist for <h: <f: <ui: <ez: is not working -- 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