[JBoss JIRA] Created: (JBIDE-782) Bring Back Capabilities
by Max Andersen (JIRA)
Bring Back Capabilities
------------------------
Key: JBIDE-782
URL: http://jira.jboss.com/jira/browse/JBIDE-782
Project: JBoss Tools
Issue Type: Bug
Components: JBoss Tools Core
Affects Versions: 2.0.0.Beta3
Reporter: Max Andersen
Assigned To: Marshall Culpepper
Priority: Critical
Fix For: 2.0.0.Beta4
Capabilities, library set, templates are a very usefull feature.
Here is a list of reasons why we disabled it (and things that would be relevant to improve)...lets find out if these are really true or we can fix or live with these:
1) All templates, including libraries seem to be copied to the users workspace on startup. That has several issues:
a) why is a copy necessary ? Can't we just use directly from our plugins ? Users workspace should not contain something that is not workspace local.
b) users can change the templates we have tested and verified - makes supporting them pretty hard.
c) what happens in case of a new version ? do we overwrite whatever changes that are done ? Users won't be happy.
My Suggested solution: Separate the capabilities/libraries etc. up into System preinstalled/plugin provided plugins and User templates. If a user want's to redefine an existing template they make a copy with a different name.
2) Library sets are very close to class libraries...so why not put them/define them as such ?
And then we could add a "Copy class libraries" feature to actually copy any class library to the project - giving users teh best of two worlds and no redundant functionallity.
3) Capabilities are very much like facets just more dynamic...should it be exposed like that instead ?
(issue: what about on projects that are not facet projects ... maybe a "Capability" facet could be made ? ...will it work with all the version number checks they got ?)
4) It seem to be bound to JSF/Struts....why ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months
[JBoss JIRA] Created: (JBIDE-1049) JSP Editor thrown a Null Pointer Exception
by Andreas Hhmann (JIRA)
JSP Editor thrown a Null Pointer Exception
------------------------------------------
Key: JBIDE-1049
URL: http://jira.jboss.com/jira/browse/JBIDE-1049
Project: JBoss Tools
Issue Type: Bug
Environment: vista 64
eclipse 3.3
java 1.6
i use the latest nightly build from http://download.jboss.org/jbosstools/builds/nightly/ ( 200710090220-nightly/ 09-Oct-2007 03:10 )
Reporter: Andreas Hhmann
open a jsp-file ... eclipse shows a NPE ...
java.lang.NullPointerException
at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.rebuildDom(MozillaPreview.java:444)
at org.jboss.tools.vpe.editor.VpeEditorPart.setVisualMode(VpeEditorPart.java:373)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:223)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:385)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:124)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2739)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651)
at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:190)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months
[JBoss JIRA] Created: (JBIDE-1219) java.lang.IllegalArgumentException when open external html/jsp file
by Anton Klimkovich (JIRA)
java.lang.IllegalArgumentException when open external html/jsp file
-------------------------------------------------------------------
Key: JBIDE-1219
URL: http://jira.jboss.com/jira/browse/JBIDE-1219
Project: JBoss Tools
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.Beta4
Reporter: Anton Klimkovich
Attachments: test.html
Open attached html file
java.lang.IllegalArgumentException: Path must include project and resource name: /test.html
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:62)
at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1631)
at org.eclipse.core.internal.resources.Container.getFile(Container.java:123)
at org.eclipse.wst.html.internal.validation.HTMLValidator.validate(HTMLValidator.java:277)
at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:339)
at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:246)
at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:96)
at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:206)
at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:183)
at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:252)
at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor.run(DirtyRegionProcessor.java:633)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months