Hide Forgot
Date of First Response: 2008-12-15 08:24:01 project_key: SOA We make changes to the jbpm consoles authentication method and look and feel in 3.2.2. These changes need to be included in jbpm 3.3. 3.3 is maven based, ideally we would prefer this as a profile but we may have to hardwire them into the SOA jbpm branch.
Link: Added: This issue is related to JBPM-1832
There is a related jbpm issue but we need to push ahead with this as they are deferring
At the moment we overlay console code for jbpm, esb etc. We do this to give it a common look and feel and give the consoles a common authentication method. You can see the changes at http://anonsvn.jboss.org/repos/soa/trunk/src/consoles/jbpm/
Link: Added: This issue is a dependency of JBPM-1920
I've added a -Psoa switch to the maven build of the jsf-console. Please see https://svn.jboss.org/repos/jbpm/projects/jsf-console/trunk and verify everything is migrated correctly. Here's what I included: <overlay> <id>soa-webapp-overlay</id> <groupId>org.jbpm.jbpm3</groupId> <artifactId>soa-webapp</artifactId> <includes> <include>JBossLogo.jpg</include> <include>login.jsp</include> <include>WEB-INF/web.xml</include> <include>WEB-INF/jboss-web.xml</include> </includes> </overlay>
Future overlays should go into the soa module of the JSF build within jbpm3.
The overlays have been added to the jbpm3 build in trunk: You can build a customized distribution, incudling the soa-p overlays like this: mvn -Pdistro,soa clean package
We still need to include the 3.2.8 branch version of the console.
This has been overtaken by events: jBPM 3.3 will not be included in the SOA platform; jBPM 3.2.10 includes the relevant changes.
Release Notes Docs Status: Added: Not Required Labels: Added: rn-not-needed