[JBoss JIRA] (JBIDE-9477) Serialize objects as XML on Debug (for unit testing purposes)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9477?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-9477.
----------------------------------------
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!
> Serialize objects as XML on Debug (for unit testing purposes)
> -------------------------------------------------------------
>
> Key: JBIDE-9477
> URL: https://issues.jboss.org/browse/JBIDE-9477
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Reporter: George Gastaldi
> Fix For: LATER
>
>
> This is an idea that I had some time ago: A feature that when a breakpoint on debug is reached, allow an inspected object to be serialized in XML (using XStream for example) for unit-testing purposes.
> The basic idea is to rebuild the whole object and ease Unit Testing of applications by rebuilding them when necessary.
--
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-2044) NullPointerException when open persistence.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2044?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-2044.
----------------------------------------
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!
> NullPointerException when open persistence.xml
> ----------------------------------------------
>
> Key: JBIDE-2044
> URL: https://issues.jboss.org/browse/JBIDE-2044
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 2.0.0.GA, 2.0.1
> Reporter: João Bosco Monteiro
> Fix For: LATER
>
>
> I always get a NPE when I open any persistence.xml, in source ou vsual mode. The stack trace follows:
> eclipse.buildId=I20070625-1500
> java.version=1.6.0_03
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR
> Command-line arguments: -os win32 -ws win32 -arch x86 -data D:\Pessoal\Joao\workspace_eclipse
> This is a continuation of log file D:\Pessoal\Joao\workspace_eclipse\.metadata\.bak_0.log
> Created Time: 2008-04-07 11:16:45.093
> Error
> Thu Apr 10 07:19:39 VET 2008
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.NullPointerException
> at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart$StatusLineLabelProvider.getText(XMLMultiPageEditorPart.java:322)
> at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart.updateStatusLine(XMLMultiPageEditorPart.java:850)
> at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart$5.selectionChanged(XMLMultiPageEditorPart.java:429)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:842)
> 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.JFaceUtil$1.run(JFaceUtil.java:46)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:193)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:840)
> at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1642)
> at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1083)
> at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:392)
> at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart$TextEditorPostSelectionAdapter.selectionChanged(XMLMultiPageEditorPart.java:233)
> at org.eclipse.wst.sse.ui.StructuredTextEditor$6.run(StructuredTextEditor.java:905)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.fireSelectionChanged(StructuredTextEditor.java:903)
> at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.handlePostSelectionChanged(StructuredTextEditor.java:961)
> at org.eclipse.wst.sse.ui.StructuredTextEditor$5.selectionChanged(StructuredTextEditor.java:884)
> at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2546)
> at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2498)
> at org.eclipse.jface.text.TextViewer$5.run(TextViewer.java:2477)
> at org.eclipse.swt.widgets.Display.runTimer(Display.java:3745)
> at org.eclipse.swt.widgets.Display.messageProc(Display.java:2967)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2264)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3291)
> 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:153)
> 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(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:504)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
--
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-3885) Add Rete View to Drools dslr editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3885?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-3885.
----------------------------------------
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 Rete View to Drools dslr editor
> -----------------------------------
>
> Key: JBIDE-3885
> URL: https://issues.jboss.org/browse/JBIDE-3885
> 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
>
>
> Rete View is only available in Drools drl editor but not in dslr editor.
> It would be nice if we had this option in both.
--
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-8623) Dynamic feature loading
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8623?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-8623.
----------------------------------------
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!
> Dynamic feature loading
> -----------------------
>
> Key: JBIDE-8623
> URL: https://issues.jboss.org/browse/JBIDE-8623
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 3.2.0.Final
> Reporter: Jiri Peterka
> Fix For: LATER
>
>
> Goal is to make JBT/JBDS more modular and user friendly via dynamic features loading when they are really used. Not to have current state when unused features are present and loaded and some extra features needs to be installed via update site manually.
> Expected state could look like:
> * Present menu items for all provided actions (like New <any-type-of> Project)
> * if selected for the first time, feature will be downloaded (if needed), installed and loaded without any special user interaction
> * wizard (or any other action) will continue after that in situation
> I see several related issues:
> 1. Seamless feature loading (currently after feature installation eclipse restart is usually needed which is not very usable for this)
> 2. Architecture (it could be quite challenging to implement dummy plug-in with some extensions like menus triggering feature post-loading)
> 3. Installation speed (currently all p2 operation are quite slow so I'm not sure if it is feasible)
> Note: take this feature request as an early proposal. I guess many people would appreciate this kind of architecture and JBT/JBDS would become more agile for the future. Everyone developer requires only specific set of IDE features. This is how they could be satisfied.
--
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-6005) JBoss Profiler 2 integration
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6005?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6005.
----------------------------------------
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!
> JBoss Profiler 2 integration
> ----------------------------
>
> Key: JBIDE-6005
> URL: https://issues.jboss.org/browse/JBIDE-6005
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: profiler
> Reporter: Jesper Pedersen
> Labels: nextjbosstools
> Fix For: LATER
>
>
> Provide integration support for the JBoss Profiler 2 branch, such that the tool and be run from within JBoss Tools - and the reports can be viewed.
--
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-558) Use Ivy as foundation for libmanagement tool
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-558?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBIDE-558.
---------------------------------------
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!
> Use Ivy as foundation for libmanagement tool
> --------------------------------------------
>
> Key: JBIDE-558
> URL: https://issues.jboss.org/browse/JBIDE-558
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: z - Legacy - libmanagement
> Reporter: Max Rydahl Andersen
> Labels: libmanagement
> Fix For: LATER
>
>
> Ivy is non-intrusive, ant and maven compatible and it is very pluggable.
> For libraries there does not exist pom's/ivy-xml we can create them and have an rhds-ivy lib, it handles multiple configuration (usefull for hibernate) and it supports just copying to local lib dir ...all good.
> Links:
> main site: http://incubator.apache.org/ivy/
> classpath container in eclipse: http://incubator.apache.org/ivy/ivyde/cp_container.html (right direction, but needs more)
> still not solved:
> how to handle related javadoc and source attachements ?
--
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-8634) Get rid of WTP DOM model in our JSF EL validation because it's too slow.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8634?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-8634.
----------------------------------------
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!
> Get rid of WTP DOM model in our JSF EL validation because it's too slow.
> ------------------------------------------------------------------------
>
> Key: JBIDE-8634
> URL: https://issues.jboss.org/browse/JBIDE-8634
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsf
> Affects Versions: 3.2.0.Final
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> We use WTP DOM model because it provides us offsets and length of XML nodes for XHTML/JSP files. But it's too slow. Let's try to replace it by something lighter.
--
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-4013) Suggestions for Insert Tag dialog of external pages
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4013?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-4013.
----------------------------------------
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!
> Suggestions for Insert Tag dialog of external pages
> ---------------------------------------------------
>
> Key: JBIDE-4013
> URL: https://issues.jboss.org/browse/JBIDE-4013
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsf, jsp/jsf/xml/html source editing
> Affects Versions: 3.0.0.GA
> Reporter: Yura Zhishko
> Assignee: Alexey Kazakov
> Priority: Minor
> Fix For: LATER
>
>
> 1) Open any page JSP or XHTML
> 2) Try to DnD external page or image from local place that doesn't belong to a project
> ASSERT: Insert tag dialog with options appears
> 3) Choose any option and press OK
> ASSERT: Empty tag is inserted
> I don't think that it is a correct behavior in such situation. There many different variants exist to rebuild it: insert absolute path for required attribute, make a warning that current page or image doesn't belong to a project, or disable DnD from local space at all. We have to find a decision of this problem. I propose to insert absolute path for required attribute. Any other suggestions maybe?
--
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-3844) Renaming faces-config.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3844?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-3844.
----------------------------------------
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!
> Renaming faces-config.xml
> -------------------------
>
> Key: JBIDE-3844
> URL: https://issues.jboss.org/browse/JBIDE-3844
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 3.0.0.GA
> Environment: WindowsXP SP2
> JBoss Tools
> Version: 3.0.0.GA
> Build id: JBossTools-ALL-win32-3.0.0.GA-N200902190001-H1442.
> JRE 1.5_08
> Reporter: Aliaksey Nis
> Priority: Minor
> Fix For: LATER
>
>
> EXECUTE: Create JSF 1.2 Kickstart project.
> EXECUTE: Create JSP page.
> EXECUTE: In package explorer select this JSP page. Right click. Press Refactor>Rename.
> EXECUTE: Change name of page, press ok.
> EXECUTE: In package explorer select faces-config.xml. Right click. Press Refactor>Rename.
> EXECUTE: Change name of config, press ok.
> FAILURE: Exception thrown(eclipse validator). tr.jsp - old name of created JSP page.
> Resource '/test/WebContent/tr.jsp' does not exist.
> org.eclipse.core.internal.resources.ResourceException: Resource '/test/WebContent/tr.jsp' does not exist.
> at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:317)
> at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:194)
> at org.eclipse.core.internal.resources.Resource.deleteMarkers(Resource.java:746)
> at org.eclipse.wst.validation.internal.MarkerManager.clearMarker(MarkerManager.java:60)
> at org.eclipse.wst.validation.internal.ValBuilderJob.visit(ValBuilderJob.java:211)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48)
> at org.eclipse.wst.validation.internal.ValBuilderJob.deltaBuild(ValBuilderJob.java:180)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:149)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:125)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months