[JBoss JIRA] (JBTIS-289) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-289?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-289:
-----------------------------------------
Looks great Paul!
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
> ----------------------------------------------------------------
>
> Key: JBTIS-289
> URL: https://issues.jboss.org/browse/JBTIS-289
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: ESB
> Affects Versions: 4.0.0
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.0.0
>
>
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> Steps as defined by Nick (thanks Nick!):
> a) the contents of the examples are in a former employee's SVN workspace
> and haven't been updated since a couple of years. They don't really work
> as well as they could.
> b) the examples are all mostly duplicated in the quickstarts folder that
> ships with SOA-P 5.3.1. See
> https://bugzilla.redhat.com/show_bug.cgi?id=951677 and
> https://issues.jboss.org/browse/JBTIS-62
> Basically, we need to:
> * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable
> eclipse projects (merge in contents from duplicate examples in Denny's
> workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned;
> if not, no great need.
> * copy the older examples that are not already in SOA-P 5.3 - the ones
> that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be
> available there.
> * update the BPEL Examples guide as needed
> * document the fact that these examples are no longer available as
> importable zipped example projects contributed by a plugin, but rather
> as already-unpacked projects nested within the SOA-P runtime zip
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15517) Explorer: There's currently no way to see that an application is scaled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15517?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15517:
------------------------------------------
[~jcantrill] the properties view is a view that you can always keep opened and see the properties for the selected item in any other view (project explorer, servers view etc.). The properties view is limited though in what it can display (you dont implement the widgets, you just provide the displayable content, the strings). That's why we implemented the details dialog where we are in full control of what and how things are displayed.
I suggest that you try to have the same consistent display on both, pretty sure that this should be doable. The boolean variant looks more compelling to me, agree?
> Explorer: There's currently no way to see that an application is scaled
> -----------------------------------------------------------------------
>
> Key: JBIDE-15517
> URL: https://issues.jboss.org/browse/JBIDE-15517
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Labels: explorer
> Fix For: 4.3.x
>
>
> There's currently no way for the user to see that an application is scaled.
> We should show this to the user via decorations in the OpenShift Explorer and also in the application details.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17483) Quick Fix for Console configuration "" does not exist
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17483?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17483:
---------------------------------------------
okey so with this project I can confirm this issue and it is truly mysterious since even when I delete the .settings/*hibernate* files (meaning hibernate is not enabled) the error shows up.
That should not happen.
> Quick Fix for Console configuration "" does not exist
> -----------------------------------------------------
>
> Key: JBIDE-17483
> URL: https://issues.jboss.org/browse/JBIDE-17483
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.CR1
>
> Attachments: JBIDE-17483-webnate.zip
>
>
> When using Maven import on "someone else's" project, it is fairly common to get a complaint about the missing Console Configuration. Numerous workarounds have been documented and can be found via Google - some work, some do not - ideally we would offer a quickfix to help address this common error message inside of the IDE.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17924) java add annotation is available on projects but fail when running it
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17924?page=com.atlassian.jira.plugi... ]
George Gastaldi resolved JBIDE-17924.
-------------------------------------
Assignee: George Gastaldi (was: Max Rydahl Andersen)
Resolution: Done
Fixed in Forge 2.9.2.Final
> java add annotation is available on projects but fail when running it
> ---------------------------------------------------------------------
>
> Key: JBIDE-17924
> URL: https://issues.jboss.org/browse/JBIDE-17924
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Max Rydahl Andersen
> Assignee: George Gastaldi
> Fix For: 4.2.0.CR1
>
>
> EXECUTE: Have an eclipse project in focus in explorer.
> EXECUTE: Cmd+4
>
> Java: Add Annotation shows up.
> Select it.
> result: error in log with this:
> org.jboss.forge.addon.facets.FacetNotFoundException: No Facet of type [interface org.jboss.forge.addon.parser.java.facets.JavaSourceFacet] is installed.
> at org.jboss.forge.addon.facets.AbstractFaceted.getFacet(AbstractFaceted.java:51)
> at org.jboss.forge.addon.parser.java.beans.ProjectOperations.getProjectClasses(ProjectOperations.java:24)
> at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl.setupTargetClass(JavaAddAnnotationCommandImpl.java:296)
> at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl.initializeUI(JavaAddAnnotationCommandImpl.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81)
> at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl_$$_javassist_59bd122d-fa09-40ec-857b-60ae17012d9e.initializeUI(JavaAddAnnotationCommandImpl_$$_javassist_59bd122d-fa09-40ec-857b-60ae17012d9e.java)
> at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.initialize(SingleCommandControllerImpl.java:55)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_3230b267-466d-40b8-9fd2-bd6828930098.initialize(CommandController_$$_javassist_3230b267-466d-40b8-9fd2-bd6828930098.java)
> at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:103)
> at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:187)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:326)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:316)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:347)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1504)
> at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1632)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1500)
> at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1598)
> at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5719)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.superKeyDown(Widget.java:1908)
> at org.eclipse.swt.widgets.Widget.keyDown(Widget.java:1085)
> at org.eclipse.swt.widgets.Control.keyDown(Control.java:2400)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5629)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2329)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5691)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5128)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5277)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> Caused by: org.jboss.forge.addon.facets.FacetNotFoundException: No Facet of type [interface org.jboss.forge.addon.parser.java.facets.JavaSourceFacet] is installed.
> ... 76 more
> I would have expected either:
> a) not having add annotation on projects
> b) when running forge would report a more informative error on why it is failing
> c) run add annotation but let me select which file it is for...
> anything except this silent logged error ;)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months