Hi all,
I have a question about getting the bean object from the session in OE BPM. The code I use to get the bean is:
session.getAttribute("bean");
According to this article of the knowledgebase, that's correct: http://knowledgebase.progress.com/articles/Article/P173990
But it always returns null. Does someone know a possible cause, or how to solve this?
Regards,
Harrie.
Hi Harrie,
Can you confirm how exactly are you trying this usecase...
Is this using a Form? or Using a CustomJSP?
Regards,
Jawahar.
It's a custom JSP file.
OK.
Can you please confirm, the following tags exists in your .jsp file
<jsp:useBean id="bizManage" class="com.savvion.sbm.bizmanage.api.BizManageBean" scope="session"></jsp:useBean>
<jsp:useBean id="bean" class="com.savvion.BizSolo.beans.Bean" scope="session"></jsp:useBean>
<jsp:useBean id="factoryBean" class="com.savvion.BizSolo.beans.EPFactoryBean" scope="session"></jsp:useBean>
<jsp:useBean id="bizSite" class="com.savvion.sbm.bpmportal.bizsite.api.BizSiteBean" scope="session"></jsp:useBean>
Regards,
Jawahar
Hi Jawahar,
I added the lines, but now it returns an object with an empty dataslots map. Which is expected behaviour if bean is null while using useBean. (useBean instantiates an empty bean if the session attribute is null)
Do you have another suggestion?
Regards,
Harrie.
Hi Jawahar,
I added the lines, but now it returns an object with an empty dataslots map. Which is expected behaviour if bean is null while using useBean. (useBean instantiates an empty bean if the session attribute is null)
Do you have another suggestion?
Regards,
Harrie.
Flag this post as spam/abuse.
Hi Jawahar,
Thanks for your answer. But that is not really the use case. I was maybe unclear with the custom JSP page. The JSP page is not attached to a activity. But is an independent JSP page within my BPM project. It is included using an iframe in the process' user interface.
Is there a way to get this bean in this context?
Regards,
Harrie.
Hi Jawahar,
Thanks for your answer. But that is not really the use case. I was maybe unclear with the custom JSP page. The JSP page is not attached to a activity. But is an independent JSP page within my BPM project. It is included using an iframe in the process' user interface.
Is there a way to get this bean in this context?
Regards,
Harrie.
Flag this post as spam/abuse.
Hi Jahawar,
I already did that, like you suggested at May 19th too. There are no dataslots filled inside the bean. If I print all elements of bean.getDataSlots() with this code:
Map dataSlotMap = bean.getDataSlots();
System.out.println("==== START CONTENT DATASLOT MAP ====");
for(Object key : dataSlotMap.keySet()) {
System.out.println(key + ": " + dataSlotMap.get(key));
}
System.out.println("==== END CONTENT DATASLOT MAP ====");
The result is:
09:02:06,359 INFO [STDOUT] ==== START CONTENT DATASLOT MAP ====
09:02:06,360 INFO [STDOUT] ==== END CONTENT DATASLOT MAP ====
So, clearly no elements inside it. The workstep which this JSP is included in has definitely dataslots attached.
Regards,
Harrie.
Hi Jahawar,
I already did that, like you suggested at May 19th too. There are no dataslots filled inside the bean. If I print all elements of bean.getDataSlots() with this code:
Map dataSlotMap = bean.getDataSlots();
System.out.println("==== START CONTENT DATASLOT MAP ====");
for(Object key : dataSlotMap.keySet()) {
System.out.println(key + ": " + dataSlotMap.get(key));
}
System.out.println("==== END CONTENT DATASLOT MAP ====");
The result is:
09:02:06,359 INFO [STDOUT] ==== START CONTENT DATASLOT MAP ====
09:02:06,360 INFO [STDOUT] ==== END CONTENT DATASLOT MAP ====
So, clearly no elements inside it. The workstep which this JSP is included in has definitely dataslots attached.
Regards,
Harrie.
Flag this post as spam/abuse.
I am not using the custom jsp IN a custom jsp. I'm using the custom jsp in a form which is generated by the form designer. So using that code is not possible for me. Since it is impossible to use hottags (<%=%>) in the properties pane. So we used javascript to kinda "hack" the src attribute. That's a js file, where we cannot use the jsp hottags.