[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5611) Unable to deploy jbpm process archive

[Koen Aers (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12506029#action_12506029 ] 

Koen Aers commented on JBIDE-5611:
----------------------------------

Ok, I finally got the time to setup my environment in order to test this properly. 

I used the following setup: 
- Fedora 12
- JBoss SOA-P 5.0.0.beta1
- Eclipse 3.5.1
- JBT 3.1.0.CR2 (nightly)

These are my conclusions:
- SOA-P 5.0.0.beta1 does NOT contain the webapp (/gpd-deployer/upload) which Alejandro added to facilitate deployment
- I changed the authentication of the jbpm-console webapp from Form to Basic
- Deployment works from the GPD using admin/admin (the default admin credentials that are to be uncommented in the configuration file) and using the deployer path (/jbpm-console/app/upload).
=> I committed two minor glitches that will avoid the additional authentication dialog and render the username/password textfields better on GTK

This is what still needs to be done (but this is server related and not tools related):
- expose the /gpd-deployer/upload servlet that has Basic authentication
(- make SOA-P run on my Mac)

> Unable to deploy jbpm process archive
> -------------------------------------
>
>                 Key: JBIDE-5611
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5611
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jbpm
>    Affects Versions: 3.1.0.CR1
>         Environment: JBDS Version: 3.0.0.CR1, SOA 5 beta and ER
> Build id: v201001051918M
> Build date: 201001051956
> Sun JDK 1.6, Linux 32 and 64
>            Reporter: Jiri Peterka
>            Assignee: Koen Aers
>            Priority: Blocker
>             Fix For: 3.1.0.CR2
>
>         Attachments: auth-with-predefined-credentials.png, deployment-error.png
>
>
> 1. Create jbpm project with default process
> 2. Try to deploy process archive ( click on process definition, Deployment tab and click Deploy Process Archive...)
> See screenshot for error description
> Note: Test Connection works ok

-- 
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