[JBoss JIRA] Created: (JBIDE-3508) Validation of orphaned namespaced end tags, i.e. </...>, does not happen for xhtml in VPE
by Karl Philipp (JIRA)
Validation of orphaned namespaced end tags, i.e. </...>, does not happen for xhtml in VPE
-----------------------------------------------------------------------------------------
Key: JBIDE-3508
URL: https://jira.jboss.org/jira/browse/JBIDE-3508
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing, Visual Page Editor core
Affects Versions: 3.0.0.CR2
Environment: Windows XP SP3, Eclipse 3.4 "GANYMEDE", Web Tools 3.0.3, RichFaces-VPE-win32-3.0.0.CR2-N200901081811, RichFaces 3.2.2.SR1, JSF 1.2 RI, Facelets 1.1.14
Reporter: Karl Philipp
Orphaned namedspaced end tags such as </rich:panel> are not detected by the validation algorithm in contrast to orphaned namedspaced start tags:
<h:form id="searchForm">
<rich:panel>
<f:facet name="header">
<h:outputText value="ServiceProvider" />
</f:facet>
<a4j:commandButton value="Search" action="#{sps.search}" />
</rich:panel>
</h:form>
</rich:panel>
The last end tag </rich:panel> above is orphaned but not detected as invalid by VPE.
--
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: (JBDS-1083) Hibernate guide update
by Svetlana mukhina (JIRA)
Hibernate guide update
-----------------------
Key: JBDS-1083
URL: https://jira.jboss.org/jira/browse/JBDS-1083
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: Doc - Hibernate
Affects Versions: 3.0.0.M4-doc
Reporter: Svetlana mukhina
Assignee: Svetlana mukhina
Fix For: 3.0.0.CR2-doc
In documentation is written to install Hibernate Tools plugins wtp is necessary, in real life the user needs these steps to install it (if he download it separately - not from update site): http://loracular.blogspot.com/2009/09/steps-to-install-hibernate-tools-fo...
4.2 - refresh figures 4.1 & 4.2; it is necessary to mention that it is possible do not select any class/package on 4.1 - as result blank hbm.xml will be generated, plus checkbox on right to control dependences depth, i.e. there is class A in the list, if class A has reference on class B, then hbm.xml will be generated for class B also. Now for hbm.xml generation there is a preview results page, as Generate Hibernate/JPA annotations has - is necessary to add description;
The same for Generate Hibernate/JPA annotations - is necessary to describe possibility to control depth.
Figure 4.5 - is necessary to refresh, cause there is possibility to specify dialect + describe this in documentation;
Figure 4.10 - refresh picture cause contextual menu little bit changed;
"4.4.2. - right click on the configuration in Hibernate Configurations View->Edit Configuration or double click on console configuration" - is necessary to mention about "double click"
Figure 4.13 - is necessary to mention that it is possible to specify absolute directory path as example "d:\temp" - in the Table 4.6;
Figure 4.33 - refresh - now it is possible "pin" HQL editor & Criteria editor for one tab in Hibernate Query Results view; it also possible to rename tab (by default the name is a whole query - too long for some cases) - select tab -> Properties view -> Name;
Figure 4.34 - refresh - contextual menu updated;
Figure 4.36 - refresh - contextual menu updated;
Figure 4.39 & Figure 4.40 - refresh - Outline view has a little change - it is possible to switch on/off alphabetical sorting;
Figure 4.41 - refresh - contextual menu updated, plus update description;
Figure 4.43 & Figure 4.44 - refresh - cause now diagram headers are shorter;
For Hibernate Mapping Diagram there is no description of toolbar and it's functionality; Refresh button refresh diagram - if console configuration was changed;
Zoom combobox - is obligatory to mention what selected zoom will be used for diagram printing, if the user wants to put diagram on one print page he should select - "Page" in zoom combobox;
Auto layout & Show|Hide connections & Expand|Collapse & Show|Hide shape(s) - is necessary to add description;
Figure 4.45 - refresh - cause new context menu;
Is necessary to describe: "Close Configuration" - this close hibernate console configuration, disconnect from DB, free other resources (for example unlock jar libs for windows);
Figure 4.46 - refresh - cause new context menu;
Figure 4.49 - refresh - cause white background icon, the same for Figure 4.50 & Figure 4.51;
"4.11. Hibernate:add JPA annotations view" - is not right - should be "4.11. Hibernate:add JPA annotations refactoring"
Figure 4.52 - refresh; add new screenshort for back page - now it is possible back and update selected classes and packages - the same as generate hbm.xml has;
"Starting Hibernate:add JPA annotations view" - this is not a view - this is dialog -> Figure 4.53 - refresh it;
It is not mentioned in documentation what "Error Log View" - is very important with Hibernate Tools plugins - it should be recommended for users to switch it on in Hibernate perspective and use "Error Log View" if there are some trubles to configure Hibernate console configuration;
prepare example projects which is used a as base project for documentation for user to download
--
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-4667) Import Tags from TLD file works wrong after second calling
by Yura Zhishko (JIRA)
Import Tags from TLD file works wrong after second calling
----------------------------------------------------------
Key: JBIDE-4667
URL: https://jira.jboss.org/jira/browse/JBIDE-4667
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.M3
Reporter: Yura Zhishko
Assignee: Alexey Kazakov
Priority: Minor
1) Create any project
2) Open JBoss Palette
3) Press Import button
4) In Import tags from TLD File dialog press Browse... button
5) Choose any tag lib, for example, x-1_0-rt.tld
6) Press OK button
ASSERT: All fields in Import tags from TLD File dialog: TLD File*, Name*, Default Prefix, Library URI are filled
7) Press Cancel button
8) Repeat steps 3-6
ASSERT: Result is the same: All fields in Import tags from TLD File dialog: TLD File*, Name*, Default Prefix, Library URI are filled.
ASSERT FAILED: Only TLD File* path is filled.
--
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-5635) OpenOn doesn't work for seam files.
by Denis Maliarevich (JIRA)
OpenOn doesn't work for seam files.
-----------------------------------
Key: JBIDE-5635
URL: https://jira.jboss.org/jira/browse/JBIDE-5635
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.CR1
Reporter: Denis Maliarevich
Assignee: Denis Maliarevich
Fix For: 3.1.0.CR2
OpenOn doesn't work when user clicks on <a href="cheat.seam">cheat.seam</a> link from Seam project.
Steps to reproduce:
1. Create Seam Project Example (i.e. Numberguess)
2. Add the <a> link to any page with the link to another one (i.e. <a href="cheat.seam">cheat.seam</a>)
3. Try Ctrl+MouseClick - nothing happens. But while runing on server the selected page will be opened.
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1410) el resolution in visual editor
by Menashe (JIRA)
el resolution in visual editor
------------------------------
Key: JBIDE-1410
URL: http://jira.jboss.com/jira/browse/JBIDE-1410
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 2.0.0.CR1
Environment: seam2.0
eclipse 3.3.1.1
Reporter: Menashe
When el is used (as image/css source) the visual editor doesn't resolve it.
Here is what I mean (this is part of my template therefor it must be full path, since if it left as relative path it gets resolved based on the path of the page that is using the template and not of the actual template location.)
<img src="#{facesContext.externalContext.requestContextPath}/images/header.gif"/>
Visual editor should be able to figure out that #{facesContext.externalContext.requestContextPath} should be just dropped.
Since
<img src="/images/header.gif"/>
works fine in visual editor but not in the seam2 (unless contextpath is '/')
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-4789) NPE if we try to add Global EL variable for all projects
by Yura Zhishko (JIRA)
NPE if we try to add Global EL variable for all projects
--------------------------------------------------------
Key: JBIDE-4789
URL: https://jira.jboss.org/jira/browse/JBIDE-4789
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.M3
Reporter: Yura Zhishko
Assignee: Denis Maliarevich
1) Go to Preferences->JBoss Tools->Web->EL Variables
2) Press Add button.
RESULT:
java.lang.NullPointerException
at org.jboss.tools.common.resref.ui.BaseAddReferenceSupport.run(BaseAddReferenceSupport.java:30)
at org.jboss.tools.common.resref.ui.BaseAddReferenceSupport.add(BaseAddReferenceSupport.java:18)
at org.jboss.tools.common.el.ui.GlobalElVariablesComposite.add(GlobalElVariablesComposite.java:74)
at org.jboss.tools.common.resref.ui.AbstractResourceReferencesComposite$BarListener.action(AbstractResourceReferencesComposite.java:136)
at org.jboss.tools.common.model.ui.action.CommandBar$ButtonDescriptor.widgetSelected(CommandBar.java:290)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
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(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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, 2 months