November 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7547) NullPointerException in code completion for EL

by Alexey Kazakov (JIRA)

NullPointerException in code completion for EL ---------------------------------------------- Key: JBIDE-7547 URL: https://jira.jboss.org/browse/JBIDE-7547 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 1. Install org.jboss.tools.common.el.core.test plug-in into JBT (there is a test EL resolver factory: ELResolverFactory1 which returns null instead of the list pf proposals). 2. Create any JSF KickStart project. 3. Try to Ctrl+Space within any EL. 4. See Eclipse log: java.lang.NullPointerException at java.util.ArrayList.addAll(ArrayList.java:472) at org.jboss.tools.jst.web.kb.PageProcessor.getProposals(PageProcessor.java:164) at org.jboss.tools.jst.web.kb.PageProcessor.getProposals(PageProcessor.java:61) at org.jboss.tools.jst.jsp.contentassist.computers.XmlELCompletionProposalComputer.addAttributeValueELProposals(XmlELCompletionProposalComputer.java:181) at org.jboss.tools.jst.jsp.contentassist.computers.XmlELCompletionProposalComputer.addAttributeValueProposals(XmlELCompletionProposalComputer.java:139) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeAttributeValueProposals(AbstractXMLCompletionProposalComputer.java:601) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:407) at org.jboss.tools.jst.jsp.contentassist.computers.AbstractXmlCompletionProposalComputer.computeCompletionProposals(AbstractXmlCompletionProposalComputer.java:655) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:174) at org.jboss.tools.jst.jsp.contentassist.computers.AbstractXmlCompletionProposalComputer.computeCompletionProposals(AbstractXmlCompletionProposalComputer.java:81) at org.jboss.tools.jst.jsp.contentassist.computers.FaceletsELCompletionProposalComputer.computeCompletionProposals(FaceletsELCompletionProposalComputer.java:85) at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284) at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:294) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:441) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:245) at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:126) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1834) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482) at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1660) at org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:441) at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$JSPStructuredTextViewer.doOperation(JSPTextEditor.java:679) at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:131) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction.java:129) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1525) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1257) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1294) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:730) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2839) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4794) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4372) 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:8163) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1239) 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:2224) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3169) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7591) Remove JSF Core/HTML TLDs v.1.2 from JSF 2 project templates.

by Alexey Kazakov (JIRA)

Remove JSF Core/HTML TLDs v.1.2 from JSF 2 project templates. ------------------------------------------------------------- Key: JBIDE-7591 URL: https://jira.jboss.org/browse/JBIDE-7591 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 1. Create JSF 2 project via New JSF Project wizard. 2. There is Web-inf/lib/jsf-tlds.jar which contains JSF Core/HTML TLDs v.1.2. We don't need to have them there. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-612) EGT - BRMS-eclipse tool - properties shows odd syntax for timestamp

by Len DiMaggio (JIRA)

EGT - BRMS-eclipse tool - properties shows odd syntax for timestamp ------------------------------------------------------------------- Key: JBDS-612 URL: https://jira.jboss.org/jira/browse/JBDS-612 Project: Developer Studio Issue Type: Bug Components: visualeditor Affects Versions: 2.0.0.cr1 Environment: Version: 2.0.0.CR1 Build id: R200812221144 Build date: 12/22/2008 11:54 Reporter: Len DiMaggio Priority: Minor See the attached screen-shot - chars "TZ" begin and end the time displayed like this: 2009-02-03T01:42:14Z -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6093) Eclipse Guvnor Tooling causes validation errors on certain file types

by Jeff DeLong (JIRA)

Eclipse Guvnor Tooling causes validation errors on certain file types ---------------------------------------------------------------------- Key: JBIDE-6093 URL: https://jira.jboss.org/jira/browse/JBIDE-6093 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: drools Affects Versions: 3.1.0.CR2 Environment: JBoss Tools Nightly Build - Jboss Drools Guvnor 5.1.0.v20100226213N-H20-31764 Reporter: Jeff DeLong Eclipse Guvnor Tooling creates a new file with the name .filename.ext when a file is added to Guvnor. For xml files (.xml, .xsd, .html, .bpel, etc,) and java files, this causes the validators to report errors. E.g., "Content is not allowed in the prolog" and "Syntax errors on tokens, delete these tokens. This is because these files have the xml or java extension, hence the validator attempts to validate them. I have looking at the Preferences -> Validation, but cannot see a clever way to create a rule to exclude all files with a . at the front of the filename. Also, Eclipse Guvnor Tooling is not able to add files to the new for Guvnor 5.1 GlobalArea. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

6
23
0 / 0

[JBoss JIRA] Created: (JBDS-1388) Creating Modeshape server in JBDS 4.0 beta1 - intermittent problem where error raised regarding existing user "admin"

by Len DiMaggio (JIRA)

