[JBoss JIRA] Created: (JBIDE-5462) BPEL Editor gives validation errors after wsdl updates
by Jeff DeLong (JIRA)
BPEL Editor gives validation errors after wsdl updates
------------------------------------------------------
Key: JBIDE-5462
URL: https://jira.jboss.org/jira/browse/JBIDE-5462
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Environment: JBoss BPEL Editor 1.0.0.v200912111224M-H175-RC1 org.jboss.tools.bpel.feature.feature.group on Mac JDK 1.6 Eclipse 3.5.1
Reporter: Jeff DeLong
Attachments: PolicyQuoteProcessService.zip
After creating BPEL process, creating partnerLinks, variables, and receive operation, I noticed an error in the process service wsdl. After updating the wsdl, the BPEL validator continues to show two errors:
Description Resource Path Location Type
<bpel:receive> activity "ReceivePolicyQuoteRequest" specifies a portType "orchws:PolicyQuoteProcessServicePortType", yet this portType does not match the portType derived from "myRole" of partnerLink "PolicyQuoteProcessService" defined in WSDL "platform:/resource/PolicyQuoteProcessService/bpelContent/PolicyQuoteProcessService.wsdl" PolicyQuoteProcess.bpel /PolicyQuoteProcessService/bpelContent line 54 BPEL Validation Marker
Description Resource Path Location Type
variable "PolicyQuoteRequest" of type "<wsdl:message "PolicyQuoteProcessServiceReq">" is not compatible with WSDL message "<wsdl:message "PolicyQuoteProcessServiceReq">". PolicyQuoteProcess.bpel /PolicyQuoteProcessService/bpelContent line 54 BPEL Validation Marker
I will attach the project files.
--
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
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-5465) CR1 updatesite zip cannot be installed from because of maven weirdness
by Max Rydahl Andersen (JIRA)
CR1 updatesite zip cannot be installed from because of maven weirdness
----------------------------------------------------------------------
Key: JBIDE-5465
URL: https://jira.jboss.org/jira/browse/JBIDE-5465
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.1.0.CR1
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Downloaded update zip from http://download.jboss.org/jbosstools/builds/nightly/3.1.0.RC1/20091214152...
Download fresh eclipse from eclipse.org
Added the updatesite zip
Added m2eclipse update site
Tried to install All features (excluding birt and tptp and SDK's)
And received this error - only when I installed m2eclipse *first* did it want to go pass this:
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss Maven Seam Integration 1.0.0.v200912141523M-H176-RC1 (org.jboss.tools.maven.seam.feature.feature.group 1.0.0.v200912141523M-H176-RC1)
Missing requirement: JBoss Maven Core 1.0.0.v200912141523M-H176-RC1 (org.jboss.tools.maven.core 1.0.0.v200912141523M-H176-RC1) requires 'bundle org.maven.ide.eclipse 0.0.0' but it could not be found
Cannot satisfy dependency:
From: Integration Seam projects with Maven 1.0.0.v200912141523M-H176-RC1 (org.jboss.tools.maven.seam 1.0.0.v200912141523M-H176-RC1)
To: bundle org.jboss.tools.maven.core 0.0.0
Cannot satisfy dependency:
From: JBoss Maven Seam Integration 1.0.0.v200912141523M-H176-RC1 (org.jboss.tools.maven.seam.feature.feature.group 1.0.0.v200912141523M-H176-RC1)
To: org.jboss.tools.maven.seam [1.0.0.v200912141523M-H176-RC1]
Why are we depending on 0.0.0 ? ( I assume that is the problem )
And shouldn't this work if m2eclipse is available as an update site ?
--
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
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-5006) Support creation of ESB archive with files from other projects
by Jeff DeLong (JIRA)
Support creation of ESB archive with files from other projects
--------------------------------------------------------------
Key: JBIDE-5006
URL: https://jira.jboss.org/jira/browse/JBIDE-5006
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: Jeff DeLong
Sometimes the files required in an esb archive are created in another project and / or need to be shared across multiple projects. For example, a drools rule file (drl file) would be created in a Drools project, but need to be included in the esb archive generated from and ESB "rules service" project. Or the xsds to support EBWS inXSD, outXSD configuration need to be shared across many services.
It would be useful if there were a was to support creation of ESB archive that includes files from other projects.
There is a similar requirement for BPEL projects. The BPEL archive requires the wsdl files, but it may be more convenient to keep these in another project location.
--
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
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-4931) 'Preview' button in 'Edit XPath' dialog throws exception
by Denis Golovin (JIRA)
'Preview' button in 'Edit XPath' dialog throws exception
--------------------------------------------------------
Key: JBIDE-4931
URL: https://jira.jboss.org/jira/browse/JBIDE-4931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
1. EXECUTE: Create JBoss AS Server and expand XMP COnfiguration/Ports node in JBoss Servre View
2. EXECUTE: Select 'Edit XPath' form popup menu on JBoss Web child node
3. EXECUTE: Press 'Preview'
4. ASSERT: There is no exceptions in Error Log View
now it throws exception showed below
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:3884)
at org.eclipse.swt.SWT.error(SWT.java:3799)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
at org.jboss.ide.eclipse.as.ui.dialogs.XPathDialogs$XPathDialog.previewPressed(XPathDialogs.java:411)
at org.jboss.ide.eclipse.as.ui.dialogs.XPathDialogs$XPathDialog$7.widgetSelected(XPathDialogs.java:302)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
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.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.jboss.ide.eclipse.as.ui.views.server.extensions.XPathActionProvider$4.run(XPathActionProvider.java:145)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: java.lang.NullPointerException
at org.jboss.ide.eclipse.as.ui.dialogs.XPathDialogs$XPathDialog$8$1.run(XPathDialogs.java:405)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
... 44 more
--
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
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-5402) Create new Portlet wizard - portlet source not generated
by Dominik Pospisil (JIRA)
Create new Portlet wizard - portlet source not generated
--------------------------------------------------------
Key: JBIDE-5402
URL: https://jira.jboss.org/jira/browse/JBIDE-5402
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal
Affects Versions: 3.1.0.M4
Environment: JBossTools 3.1.0.M4
Linux x86_64
JBoss EPP 4.3 CR2
Reporter: Dominik Pospisil
After creating new portlet using New Portlet wizard, portlet source code not generated.
Steps to reproduce:
1) Create new "Dynamic Web Project" with modified configuration - add JBoss Core Portlet 2.0 facet
2) File -> New -> Other -> Portlet -> Java Portlet
3) Choose Name, package, click Finish
Results:
Created portlet registered in both portlet.xml and portlet-instances.xml but the source code is missing. Only empty package is created.
--
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
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-5063) Fix SeamRefactoringAllTests
by Alexey Kazakov (JIRA)
Fix SeamRefactoringAllTests
---------------------------
Key: JBIDE-5063
URL: https://jira.jboss.org/jira/browse/JBIDE-5063
Project: Tools (JBoss Tools)
Issue Type: Task
Components: QA, Seam
Affects Versions: 3.1.0.M4
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 3.1.0.M4, 3.1.0.CR1
testSeamComponentRename:
There is unexpected number of changes expected:<7> but was:<4>
junit.framework.AssertionFailedError: There is unexpected number of changes expected:<7> but was:<4>
at org.jboss.tools.seam.core.test.refactoring.SeamComponentRefactoringTest.renameComponent(SeamComponentRefactoringTest.java:120)
at org.jboss.tools.seam.core.test.refactoring.SeamComponentRefactoringTest.testSeamComponentRename(SeamComponentRefactoringTest.java:81)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115)
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.test.UITestApplication.runApplication(UITestApplication.java:138)
at org.eclipse.test.UITestApplication.run(UITestApplication.java:60)
at org.eclipse.test.UITestApplication.start(UITestApplication.java:210)
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 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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
at org.eclipse.core.launcher.Main.main(Main.java:34)
testSeamContextVariable_Component_Rename:
There is unexpected number of changes expected:<7> but was:<4>
junit.framework.AssertionFailedError: There is unexpected number of changes expected:<7> but was:<4>
at org.jboss.tools.seam.core.test.refactoring.SeamContextVariableRefactoringTest.renameContextVariable(SeamContextVariableRefactoringTest.java:44)
at org.jboss.tools.seam.core.test.refactoring.SeamContextVariableRefactoringTest.testSeamContextVariable_Component_Rename(SeamContextVariableRefactoringTest.java:126)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115)
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.test.UITestApplication.runApplication(UITestApplication.java:138)
at org.eclipse.test.UITestApplication.run(UITestApplication.java:60)
at org.eclipse.test.UITestApplication.start(UITestApplication.java:210)
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 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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
at org.eclipse.core.launcher.Main.main(Main.java:34)
See http://download.jboss.org/jbosstools/builds/nightly/latestBuild.html
--
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
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-5225) Composite Component file opened in wrong editor.
by Aliaksey Nis (JIRA)
Composite Component file opened in wrong editor.
------------------------------------------------
Key: JBIDE-5225
URL: https://jira.jboss.org/jira/browse/JBIDE-5225
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.1.0.CR1
Environment: WindowsXP SP2
JBoss Developer Studio
Version: 3.0.0.M4
Build id: jbdevstudio-eap-win32-3.0.0.v200911161447M-H94-M4
JRE 1.6
Reporter: Aliaksey Nis
Priority: Minor
EXECUTE: Create JSF 1.2 with Facelets Kickstart.
EXECUTE: Open Web Projects view, select Webcontent folder, right click on it.
EXECUTE: Select New > File > Composition Component.
EXECUTE: Input name, Press Finish.
FAILURE: New file opened in basic editor instead of JBoss Editor.
EXECUTE: Close editor. Right click on this file in Web Projects view.
ASSERT: "Open" options - check that JBoss Editor is selected(correct editor).
EXECUTE: Double click on this file.
FAILURE: This file opened in basic editor again.
So "Open with" option is correct, but file opened in wrong editor.
--
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
14 years, 6 months