[JBoss JIRA] Created: (JBPM-1012) The web interface should support multiple logins from a single browser
by Micah Modell (JIRA)
The web interface should support multiple logins from a single browser
----------------------------------------------------------------------
Key: JBPM-1012
URL: http://jira.jboss.com/jira/browse/JBPM-1012
Project: JBoss jBPM
Issue Type: Bug
Components: Web Interface
Affects Versions: jBPM jPDL 3.2.1
Environment: Fedora Core 6 + Firefox 1.5.0.12 + Sun Java 1.5.0.12
Reporter: Micah Modell
Assigned To: Tom Baeyens
If one logs in to the jbpm-console and then opens a new tab or window, they are already logged in in that window. If they then log out, both windows are effectively logged out.
If one opens two tabs on the login screen, logs in on one and then tries to log in on the other, they get the JSP error:
HTTP Status 404 - /jbpm-console/sa/j_security_check
type Status report
message /jbpm-console/sa/j_security_check
description The requested resource (/jbpm-console/sa/j_security_check) is not available.
Apache Tomcat/5.5.17
--
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
17 years, 3 months
[JBoss JIRA] Commented: (JBPM-457) Parent process deployment does not link process-state with subprocess definition
by Tyler Mendenhall (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-457?page=comments#action_12368281 ]
Tyler Mendenhall commented on JBPM-457:
---------------------------------------
This is still an issue in jbpm-jpdl-3.2.1 and causes the same null pointer issue when deploying a process definition that references a subflow in the jbpm console.
I have implemented similar code to resolve the problem in a unit test.
I have a deploy process method:
protected void deployProcess() {
this.dbPersistenceServiceFactory.createSchema();
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
try {
String processDef = this.getProcessDefinitionLocation();
if (processDef==null) throw new IllegalArgumentException("unspecified process name");
ProcessDefinition processDefinition =
ProcessDefinition.parseXmlResource(processDef);
jbpmContext.deployProcessDefinition(processDefinition);
this.deploySubProcesses(processDefinition);
} finally {
jbpmContext.close();
}
}
private void deploySubProcesses(ProcessDefinition superProcessDef){
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
try{
// for each subprocess defined in the map there will be a node definition in the key
// and the process definition xml location in the value
Map subProcessMap = this.getSubProcessMap();
for (Iterator iter = subProcessMap.keySet().iterator(); iter.hasNext();) {
String nodeName = (String) iter.next();
String definitionLocation = (String)subProcessMap.get(nodeName);
if (definitionLocation==null){
throw new IllegalArgumentException("Node:"+nodeName+" is missing the processdefinition.xml location");
}
ProcessDefinition processDefinition = ProcessDefinition.parseXmlResource(definitionLocation);
jbpmContext.deployProcessDefinition(processDefinition);
ProcessState node = (ProcessState)superProcessDef.getNode(nodeName);
if (node!=null){
node.setSubProcessDefinition(processDefinition);
} else {
String superName = superProcessDef.getName();
throw new IllegalArgumentException("Node:"+nodeName+" does not exist in "+superName);
}
}
} finally {
jbpmContext.close();
}
}
However it requires the user to set up the association between process nodes in the parent process definition with individual sub classes.
Hopefully this will help out a bit.
Thanks,
Tyler
> Parent process deployment does not link process-state with subprocess definition
> --------------------------------------------------------------------------------
>
> Key: JBPM-457
> URL: http://jira.jboss.com/jira/browse/JBPM-457
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Reporter: Eduardo Jimenez
> Assigned To: Tom Baeyens
>
> From the ProcessState code:
> Code:
> if (jbpmSession != null) {
>
> // now, we must be able to find the sub-process
> if (subProcessName != null) {
>
> // if the name and the version are specified
> if (subProcessVersion != null) {
>
> try {
> int version = Integer.parseInt(subProcessVersion);
> // select that exact process definition as the subprocess definition
> subProcessDefinition = jbpmSession.getGraphSession().findProcessDefinition(subProcessNam
> e, version);
> } catch (NumberFormatException e) {
> jpdlReader.addWarning("version in process-state was not a number: " + processStateElement.asXML());
> }
>
> } else { // if only the name is specified
> // select the latest version of that process as the subprocess
> // definition
> subProcessDefinition = jbpmSession.getGraphSession().findLatestProcessDefinition(subProces
> sName);
> }
> } else {
> jpdlReader.addWarning("no sub-process name specified in process-state " + processStateElement.asXML());
> }
> }
>
> if there is no session open, it simply won't look for the parent process.
> Now, from the ProcessArchiveDeployer:
> Code:
> public static void deployZipInputStream(ZipInputStream zipInputStream, JbpmSessionFactory jbpmSessio
> nFactory) {
> ProcessDefinition processDefinition = ProcessDefinition.parseParZipInputStream(zipInputStream);
> deployProcessDefinition(processDefinition, jbpmSessionFactory);
> }
>
> It reads the process definition first, then calls deploy, which opens the first jbpmSession!!!. The session must be open first before attempting to deploy!.
> Now, you might say, use the ant task, but the bug is still there:
> Code:
> private void deploy(File file, JbpmSessionFactory jbpmSessionFactory) throws IOException, FileNotFou
> ndException {
> ZipInputStream zipInputStream = new ZipInputStream(new FileInputStream(file));
> ProcessArchiveDeployer.deployZipInputStream(zipInputStream,jbpmSessionFactory);
> }
>
> See, the ant task doens't open a jbpmSession either, so its up to ProcessArchiveDeployer.deployZipInputStream() to do it, which is the same method I'm having an issue with.
> Examining ProcessArchiveDeployer, every way of deploying a process would have the same problem.
--
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
17 years, 3 months
[JBoss JIRA] Created: (JBAS-4527) Cookie and Header information Lost while processing servlets
by Dick Weisinger (JIRA)
Cookie and Header information Lost while processing servlets
------------------------------------------------------------
Key: JBAS-4527
URL: http://jira.jboss.com/jira/browse/JBAS-4527
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.0.GA
Environment: Windows XP; ColdFusion 8
Reporter: Dick Weisinger
I'm seeing different behavior using JSP and CFMs with different versions of JBoss.
At the top of my JSP page I include:
<jsp:include page="../../../app/Application.cfm"/>
Application.cfm tries to set cookie and header data:
<cfheader name="CP" value="NOI DSP COR NID ADMa OPTa OUR NOR">
....
<cfcookie name="MyCookie" value="#NewDataforCookie#" expires="never">
Using JBoss version 4.0.5GA the header information and cookies are correctly set.
But when I deploy the same war file with JBoss 4.2.0, both header and cookie information gets lost.
Can this behavior in version 4.2.0 be modified via a configuration change? Is there a workaround?
------------------------------------------------------------------------------
How to reproduce:
Use JBoss 4.2.0.
Deploy Cold Fusion war on JBoss.
Create a JSP page and put at the top of it:
<jsp:include page="../../../app/Application.cfm"/>
In the referenced Application.cfm file set the following:
<cfheader name="CP" value="NOI DSP COR NID ADMa OPTa OUR NOR">
<cfcookie name="MyCookie" value="ArbitraryData" expires="never">
In your browser, delete your cookies.
Open the JSP file.
Check for the cookie and header information.
For us, it is getting lost.
--
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
17 years, 3 months