Creating Modeshape server in JBDS 4.0 beta1 - intermittent problem where error raised regarding existing user "admin" --------------------------------------------------------------------------------------------------------------------- Key: JBDS-1388 URL: https://jira.jboss.org/browse/JBDS-1388 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Modeshape Affects Versions: 4.0.0.Beta1 Reporter: Len DiMaggio JBDS issue for JIRA: SOA-2508 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7270) New teiid connection instances are created badly in 3.2.0.beta1

by Jiri Peterka (JIRA)

New teiid connection instances are created badly in 3.2.0.beta1 --------------------------------------------------------------- Key: JBIDE-7270 URL: https://jira.jboss.org/browse/JBIDE-7270 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.Beta1 Environment: JBDS 4.0.0.beta1 #30, Linux 64 Reporter: Jiri Peterka Priority: Blocker Fix For: 3.2.0.Beta1 Steps: - Create new instance in Teidd view. ERROR: It's unable to connect teiid server with newly created connection Java.io.StreamCorruptedException: invalid data length: -2140864253 at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:116) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:282) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:340) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:272) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:192) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
11
0 / 0

[JBoss JIRA] Created: (JBDS-1383) Unable to publish Teiid Example Project to modeshape repository (IllegalArgumentException)

by Pavol Srna (JIRA)

Unable to publish Teiid Example Project to modeshape repository (IllegalArgumentException) ------------------------------------------------------------------------------------------ Key: JBDS-1383 URL: https://jira.jboss.org/browse/JBDS-1383 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Modeshape Affects Versions: 4.0.0.Beta2 Environment: linux 32bit, jbdevstudio-linux-gtk-4.0.0.v201010260634N-H123-Beta2, soa-5.1.0.ER2 with modeshape 2.3 Reporter: Pavol Srna I used soa-5.1.0.ER2 with modeshape 2.3, JBDS 4.0.0.Beta2 and tried to publish Teiid Project Example to default in-memory repository. Message: Publishing file "/home/psrna/data/testing/workspaces/jbdev23/PartsProject/PartsSourceA.xmi" to path "/PartsProject" in workspace "default" failed. Exception Stack Trace: java.lang.IllegalArgumentException: The stream argument may not be null at org.modeshape.common.util.CheckArg.isNotNull(CheckArg.java:387) at org.modeshape.common.util.MimeTypeUtil.load(MimeTypeUtil.java:153) at org.modeshape.web.jcr.rest.client.Utils.getMimeType(Utils.java:72) at org.modeshape.web.jcr.rest.client.json.FileNode.<init>(FileNode.java:112) at org.modeshape.web.jcr.rest.client.json.JsonRestClient.pathExists(JsonRestClient.java:372) at org.modeshape.web.jcr.rest.client.json.JsonRestClient.publish(JsonRestClient.java:392) at org.jboss.tools.modeshape.rest.ServerManager.publish(ServerManager.java:504) at org.jboss.tools.modeshape.rest.jobs.PublishJob.run(PublishJob.java:213) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1385) Configuring Modeshape repository in JBDS 4.0 beta1 results in errors - trying to execute: getRepositories: server=ModeShape Server - URL: http://localhost:8080/modeshape-rest/repository

by Len DiMaggio (JIRA)

Configuring Modeshape repository in JBDS 4.0 beta1 results in errors - trying to execute: getRepositories: server=ModeShape Server - URL: http://localhost:8080/modeshape-rest/repository ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBDS-1385 URL: https://jira.jboss.org/browse/JBDS-1385 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Modeshape Affects Versions: 4.0.0.Beta1 Reporter: Len DiMaggio JBDS issue for JIRA: SOA-2504 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6655) ModeShape Servers view Edit Server dialog description misleading

by Brian Fitzpatrick (JIRA)

ModeShape Servers view Edit Server dialog description misleading ---------------------------------------------------------------- Key: JBIDE-6655 URL: https://jira.jboss.org/browse/JBIDE-6655 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: modeshape Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Dan Florian Fix For: 3.2.x On the "Edit Server" dialog, perhaps change the description at the top to be "Define server details for this ModeShape server instance." The existing text is a bit misleading - "Define the server information where the ModeShape repositories are located" hints that you're defining the location for more than one server on this dialog, which is probably an incorrect assumption. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6979) Published Locations shell for Modeshape is always shown on 1st monitor

by Jiri Peterka (JIRA)

Published Locations shell for Modeshape is always shown on 1st monitor ---------------------------------------------------------------------- Key: JBIDE-6979 URL: https://jira.jboss.org/browse/JBIDE-6979 Project: Tools (JBoss Tools) Issue Type: Bug Components: modeshape Affects Versions: 3.2.0.M2 Environment: JBT 3.2.0.m2 H309, Linux 64, Fedora 13, GKT Reporter: Jiri Peterka Have Eclipse opened on 2nd monitor 1. Create Project 2. Create file 3. Add file to modehape 4. Show published locations of the file Published Locations shell for Modeshape is always shown on 1st monitor. All other separate shells are opened correctly on the monitor where Eclipse is opened. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
4
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 November 2010