[JBoss JIRA] Created: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
11:41 a.m.
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
11:53 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5038:
------------------------------------------
Here's the wiki created by the Riftsaw team detailing the deployment descriptor.
http://www.jboss.org/community/wiki/DeployingBPELtoRiftSaw
Other details on the deployment descriptor can also be found at the Apache ODE site
http://ode.apache.org/user-guide.html#UserGuide-DeploymentDescriptor
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
12:11 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5038:
------------------------------------------
Here's the exception from the ODE descriptor file editor:
java.lang.NoClassDefFoundError:
org/eclipse/bpel/apache/ode/deploy/model/dd/util/ddResourceFactoryImpl
at
org.eclipse.bpel.apache.ode.deploy.ui.editors.ODEDeployMultiPageEditor.createModel(ODEDeployMultiPageEditor.java:192)
at
org.eclipse.bpel.apache.ode.deploy.ui.editors.ODEDeployMultiPageEditor.init(ODEDeployMultiPageEditor.java:98)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:644)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
at
org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at
org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at
org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at
org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1608)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:778)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:677)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2854)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2676)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:361)
at
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:168)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:229)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:208)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274)
at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:373)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:526)
at
org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:842)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:840)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1101)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1205)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
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:597)
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)
Caused by: java.lang.ClassNotFoundException:
org.eclipse.bpel.apache.ode.deploy.model.dd.util.ddResourceFactoryImpl
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:494)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
... 78 more
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
12:24 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5038:
------------------------------------------
To get the editor:
1) Create a file called "bpel-deploy.xml" in the same directory with the *.bpel
and *.wsdl files. OR Create a new Apache ODE Deployment Descriptor using the New Apache
ODE Deployment Descriptor wizard. OR try copy an existing bpel-deploy.xml file (like from
the imported BPEL quickstarts)
2) Try to open the file.
By default, the ODE Deployment Descriptor editor tries to open the file, and fails with
the exception above.
The only workaround is to open the .xml file in a different editor such as the XML Editor
or the Text Editor.
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
12:24 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5038:
------------------------------------------
That should be "To get the error" - not "To get the editor" - sorry.
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
4:35 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-5038:
---------------------------------
This issue is because that the classes of the plugin
"org.eclipse.bpel.apache.ode.deploy.model" are missing, I am not sure why Jboss
tools build did not pick the classes file of the plugin. When I run BPEL tools from
code, the descriptor editor works.
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
10:12 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-5038:
-----------------------------------
Well, my usual explanation for "sources not found while building is:
because they're not included in the map files that PDE uses to fetch sources. When you
add new plugins or features (or test plugins/features), you have to let me or Denis (or
anyone with write permission to
http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.r...
) know what new stuff has been added.
However, org.eclipse.bpel.apache.ode.deploy.model plugin is already in the map, and its
build.properties looks OK (though I've added the "." entry just in case
that'll help).
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
5:56 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Snjezana Peco commented on JBIDE-5038:
--------------------------------------
build.properties for org.eclipse.bpel.apache.ode.deploy.model isn't valid.
Attached is a patch.
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
5:58 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Snjezana Peco updated JBIDE-5038:
---------------------------------
Attachment: bpel.patch
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Attachments: bpel.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
2:42 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-5038:
---------------------------------
Nick, I checked the JBT build of yesterday, it still doesn't contains the classes in
the plugin.
I applied the patch which provided by Snjezana, and will check it with tomorrow's
build.
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.CR1
Attachments: bpel.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
12:12 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Denis Golovin commented on JBIDE-5038:
--------------------------------------
merged to M4 branch
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.M4
Attachments: bpel.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
12:12 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-5038:
---------------------------------
Fix Version/s: 3.1.0.M4
(was: 3.1.0.CR1)
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.M4
Attachments: bpel.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
3 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5038:
------------------------------------------
With the new build JBossTools-Update-3.1.0.v200910210858N-H8-RC1.zip this issue has gone
away. You can now create a deployment descriptor and deploy a BPEL project.
My only question then remains... Do we need to change the name of this deployment
descriptor from "Apache ODE Deployment Descriptor" to something more
JBoss-specific? Seeing "Apache ODE", though Riftsaw uses the technology,
doesn't necessarily connect immediately to "BPEL" in my mind. Maybe this is
just me though?
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.M4
Attachments: bpel.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
1:13 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-5038:
---------------------------------
I have already created a JIRA for this, see JBIDE-4825
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.M4
Attachments: bpel.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
1:20 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5038) With changes to BPEL project wizard, BPEL deployment is broken in UI
[
https://jira.jboss.org/jira/browse/JBIDE-5038?page=com.atlassian.jira.plu...
]
Denny Xu resolved JBIDE-5038.
-----------------------------
Resolution: Done
Also verified with 3.1.0 M4 build, it works.
With changes to BPEL project wizard, BPEL deployment is broken in UI
--------------------------------------------------------------------
Key: JBIDE-5038
URL: https://jira.jboss.org/jira/browse/JBIDE-5038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Reporter: Brian Fitzpatrick
Assignee: Denny Xu
Priority: Critical
Fix For: 3.1.0.M4
Attachments: bpel.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Rob helped out with getting the BPEL project structure working like the ESB project
structure so we are more consistent down the line and have more flexibility. We now have a
JBoss-provided BPEL project wizard instead of what came from the Eclipse project.
The downside to this is that we lose the Apache ODE Descriptor code that used to work (in
fact, it's broken and throws an error when you try to use it or open a non-ODE
deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in:
org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's
now not connected to our BPEL project. So we need to create a new mechanism for generating
the JBoss Riftsaw deployment descriptor.
--
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
6010
days inactive
6016
days old
jbosstools-issues@lists.jboss.org
14 comments
5 participants
participants (5)
-
Brian Fitzpatrick (JIRA) -
Denis Golovin (JIRA)
-
Denny Xu (JIRA)
-
Nick Boldt (JIRA)
-
Snjezana Peco (JIRA)