[JBoss JIRA] Created: (JBIDE-5028) Add JSF Capabilities breaks VPE model
by Yura Zhishko (JIRA)
Add JSF Capabilities breaks VPE model
-------------------------------------
Key: JBIDE-5028
URL: https://jira.jboss.org/jira/browse/JBIDE-5028
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Environment: Eclipse 3.5.1 with all required plug-ins installed.
JBoos Tools installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/
Reporter: Yura Zhishko
Assignee: Yahor Radtsevich
Fix For: 3.1.0.M4
1) Install Eclipse 3.5.1 with all required plug-ins.
2) Help -> Install New Software.
3) Install JBT using link from environment description.
4) Import attached project into workspace.
5) Wait until Updating Maven Dependencies doesn't finish.
6) Open src -> login.xhtml
ASSERT: Page is shown in VPE like on screenshot-1
7) RMB on project
8) JBoss Tools -> Add JSF Capabilities -> Next -> (select any runtime) -> Finish
9) After Building workspace Refresh opened page
ASSERT: The result should be the same as shown on screenshot-1.
ASSERT FAILED: h:head and h:body looks like unknown tags (screenshot-2).
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBIDE-4773) NPE with Open-On from .jar file
by Yura Zhishko (JIRA)
NPE with Open-On from .jar file
-------------------------------
Key: JBIDE-4773
URL: https://jira.jboss.org/jira/browse/JBIDE-4773
Project: JBoss Tools
Issue Type: Bug
Components: common, jsp/jsf/xml source editing, Visual Page Editor core
Affects Versions: 3.1.0.M3
Reporter: Yura Zhishko
Assignee: Alexey Kazakov
1) Import project from https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js...
2) Open paginator.xhtml from mareshkau.jar
3) Try to make Open-on, for example, on h:commandButton tag
RESULT:
java.lang.NullPointerException
at org.jboss.tools.jsf.text.ext.hyperlink.JsfJSPTagNameHyperlinkPartitioner.recognize(JsfJSPTagNameHyperlinkPartitioner.java:78)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:48)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:55)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:55)
at org.jboss.tools.common.text.ext.hyperlink.HyperlinkDetector.getPartitionTypes(HyperlinkDetector.java:65)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.getPartitionType(BaseHyperlinkDetector.java:120)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.getHyperlinks(BaseHyperlinkDetector.java:52)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.detectHyperlinks(BaseHyperlinkDetector.java:132)
at org.eclipse.wst.sse.ui.internal.hyperlink.OpenHyperlinkAction$1.run(OpenHyperlinkAction.java:60)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.wst.sse.ui.internal.hyperlink.OpenHyperlinkAction.run(OpenHyperlinkAction.java:63)
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:470)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:510)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1191)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036)
at org.eclipse.swt.widgets.Widget.wmKeyDown(Widget.java:1669)
at org.eclipse.swt.widgets.Control.WM_KEYDOWN(Control.java:4281)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3977)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4602)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2409)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3471)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBIDE-3950) Add Enum type on configuration page for "EnumDecoder" decoder
by Maurice Zeijen (JIRA)
Add Enum type on configuration page for "EnumDecoder" decoder
-------------------------------------------------------------
Key: JBIDE-3950
URL: https://jira.jboss.org/jira/browse/JBIDE-3950
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.0.0.CR2
Reporter: Maurice Zeijen
The Enum decoder is used to map Strings to a Java enum. The decoder parameters are used to map the value to the Enum value. Here is a configuration example:
<resource-config selector="decoder:test">
<resource>org.milyn.javabean.decoders.EnumDecoder</resource>
<param name="enumType">example.trgmodel.LineOrderPriority</param>
<param name="LOW">NOT_IMPORTANT</param>
<param name="MEDIUM">IMPORTANT</param>
<param name="HIGH">VERY_IMPORTANT</param>
</resource-config>
The enumType parameter defines the enumeration object. The other parameters represent the enum mapping (it isn't pretty, I know ;) ). The name of the parameter is the input value and the value of the parameter is the resulting enum name.
A good editor could make this mapping easier by looking at the enum type and create the mapping for the several enum names. The user only needs to map the input values.
Maybe the graph editor could also be enhanced to make it possible to map an enum to an enum.
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBIDE-5509) Seam Portlet Project - datasource deployment not available
by Dominik Pospisil (JIRA)
Seam Portlet Project - datasource deployment not available
----------------------------------------------------------
Key: JBIDE-5509
URL: https://jira.jboss.org/jira/browse/JBIDE-5509
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal
Affects Versions: 3.1.0.CR1
Reporter: Dominik Pospisil
Project created using "New Dynamic web Project" wizard with "JBoss Seam Portlet Project v2.0" configuration does not expose associted datasource for deployment. As a result deployment of the project fails.
Steps to reproduce:
1) File -> New -> Dynamic Web Project
2) Select "JBoss Seam Portlet Project v2.0" configuration
3) Choose propper runtimes, finish.
4) Right click project, choose Run as -> Run on server
5) Run as resource deployment configuration dialog does not contain project datasource as expected.
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBIDE-5468) Server instance not allways created when creating new runtime
by Dominik Pospisil (JIRA)
Server instance not allways created when creating new runtime
-------------------------------------------------------------
Key: JBIDE-5468
URL: https://jira.jboss.org/jira/browse/JBIDE-5468
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR1
Reporter: Dominik Pospisil
Assignee: Rob Stryker
When creating new server runtime, associated server instance is not allways created as expected (even if create local server checkbox is selected).
Steps to reproduce:
1. Create new runtime (e.g. JBoss EAP 4.3 Runtime) with non-default name (e.g. JBoss EPP 4.3 Runtime)
2. Rename created server to non-default name (JBoss EPP 4.3 Runtime Server)
3. Now we have EPP runtime and EPP server
4. Create new runtime of the same type (JBoss EAP 4.3 Runtime)
5. Corresponding server is not created (JBoss EAP 4.3 Runtime Server)
--
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
16 years, 1 month