[ https://jira.jboss.org/jira/browse/JBIDE-5380?page=com.atlassian.jira.plu... ] Dominik Pospisil updated JBIDE-5380: ------------------------------------ Environment: JBoss Tools - 3.1.0.v200910281724M-H247-M4 - Linux x86_64, Vista x86 SOA-P 5.0.0.ER4 was: JBoss Tools - 3.1.0.v200910281724M-H247-M4 - Linux x86_64 SOA-P 5.0.0.ER4 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5380?page=com.atlassian.jira.plu... ] Martin Malina commented on JBIDE-5380: -------------------------------------- !ENTRY org.jbpm.gd.jpdl 4 0 2009-12-10 15:11:12.795 !MESSAGE The server refused to execute the deployment. Check your credentials. !STACK 0 java.io.IOException: Server returned HTTP response code: 403 for URL: http://localhost:8080/jbpm-console/app/upload at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1313) at org.jbpm.gd.jpdl.util.ProcessDeployer.deployProcessWithServlet(ProcessDeployer.java:262) at org.jbpm.gd.jpdl.util.ProcessDeployer.access$3(ProcessDeployer.java:237) at org.jbpm.gd.jpdl.util.ProcessDeployer$1.run(ProcessDeployer.java:207) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.jbpm.gd.jpdl.util.ProcessDeployer.showProgressMonitorDialog(ProcessDeployer.java:199) at org.jbpm.gd.jpdl.util.ProcessDeployer.deploy(ProcessDeployer.java:103) at org.jbpm.gd.jpdl.deployment.DeploymentForm$1.widgetSelected(DeploymentForm.java:135) 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:1598) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1622) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1607) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1396) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3484) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3068) 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) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5380?page=com.atlassian.jira.plu... ] Dominik Pospisil commented on JBIDE-5380: ----------------------------------------- The "default" SOA-P server profile has jbpm-console unsecured. I am fine that the deployment does not work with all and producdion configs. But, with "default" profile this should work out-of-the-box. Server deployer path should be changed to "/jbpm-console/app/upload" by default, or the soa-p bundled jbpm console should be adjusted accordingly. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5380?page=com.atlassian.jira.plu... ] Martin Malina commented on JBIDE-5380: -------------------------------------- Yes, it is a problem with the secured deployments. But I just tried it with the default server profile and same problem occurs there. Then I tried to access the jbpm-console in a browser and it wants a password, so it seems the default profile is secured as well. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5380?page=com.atlassian.jira.plu... ] Martin Malina commented on JBIDE-5380: -------------------------------------- Does that mean that it should be fixed now and work together smoothly? If so, it which versions of JBTools and SOA-P can we expect this to work? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5380?page=com.atlassian.jira.plu... ] Alejandro Guizar commented on JBIDE-5380: ----------------------------------------- The upload servlet secured with basic auth will be shipped with SOA-P 5.0. It will be included in the upcoming 4.3 CP03 as well. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5380?page=com.atlassian.jira.plu... ] Dominik Pospisil closed JBIDE-5380. ----------------------------------- Verified on JBDS 3.0.0.CR2 (jbdevstudio-eap-linux-gtk-x86_64-3.0.0.v201002190339M-H173-CR2.jar) and SOA-P 5.0 Beta2 (GA). -- 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