[
https://jira.jboss.org/jira/browse/JBIDE-5380?page=com.atlassian.jira.plu...
]
Martin Malina commented on JBIDE-5380:
--------------------------------------
I tested the deployment with JBossTools-Update-3.1.0.v200912081204N-H34-GA.zip and SOA-P
5.0.0.ER5 on Mac OS X 10.6.2 Snow Leopard.
After uncommenting the user admin in server/all/conf/props/soa-users.properties I got as
far as testing the connection using the Test Connection in JBDS. But the deployment fails
as Dominik says.
From JBPM-2289:
"The SOA distribution of jBPM is tuned for
production deployment and maps this servlet to a URL pattern in the secured area. In
consequence, the upload servlet is no longer able to accept GPD deployment requests, as
GPD does not support authentication.
To reenable GPD deployment, map the servlet to the path expected by the GPD, namely
"/upload/*"."
This seems to be the main problem - if GPD does not support authentication, then it
can't be in a secured area. Therefore I don't understand why the option to enter
the credentials is even there in JBDS. Anyway, we need to decide how to make this work.
Either the servlet must be mapped somewhere else in SOA-P, or GPD needs to support
authentication?
jBPM deployment wizard - both test connection and deployment
failing
---------------------------------------------------------------------
Key: JBIDE-5380
URL:
https://jira.jboss.org/jira/browse/JBIDE-5380
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.M4
Environment: JBoss Tools - 3.1.0.v200910281724M-H247-M4 - Linux x86_64, Vista
x86
SOA-P 5.0.0.ER4
Reporter: Dominik Pospisil
Both test connection and deployment to bundled SOA-P 5.0.0.ER4 jBPM runtime fails.
Failure message:
An exception happened with testing server connection.
Reason:
An unexpected exception caused the test connection opertaion to fail
Checked that jbpm console is up and running. Also tried unsecure jbpm console, no
difference.
No other error messages/logs found.
--
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