12:20 p.m.
SOA platform changed upload URL for jBPM
----------------------------------------
Key: JBESB-1673
URL: http://jira.jboss.com/jira/browse/JBESB-1673
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Fix For: 4.2.1 CP3
The SOA platform has changed the URL used for uploading the process definitions for the
'production' server instance. The consequence of this is that the QSes cannot
deploy their process definitions through the build.xml file.
The mapping should read
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
but now reads
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/app/upload/*</url-pattern>
</servlet-mapping>
The ant task is still using http://localhost:8080/jbpm-console/upload
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:28 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1673) SOA platform changed upload URL for jBPM
[ http://jira.jboss.com/jira/browse/JBESB-1673?page=comments#action_12408999 ]
Kevin Conner commented on JBESB-1673:
-------------------------------------
This was a deliberate change by the productisation team, to protect the servlet access
using security.
We need to modify the ant task to support the provision of security credentials and modify
the QS scripts to automatically choose the correct deployment URL.
SOA platform changed upload URL for jBPM
----------------------------------------
Key: JBESB-1673
URL: http://jira.jboss.com/jira/browse/JBESB-1673
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Fix For: 4.2.1 CP3
The SOA platform has changed the URL used for uploading the process definitions for the
'production' server instance. The consequence of this is that the QSes cannot
deploy their process definitions through the build.xml file.
The mapping should read
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
but now reads
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/app/upload/*</url-pattern>
</servlet-mapping>
The ant task is still using http://localhost:8080/jbpm-console/upload
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1673) SOA platform changed upload URL for jBPM
[ http://jira.jboss.com/jira/browse/JBESB-1673?page=all ]
Kevin Conner reassigned JBESB-1673:
-----------------------------------
Assignee: Daniel Bevenius
SOA platform changed upload URL for jBPM
----------------------------------------
Key: JBESB-1673
URL: http://jira.jboss.com/jira/browse/JBESB-1673
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Assigned To: Daniel Bevenius
Fix For: 4.2.1 CP3
The SOA platform has changed the URL used for uploading the process definitions for the
'production' server instance. The consequence of this is that the QSes cannot
deploy their process definitions through the build.xml file.
The mapping should read
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
but now reads
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/app/upload/*</url-pattern>
</servlet-mapping>
The ant task is still using http://localhost:8080/jbpm-console/upload
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:30 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1673) SOA platform changed upload URL for jBPM
[ http://jira.jboss.com/jira/browse/JBESB-1673?page=all ]
Work on JBESB-1673 started by Daniel Bevenius.
SOA platform changed upload URL for jBPM
----------------------------------------
Key: JBESB-1673
URL: http://jira.jboss.com/jira/browse/JBESB-1673
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Assigned To: Daniel Bevenius
Fix For: 4.2.1 CP3
The SOA platform has changed the URL used for uploading the process definitions for the
'production' server instance. The consequence of this is that the QSes cannot
deploy their process definitions through the build.xml file.
The mapping should read
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
but now reads
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/app/upload/*</url-pattern>
</servlet-mapping>
The ant task is still using http://localhost:8080/jbpm-console/upload
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1673) SOA platform changed upload URL for jBPM
[ http://jira.jboss.com/jira/browse/JBESB-1673?page=comments#action_12414021 ]
Daniel Bevenius commented on JBESB-1673:
----------------------------------------
I took a look in the web.xml for the jbpm-console.war see that there are three
login-configs there. Two are commented out. I actually looked and thought that BASIC
authentication was in use, but it is FORM based authentication which is the default.
This has an impact on the upload servlet with regard to authentication. Should the ant
task be able to support both authentication methods or just one of them?
Thanks,
Daniel
SOA platform changed upload URL for jBPM
----------------------------------------
Key: JBESB-1673
URL: http://jira.jboss.com/jira/browse/JBESB-1673
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Assigned To: Daniel Bevenius
Fix For: 4.2.1 CP3
The SOA platform has changed the URL used for uploading the process definitions for the
'production' server instance. The consequence of this is that the QSes cannot
deploy their process definitions through the build.xml file.
The mapping should read
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
but now reads
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/app/upload/*</url-pattern>
</servlet-mapping>
The ant task is still using http://localhost:8080/jbpm-console/upload
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:15 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1673) SOA platform changed upload URL for jBPM
[ http://jira.jboss.com/jira/browse/JBESB-1673?page=comments#action_12414159 ]
Daniel Bevenius commented on JBESB-1673:
----------------------------------------
Ignore my previous comment. I've got it working will all three login-config
authentication options.
I do find the commenting in web.xml a little hard to read though. For example this is what
one of the login-config elements looks like:
<!-- Login configuration option #2 - use basic auth ==>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>jBPM Administration Console</realm-name>
</login-config>
<!== End Login configuration option #2 -->
If you look at this quickly you might think that this login-config is in use, when it is
in fact commented out.
Anyone else think that this is somewhat hard to read, or is it just me? :)
SOA platform changed upload URL for jBPM
----------------------------------------
Key: JBESB-1673
URL: http://jira.jboss.com/jira/browse/JBESB-1673
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Assigned To: Daniel Bevenius
Fix For: 4.2.1 CP3
The SOA platform has changed the URL used for uploading the process definitions for the
'production' server instance. The consequence of this is that the QSes cannot
deploy their process definitions through the build.xml file.
The mapping should read
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
but now reads
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/app/upload/*</url-pattern>
</servlet-mapping>
The ant task is still using http://localhost:8080/jbpm-console/upload
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:43 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1673) SOA platform changed upload URL for jBPM
[ http://jira.jboss.com/jira/browse/JBESB-1673?page=all ]
Daniel Bevenius closed JBESB-1673.
----------------------------------
Resolution: Done
Committed to JBESB_4_2_1_GA_CP with revision: 20163
Notes about testing:
To test this with the SOA platform I took these steps:
1. Downloaded jboss-soa-p.4.2.0
2. Copied jbpm-ant.jar from the JBESB_4_2_1_GA_CP branch to
jboss-soa-p.4.2.0/jboss-as/server/production/deploy/jbpm.esb/jbpm-ant.jar
3. Uncommented the admin user in server/production/conf/props/soa-users.properties
4. In the JBESB_4_2_1_GA_CP branch, updated
samples/quickstarts/conf/quickstarts.properties and set org.jboss.esb.server.home to point
to the downloaded jboss-soa-p.4.2.0 server.
5. In the JBESB_4_2_1_GA_CP branch, updated
samples/quickstarts/conf/quickstarts.properties and set org.jboss.esb.server.config to
production.
6. In the JBESB_4_2_1_GA_CP branch, updated
samples/quickstarts/conf/quickstarts.properties and uncommented jbpm.console.username and
jbpm.console.password. If you don't you will see the following error message:
BUILD FAILED
/opt/jboss/esb/JBESB_4_2_1_GA_CP/product/samples/quickstarts/conf/base-build.xml:266:
Quickstart configuration error:
jBPM username and password must be set in
/opt/jboss/esb/JBESB_4_2_1_GA_CP/product/samples/quickstarts/conf/quickstarts.properties.
The jBPM web console is secured when running in production mode i.e when
org.jboss.esb.server.config=production.
7. Start the server with the production configuration.
8. In the JBESB_4_2_1_GA_CP branch, run 'ant deploy' from one of the
bpm_orchestration quickstart.
9. In the JBESB_4_2_1_GA_CP branch, run 'ant deployProcess' from one of the
bpm_orchestration quickstart.
10. Log into the jbpm-console and verify that the process has been deployed (note that
there was no console output as described in the readme.txt)
To test this with the all configuration just shutdown the server and start with the all
configuration.
To test with BASIC authentication, update jbpm-console.war, web.xml and comment out the
current login-config(FORM based) and uncomment the BASIC based login-config.
To test this with no security configuration simply run the quickstart against the
esbserver in the JBESB_4_2_1_GA_CP branch.
The above steps will not be needed once the changes are in the soa platform. They are just
here in case someone needs/wants to test this before that time.
SOA platform changed upload URL for jBPM
----------------------------------------
Key: JBESB-1673
URL: http://jira.jboss.com/jira/browse/JBESB-1673
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Assigned To: Daniel Bevenius
Fix For: 4.2.1 CP3
The SOA platform has changed the URL used for uploading the process definitions for the
'production' server instance. The consequence of this is that the QSes cannot
deploy their process definitions through the build.xml file.
The mapping should read
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
but now reads
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/app/upload/*</url-pattern>
</servlet-mapping>
The ant task is still using http://localhost:8080/jbpm-console/upload
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:43 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1673) SOA platform changed upload URL for jBPM
[
https://jira.jboss.org/jira/browse/JBESB-1673?page=com.atlassian.jira.plu...
]
Darrin Mison commented on JBESB-1673:
-------------------------------------
Proposed SOA 4.2 TP02 Release Note:
Quick Starts have been updated to bring them in line with the SOA platform upload URL for
jBPM
SOA platform changed upload URL for jBPM
----------------------------------------
Key: JBESB-1673
URL: https://jira.jboss.org/jira/browse/JBESB-1673
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2.1 CP2
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.2.1 CP3
The SOA platform has changed the URL used for uploading the process definitions for the
'production' server instance. The consequence of this is that the QSes cannot
deploy their process definitions through the build.xml file.
The mapping should read
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
but now reads
<servlet-mapping>
<servlet-name>GDP Deployer Servlet</servlet-name>
<url-pattern>/app/upload/*</url-pattern>
</servlet-mapping>
The ant task is still using http://localhost:8080/jbpm-console/upload
--
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
5985
days inactive
6085
days old
7 comments
3 participants
participants (3)
-
Daniel Bevenius (JIRA) -
Darrin Mison (JIRA)
-
Kevin Conner (JIRA)