[JBoss JIRA] Created: (JBAS-6000) Remote Deployment does not work since StreamingTarget makes different assumptions about scheme of deployURI than DeploymentFactoryImpl.handleUri()
by Stefan Ocke (JIRA)
Remote Deployment does not work since StreamingTarget makes different assumptions about scheme of deployURI than DeploymentFactoryImpl.handleUri()
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6000
URL: https://jira.jboss.org/jira/browse/JBAS-6000
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.0.CR2, JBossAS-4.2.3.GA
Reporter: Stefan Ocke
Assignee: Ales Justin
To perform a JSR-88 deployment to a remotely installed server, the org.jboss.deployment.remoting.StreamingTarget seems to be the right target to use, since it perfomrs the file upload of the artificat to be deployed.
However, StreamingTarget cannot really be used, since it is immpossible to construct a deployURI that is understood by both, StreamingTarget and org.jboss.deployment.spi.factories.DeploymentFactoryImpl.handleUri():
- DeploymentFactoryImpl.handleUri() understands the follwoing URIs:
-- "http://org.jboss.deployment/jsr88" (only exact matches are allowed)
-- URIs shaving scheme "jnp"
- DeploymentManager impl only constructs a StreamingTarget, when the URI has a parameter "targetType=remote". This is in contradiction, wtih the excact matchin of "http://org.jboss.deployment/jsr88", sicne it just does not allow any parameters. So, to get a StreaminTarget, on has to use "jnp:" as scheme in the URI.
- But: StreamingTarget cannot handle URIs starting with "jnp", but just schemes like "socket" or "http", where an according TransportClientFactory exists in jboss-remoting module.
So in summary, handling of the deployURI seems to be quite inconsistent and works only for the local case and only if URI is "http://org.jboss.deployment/jsr88"
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-6152) URLComparator PrefixDeploymentSorter doesn't work for instance all in jboss 4.2.3GA only with instance "all"
by Benoit Reverbel (JIRA)
URLComparator PrefixDeploymentSorter doesn't work for instance all in jboss 4.2.3GA only with instance "all"
------------------------------------------------------------------------------------------------------------
Key: JBAS-6152
URL: https://jira.jboss.org/jira/browse/JBAS-6152
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: JBossAS-4.2.3.GA
Environment: Windows XP Pro/Linux Red Hat
Reporter: Benoit Reverbel
Assignee: Ales Justin
I used so far the PrefixDeploymentSorter to select in which order my archives would be deployed.
It worked fine in JBoss AS 4.2.0GA. Now I am upgrading to JBoss AS 4.2.3GA and it seems not to work anymore (only for instance "all").
When I use instance "default", the deployer follows number prefixes of my archives:
1) 010-myear.ear
2) 020-myjar.jar
3) 030-mywar.war
When using instance "all", it seems to use the default DeploymentSorter by deploying first service.xml, then my jars, after that my wars and at the end ears.
1) 020-myjar.jar
2) 030-mywar.war
3) 010-myear.ear
As I need to use JBoss 4.2.3GA in cluster mode, it is mandatory for me to start from "all" instance.
Is there any workaround or any special configuration to do ?
Best Regards,
Benoit Reverbel
--
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
15 years, 7 months
[JBoss JIRA] Resolved: (GPD-249) Cannot create process definition in root project folder
by Koen Aers (JIRA)
[ https://jira.jboss.org/jira/browse/GPD-249?page=com.atlassian.jira.plugin... ]
Koen Aers resolved GPD-249.
---------------------------
Resolution: Done
> Cannot create process definition in root project folder
> -------------------------------------------------------
>
> Key: GPD-249
> URL: https://jira.jboss.org/jira/browse/GPD-249
> Project: JBoss jBPM GPD
> Issue Type: Bug
> Components: jpdl
> Environment: jBPM designer: 3.1.5Beta1-N200810230806
> Reporter: Koen Aers
> Assignee: Koen Aers
> Priority: Critical
> Fix For: jBPM jPDL Designer 3.1.6
>
>
> Tried to create a process definition in the top level of a project (that is, I selected a project as the destination folder, not a subfolder within the project). The following exception appears repeatedly while typing the process name in the wizard, and the Finish button is not enabled. If I select a subfolder, the wizard completes without error.
> -------------------------------
> java.lang.IllegalArgumentException: Path must include project and resource name: /test_jbpm
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1628)
> at org.eclipse.core.internal.resources.Container.getFolder(Container.java:137)
> at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkContainerPathValid(Unknown Source)
> at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.verifyContentsValid(Unknown Source)
> at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.access$0(Unknown Source)
> at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage$3.modifyText(Unknown Source)
> 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.Widget.sendEvent(Widget.java:1158)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
> at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
> 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:1158)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
> 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:193)
> 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:386)
> 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:549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
--
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
15 years, 7 months