[JBoss JIRA] (JBIDE-9667) NPE when deleting project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9667?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-9667.
----------------------------------------
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!
> NPE when deleting project
> -------------------------
>
> Key: JBIDE-9667
> URL: https://issues.jboss.org/browse/JBIDE-9667
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 3.3.0.M3
> Reporter: Libor Zoubek
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: LATER
>
>
> Sometimes I get this when running swtbot tests, There is our class in stacktrace.
> {noformat}
> [java] !ENTRY org.eclipse.ui.navigator 4 0 2011-09-06 14:42:27.944
> [java] !MESSAGE An exception occurred invoking extension: org.eclipse.jst.jee.ui.web for object P/BottomUpWS-web
> [java] !STACK 0
> [java] java.lang.NullPointerException
> [java] at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.createModelResource(JEE5ModelProvider.java:193)
> [java] at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelResource(JEE5ModelProvider.java:174)
> [java] at org.eclipse.jst.jee.model.internal.Web25ModelProvider.getModelObject(Web25ModelProvider.java:44)
> [java] at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelObject(JEE5ModelProvider.java:217)
> [java] at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getLastModificationTimeOfDDFile(AbstractMergedModelProvider.java:235)
> [java] at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.hasToReloadModel(AbstractMergedModelProvider.java:229)
> [java] at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getMergedModel(AbstractMergedModelProvider.java:218)
> [java] at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getModelObject(AbstractMergedModelProvider.java:139)
> [java] at org.eclipse.jst.jee.ui.internal.navigator.Web25ContentProvider.getNewContentProviderInstance(Web25ContentProvider.java:69)
> [java] at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.getCachedContentProvider(JEE5ContentProvider.java:92)
> [java] at org.eclipse.jst.jee.ui.internal.navigator.Web25ContentProvider.getChildren(Web25ContentProvider.java:35)
> [java] at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96)
> [java] at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:275)
> [java] at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:94)
> [java] at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152)
> [java] at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> [java] at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139)
> [java] at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:125)
> [java] at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1352)
> [java] at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391)
> [java] at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917)
> [java] at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:605)
> [java] at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2620)
> [java] at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1908)
> [java] at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
> [java] at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1915)
> [java] at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721)
> [java] at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1883)
> [java] at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1840)
> [java] at org.eclipse.ui.navigator.CommonViewer.internalRefresh(CommonViewer.java:561)
> [java] at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1535)
> [java] at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
> [java] at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403)
> [java] at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
> [java] at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1533)
> [java] at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:548)
> [java] at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:353)
> [java] at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:510)
> [java] at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1465)
> [java] at org.jboss.tools.seam.ui.views.AbstractSeamContentProvider$3.run(AbstractSeamContentProvider.java:224)
> [java] at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> [java] at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> [java] at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
> [java] at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
> [java] at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
> [java] at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
> [java] at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:331)
> [java] at org.eclipse.ltk.ui.refactoring.RefactoringWizard.internalPerformFinish(RefactoringWizard.java:605)
> [java] at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.performFinish(UserInputWizardPage.java:153)
> [java] at org.eclipse.ltk.ui.refactoring.resource.DeleteResourcesWizard$DeleteResourcesRefactoringConfigurationPage.performFinish(DeleteResourcesWizard.java:151)
> [java] at org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish(RefactoringWizard.java:678)
> [java] at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.okPressed(RefactoringWizardDialog2.java:455)
> [java] at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
> [java] at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> [java] at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
> [java] at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> [java] at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
> [java] at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
> [java] at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267)
> [java] at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1061)
> [java] at org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot$2.run(AbstractSWTBot.java:159)
> [java] at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable$5.doRun(UIThreadRunnable.java:221)
> [java] at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable$1.run(UIThreadRunnable.java:89)
> [java] at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> [java] at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> [java] at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
> [java] at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
> [java] at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> [java] at org.eclipse.jface.window.Window.open(Window.java:801)
> [java] at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:181)
> [java] at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> [java] at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:193)
> [java] at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:116)
> [java] at org.eclipse.ltk.internal.ui.refactoring.actions.DeleteResourcesHandler.execute(DeleteResourcesHandler.java:40)
> [java] at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
> [java] at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
> [java] at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> [java] at org.eclipse.ui.internal.handlers.HandlerService.executeCommandInContext(HandlerService.java:270)
> [java] at org.eclipse.ui.internal.ide.actions.LTKLauncher.runCommand(LTKLauncher.java:95)
> [java] at org.eclipse.ui.internal.ide.actions.LTKLauncher.openDeleteWizard(LTKLauncher.java:47)
> [java] at org.eclipse.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:474)
> [java] at org.eclipse.jdt.internal.ui.refactoring.reorg.DeleteAction.run(DeleteAction.java:165)
> [java] at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275)
> [java] at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251)
> [java] at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> [java] at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> [java] at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> [java] at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> [java] at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> [java] at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
> [java] at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
> [java] at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267)
> [java] at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1061)
> [java] at org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot$2.run(AbstractSWTBot.java:159)
> [java] at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable$5.doRun(UIThreadRunnable.java:221)
> [java] at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable$1.run(UIThreadRunnable.java:89)
> [java] at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> [java] at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> [java] at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
> [java] at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
> [java] at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
> [java] at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
> [java] at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
> [java] at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
> [java] at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> [java] at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
> [java] at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> [java] at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
> [java] at org.eclipse.swtbot.eclipse.junit4.headless.UITestApplication.start(UITestApplication.java:53)
> [java] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
> [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(Method.java:616)
> [java] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
> [java] at org.eclipse.core.launcher.Main.main(Main.java:34)
> {noformat}
--
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-6316) Generate Shrinkwraped archived
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6316?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6316.
----------------------------------------
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!
> Generate Shrinkwraped archived
> ------------------------------
>
> Key: JBIDE-6316
> URL: https://issues.jboss.org/browse/JBIDE-6316
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: testing-tools
> Reporter: Pete Muir
> Fix For: LATER
>
>
> Often it is useful to generate an archive when you are writing a test to deploy it manually to check certain failures, or modify files inline.
> Provide the ability to "export" a shrinkwraped archive to disk
--
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-6411) [tester] Add ability to peruse JBoss UDDI v3 repository to pick WS to test
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6411?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6411.
----------------------------------------
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!
> [tester] Add ability to peruse JBoss UDDI v3 repository to pick WS to test
> --------------------------------------------------------------------------
>
> Key: JBIDE-6411
> URL: https://issues.jboss.org/browse/JBIDE-6411
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 3.2.x
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Now that we have the ability to poke at a WSDL file and pick out enough details to test a WS we should offer a way to browse the UDDI v3 repository in some JBoss runtimes to allow someone to pick from the list of published services to test.
--
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-2347) Locale control feature
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2347?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-2347.
----------------------------------------
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!
> Locale control feature
> ----------------------
>
> Key: JBIDE-2347
> URL: https://issues.jboss.org/browse/JBIDE-2347
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Tomasz Wilczynski
> Assignee: Daniel Azarov
> Fix For: LATER
>
>
> It would be very useful if Jboss Tools were locale sensitive.
> In my case, changing the default locale in faces-config.xml from 'en' to 'pl' has no effect in code assist box content.
> Only when I delete or rename messages_en.properties, the code assist looks up for entries in messages_pl.properties.
--
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-8936) WebContent folder is missing for seam project in 'Project Explorer' view
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8936?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-8936.
----------------------------------------
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!
> WebContent folder is missing for seam project in 'Project Explorer' view
> ------------------------------------------------------------------------
>
> Key: JBIDE-8936
> URL: https://issues.jboss.org/browse/JBIDE-8936
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 3.3.0.M1
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Fix For: LATER
>
> Attachments: screenshot61.png, screenshot62.png, screenshot63.png
>
>
> After creating seam project there is no way to open xhtml page for editing because WebContent folder is filtered out by default
> !screenshot61.png!
> Select 'Go Into' item from context menu on project and it appears in view
> !screenshot62.png!
--
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-3763) Open On feature for Drools editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3763?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-3763.
----------------------------------------
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!
> Open On feature for Drools editor
> ---------------------------------
>
> Key: JBIDE-3763
> URL: https://issues.jboss.org/browse/JBIDE-3763
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: drools
> Affects Versions: 3.0.0.CR2
> Environment: JBDS 2.0.0.CR2
> Reporter: Joao Viragine
> Priority: Minor
> Fix For: LATER
>
>
> It would be great if we could use Open On in Drools DRL editor.
--
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-1347) Creation of Seam web project - JSF implementation error
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-1347?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-1347.
----------------------------------------
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!
> Creation of Seam web project - JSF implementation error
> -------------------------------------------------------
>
> Key: JBIDE-1347
> URL: https://issues.jboss.org/browse/JBIDE-1347
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 2.0.0.CR1
> Environment: WindowsXP SP2
> rhds-win32-1.0.0.CR1.jar
> Red Hat Developer Studio
> Version: 1.0.0 BETA2
> Build: Cr1-20071115
> JDK 1.5_08
> Reporter: Aliaksey Nis
> Fix For: LATER
>
> Attachments: Library.txt
>
>
> 1. Main menu > New project > Seam > Seam Web Project
> 2. Enter project name... goto to JSF implementation step.
> 3. New component library list press New button.
> 4. Name new library, add random jar. Press Finish.
> 5. Move newly created library to components library list.
> 6. Open it's tree (click on "+"), double click on jar file.
> Error message and exception appears. Log attached.
--
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-4067) Add option to open xhtml (.seam) page displayed in Eclipse Browser in JBoss Tools HTML Editor.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4067?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-4067.
----------------------------------------
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!
> Add option to open xhtml (.seam) page displayed in Eclipse Browser in JBoss Tools HTML Editor.
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-4067
> URL: https://issues.jboss.org/browse/JBIDE-4067
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Joao Viragine
> Assignee: Alexey Kazakov
> Priority: Minor
> Fix For: LATER
>
>
> It's a very useful feature when we are developing pages.
> The JBDS/Tools gets the URL of Eclipse Browser and displays the correspondent page in the JBoss Tools HTML Editor.
> As we have an option to click in a web page and 'Run As/Run on Server", we could have an option to do the reverse: click in a "running page" and open it for editing.
> This behavior may be exposed as
> right button option or an icon in Eclipse Browser (perhaps beside the 'Go to selected URL' button)
> E.g.
> If we have the following URL in the Eclipse Browser: http://localhost:8080/seamRulez/JBossToolsRulez.seam?cid=123
> When we click in that proposed option, the JBDS/Tools opens the JBossToolsRulez.xhmtl in JSF Page Editor
>
--
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-2630) Create minimal Seam project (no DB), or/and add Seam facet with minimal impact (no DB)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2630?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-2630.
----------------------------------------
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 minimal Seam project (no DB), or/and add Seam facet with minimal impact (no DB)
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-2630
> URL: https://issues.jboss.org/browse/JBIDE-2630
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Affects Versions: 2.1.2
> Reporter: Francisco Jose Peredo Noguez
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: LATER
>
>
> Currently, to create a Seam project, one needs to configure a database connection, but Seam can be used in other contexts that maybe do not need a database connection, or that may not need to use JPA (for example a Web applications that is acting as the client of a WebService, or that needs to interact with a legacy database using plain JDBC or Ibatis, or to create an small example project.
> I find the need to specify the database connection cumbersome, specially if I just want to create a small "test project" to try to solve an small non database related problem in isolation (or to demonstrate Seam capabilities beyond its integration with JPA).
> I think it should be possible to create a Minimal Seam project using the wizard, one that does not ask for a database connection, and does not need to use a database connection.
> It should also be possible to add the Seam facet to a project with minimal impact to the project (minimal web.xml alteration for support for JSF, or perhaps only do that if JavaServer Faces facet is selected, copying of minimal required libs, and a components.xml with literally everything disabled (specially anything database related)).
--
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-3751) Let user change Seam version on Seam settings page.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3751?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-3751.
----------------------------------------
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!
> Let user change Seam version on Seam settings page.
> ---------------------------------------------------
>
> Key: JBIDE-3751
> URL: https://issues.jboss.org/browse/JBIDE-3751
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> Max Andersen:
> "now that we have more than 2 versions of Seam and especially 2.0 and 2.1 being so close it might make sense to show all runtimes in our seam combo and simply error if the versions doesn't match ? Or even better show a warning and if users click apply anyway and they are in a faceted project they are given a Dialog asking if they really want to change version and we show the change version dialog ... that would avoid the need to browse two different ui's for this."
--
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