[JBoss JIRA] (JBIDE-2615) [JSF12] CA for #{application}
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2615?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-2615.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> [JSF12] CA for #{application}
> -----------------------------
>
> Key: JBIDE-2615
> URL: https://issues.jboss.org/browse/JBIDE-2615
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsf
> Reporter: Adrian Mitev
> Assignee: Alexey Kazakov
> Labels: content_assist, jsf, validation
> Fix For: LATER
>
>
> #{application} was introduced in JSF 1.2 and corresponds to the implicit object named application from JSP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-4543) Create categories for properties
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4543?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-4543.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Create categories for properties
> --------------------------------
>
> Key: JBIDE-4543
> URL: https://issues.jboss.org/browse/JBIDE-4543
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Krasimir Goutcev
> Assignee: Viacheslav Kabanovich
> Fix For: LATER
>
> Attachments: prop.png, properties1.png, properties2.png
>
>
> Open your page file and place the cursor in a place where you'd like to add a tag and then click that tag in the palette. In the Insert Tag window, that appears, you can set the value of GENERAL and ADVANCED attributes of the tag that you chose.(see pic1)
> Why to not have same categories when select inserted tag on page( see pic2) in properties view?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-5722) Implement content assist in JBoss Properties editors for seam.properties
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-5722?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-5722.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Implement content assist in JBoss Properties editors for seam.properties
> ------------------------------------------------------------------------
>
> Key: JBIDE-5722
> URL: https://issues.jboss.org/browse/JBIDE-5722
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: LATER
>
>
> Values of properties of Seam components can be set in seam.properties file.
> So, content assist can be implemented for names of entries in it.
> In some cases, e.g. value is boolean, or schema restrict it to a list of values, content assist can be implemented for values.
> org.jboss.seam.international.timeZoneSelector.cookieEnabled - is boolean.
> org.jboss.seam.core.manager.defaultFlushMode - restricted to {MANUAL,AUTO,COMMIT} in core-2.2.xsd
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-2061) Ftl editor does not support opening local files external to the workspace.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2061?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-2061.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Ftl editor does not support opening local files external to the workspace.
> --------------------------------------------------------------------------
>
> Key: JBIDE-2061
> URL: https://issues.jboss.org/browse/JBIDE-2061
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Environment: RHDS version 1.0, with Seam 2.0.1GA, on Windows XP, JBossAS 4.2.2.GA
> Reporter: Bruce Link
> Assignee: Denis Golovin
> Fix For: LATER
>
>
> Used JBDS to look at the view.xhtml.ftl file under jbdevstudio\jboss-eap\seam\seam-gen\view. The FreeMarker site indicates that JBDS has a plugin for eclipse that can do this, so I figured I would see if it worked using file>open, as I could not see a FreeMarker view.
> JBDS could not open the file and gave an error message, referencing a log entry.
> The edit window shows a blue horizontal line and the word ERROR. The tab at the bottom reads "Source" The tab at the top has an icon showing a page with the overlay <FM> and reads "view.xhtml.ftl
> Same thing with other ftl files I tried to open, in the same directory or in the Seam 2.0.1GA\seam-gen\view directory.
> The log entry follows:
> !ENTRY org.eclipse.ui.workbench 4 2 2008-04-13 17:17:44.690
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.freemarker.model.ItemSet.<init>(ItemSet.java:56)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.getItemSet(Editor.java:271)
> at org.jboss.ide.eclipse.freemarker.outline.OutlineContentProvider.getElements(OutlineContentProvid
> er.java:63)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:937)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:693)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1298)
> at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:378)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getFilteredChildren(AbstractTreeViewer.java:615)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:581)
> at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:778)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:755)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:627)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1463
> )
> at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:816)
> at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1446)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1368)
> at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:390)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1330)
> at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1435)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:251)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1606)
> at org.jboss.ide.eclipse.freemarker.outline.OutlinePage.createControl(OutlinePage.java:85)
> at org.eclipse.ui.views.contentoutline.ContentOutline.doCreatePage(ContentOutline.java:135)
> at org.eclipse.ui.part.PageBookView.createPage(PageBookView.java:399)
> at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:741)
> at org.eclipse.ui.internal.PartListenerList$1.run(PartListenerList.java:72)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at org.eclipse.core.runtime.Platform.run(Platform.java:857)
> at org.eclipse.ui.internal.PartListenerList.fireEvent(PartListenerList.java:57)
> at org.eclipse.ui.internal.PartListenerList.firePartActivated(PartListenerList.java:70)
> at org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:73)
> at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:171)
> at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:5
> 6)
> at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:126)
> at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3402)
> at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:611)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2748)
> 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.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2557)
> at org.eclipse.ui.ide.IDE.openEditorOnFileStore(IDE.java:1090)
> at org.eclipse.ui.internal.ide.actions.OpenLocalFileAction.run(OpenLocalFileAction.java:105)
> at org.eclipse.ui.internal.ide.actions.OpenLocalFileAction.run(OpenLocalFileAction.java:75)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
> at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.jav
> a:546)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
> 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.j
> ava: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:585)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-8559) Generated list.xhtml file uses undefined class "results"
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8559?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-8559.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Generated list.xhtml file uses undefined class "results"
> --------------------------------------------------------
>
> Key: JBIDE-8559
> URL: https://issues.jboss.org/browse/JBIDE-8559
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2, upstream
> Environment: JBDS4
> Reporter: Peter Larsen
> Assignee: Alexey Kazakov
> Priority: Minor
> Fix For: LATER
>
>
> The generated xhtml file for an entity, ie. userList.xhtml, contains a <div class="results"> which refers to a CSS definition ".results" that is not defined in the default stylesheet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-9692) detect RESTEasy libraries when they're added to project classpath
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9692?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-9692.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> detect RESTEasy libraries when they're added to project classpath
> -----------------------------------------------------------------
>
> Key: JBIDE-9692
> URL: https://issues.jboss.org/browse/JBIDE-9692
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 3.3.0.M3
> Reporter: Rastislav Wagner
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When creating Sample RESTFul Web Service project, RESTEasy libraries should be detected when they are in the runtime of associated project. They are detected only in the lib folder of AS so far.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-3419) CSS Refactoring: Make it easy to switch between internal an external CSS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3419?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-3419.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> CSS Refactoring: Make it easy to switch between internal an external CSS
> ------------------------------------------------------------------------
>
> Key: JBIDE-3419
> URL: https://issues.jboss.org/browse/JBIDE-3419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 3.0.0.cr1
> Reporter: Francisco Jose Peredo Noguez
> Fix For: LATER
>
>
> Some times it is just easier to use the "style" attribute of an html tag to alter/change the way it is presented to the user, but later, it is better to consolidate this information in an external .css file. I would be really nice if I could right click the "style" attribute of an html tag, select "Refactor->Extract Style to CSS file" in the contextual menu and have the style automatically copied to the .css file I choose (and of course have the <link href="..." rel="stylesheet" type="text/css" /> automatically created for me.
> I would also be great if it could be done not only on an individual tag, but in all the tags in a file, or even in all the files in a project.
> And of course there are times when is more convenient to have the style embedded in the html file and drop the <link href="..." rel="stylesheet" type="text/css" /> , for those cases it would be really nice to have a "Inline css" option to do the opposite.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-2318) Case Sensitive Code Completion in JSF page editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2318?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-2318.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Case Sensitive Code Completion in JSF page editor
> -------------------------------------------------
>
> Key: JBIDE-2318
> URL: https://issues.jboss.org/browse/JBIDE-2318
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 2.1.1
> Environment: JBDS 1.1.0 CR 1, JBoss Tools 2.1.1 GA (tested Both), Windows XP, Eclipse-Europa-Winter, brand new project
> Reporter: Andy Gibson
> Assignee: Victor Rubezhny
> Fix For: LATER
>
> Attachments: bug3.swf, bug3.swf.html
>
>
> There are some issues with case sensitivity in the code completion for Seam items. I'll attach a movie demonstrating this, but essentially, if you try code completion with :
> <h:outputText value="#{paramv"/> (lower case 'v' at the end)
> Then the value #{paramValues} will appear in the code suggestions.
> However, if you have :
> <h:outputText value="#{conversatione"/> (lower case 'e' at the end)
> Then #{conversationEntries} does NOT appear, but it will appear if I make the trailing 'e' an upper case 'E'.
> The conversationEntries and paramValues are available in a newly created project if you want to try and re-produce the problem.
> If I create a bean called "myBean" and type :
> <h:outputText value="#{myb"/>
> Then myBean does not appear but if you type ;
> <h:outputText value="#{myB"/>
> Then myBean does appear.
> The problem also extends into methods / attributes on the bean, so #{conversation.changeflush does not return anything.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months