[JBoss JIRA] Created: (JBIDE-1461) Tiles editor - ERROR - Unindentified parser error.
by Alex Titov (JIRA)
Tiles editor - ERROR - Unindentified parser error.
--------------------------------------------------
Key: JBIDE-1461
URL: http://jira.jboss.com/jira/browse/JBIDE-1461
Project: JBoss Tools
Issue Type: Bug
Components: struts/shale
Affects Versions: 2.0.0.CR1
Environment: Linux, Eclipse 3.3.1.1
Reporter: Alex Titov
I cannot open any tiles-defs.xml. Here is an example. This file works fine in struts...
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE tiles-definitions PUBLIC
"-//Apache Software Foundation//DTD Tiles Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd">
<!--
This is a blank Tiles definition file with a commented example.
-->
<tiles-definitions>
<!-- sample tiles definitions
<definition name=".mainLayout" path="/common/layouts/classicLayout.jsp">
<put name="title" value="Sample Page Title" />
<put name="header" value="/common/header.jsp" />
<put name="menu" value=".mainMenu" />
<put name="footer" value="/common/footer.jsp" />
<put name="body" value=".portal.body" />
</definition>
<definition name=".mainMenu" path="/common/layouts/vboxLayout.jsp" >
<putList name="list" >
<add value=".menu.links" />
<add value=".menu.taglib.references" />
<add value=".menu.printer.friendly" />
<add value=".menu.old.documents" />
</putList>
</definition>
<definition name="aPage" extends=".mainLayout">
<put name="title" value="Another Title" />
<put name="body" value=".aPage.body" />
</definition>
end samples -->
<definition name=".markSystems.list" path="/WEB-INF/jsp/template.jsp">
<put name="content" value="/marks/systems/list.jsp"></put>
</definition>
<definition name=".markSystems.add" path="/WEB-INF/jsp/template.jsp">
<put name="content" value="/marks/systems/add_edit.jsp"></put>
</definition>
<definition name=".marks.list" path="/WEB-INF/jsp/template.jsp">
<put name="content" value="/marks/list.jsp"></put>
</definition>
<definition name=".marks.add" path="/WEB-INF/jsp/template.jsp">
<put name="content" value="/marks/add_edit.jsp"></put>
</definition>
</tiles-definitions>
--
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
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-1462) Cannot open struts-config.xml
by Alex Titov (JIRA)
Cannot open struts-config.xml
-----------------------------
Key: JBIDE-1462
URL: http://jira.jboss.com/jira/browse/JBIDE-1462
Project: JBoss Tools
Issue Type: Bug
Components: struts/shale
Affects Versions: 2.0.0.CR1
Environment: Linux, Eclipse 3.3.1.1
Reporter: Alex Titov
When I try to open struts-config.xml with JBoss XML editor the fillowing error appears in .log file:
!ENTRY org.eclipse.ui 4 0 2007-12-07 01:05:43.142
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NoSuchFieldError: ATTR_REGISTER_IN_TOMCAT
at org.jboss.tools.struts.StrutsPreference.<clinit>(StrutsPreference.java:28)
at org.jboss.tools.struts.ui.editor.StrutsConfigEditor.doCreatePages(StrutsConfigEditor.java:57)
at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:234)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:178)
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$3.handleEvent(OpenWithMenu.java:226)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
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(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: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
15 years, 5 months
[JBoss JIRA] Created: (RHDS-120) java.lang.NullPointerException when try to save empty value in web.xml Editor.
by Anton Klimkovich (JIRA)
java.lang.NullPointerException when try to save empty value in web.xml Editor.
------------------------------------------------------------------------------
Key: RHDS-120
URL: http://jira.jboss.com/jira/browse/RHDS-120
Project: Red Hat Developer Studio
Issue Type: Bug
Affects Versions: 1.0.0.beta1
Reporter: Anton Klimkovich
Open web.xml on tree tab
Right ckick on Error Pages for example
Set Error-Code and location
On Tree tab in web.xml Editor clear field with Error-Code
Try to save file.
java.lang.NullPointerException
at org.eclipse.jst.j2ee.model.internal.validation.WarValidator.validateErrorPages(WarValidator.java:693)
at org.eclipse.jst.j2ee.model.internal.validation.WarValidator.validate(WarValidator.java:251)
at org.eclipse.jst.j2ee.internal.web.validation.UIWarValidator.validate(UIWarValidator.java:95)
at org.eclipse.jst.j2ee.model.internal.validation.WarValidator.validateInJob(WarValidator.java:329)
at org.eclipse.jst.j2ee.internal.web.validation.UIWarValidator.validateInJob(UIWarValidator.java:111)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
org.eclipse.wst.validation.internal.core.ValidationException: CHKJ3000E: WAR Validation Failed: java.lang.NullPointerException
at org.eclipse.jst.j2ee.model.internal.validation.WarValidator.validateInJob(WarValidator.java:343)
at org.eclipse.jst.j2ee.internal.web.validation.UIWarValidator.validateInJob(UIWarValidator.java:111)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75)
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
15 years, 8 months
[JBoss JIRA] Created: (JBIDE-1531) Editors not shown at first when an xhtml file is opened in the jboss editor (but does after toggling another tab)
by Ernout vd Waard (JIRA)
Editors not shown at first when an xhtml file is opened in the jboss editor (but does after toggling another tab)
-----------------------------------------------------------------------------------------------------------------
Key: JBIDE-1531
URL: http://jira.jboss.com/jira/browse/JBIDE-1531
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.GA
Environment: We use the following versions:
- Eclipse 3.3.1.1
- JBoss Tools 2.0.0.GA
- Java JDK6 64 bit
Reporter: Ernout vd Waard
When we open a xhtml file in the jboss html editor, the first time there isn't anything show, just a grey background.
The tabs at the bottom of the pane are shown, and if you click another tab the editor is shown and you can use all different edit modes.
I can close the editor and open a new one and it works again after toggling the tab.
We are running Eclipse on Windows Vista 64, and maybe this has something to do with it. When we copied the configuration to a Vista 32 bit machine, the problem went away.
It would be great if someone could point us in the right direction of where to continue our search!
Another hint may be that the settings pane for the visual editor also is blank after we used the editor once.
What we've tried so far (but did not succeed):
- update to nightly build of jboss tools
- searched the jira
- searched the forums
- edit the code ourselves
- tried running this eclipse configuration with JDK 5 (both 64 as 32 bit)
- tried setting another default editor
--
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
16 years