topic Re: Could not lookup beanmanager in jndi in weblogic in Alfresco Archive

Could not lookup beanmanager in jndi in weblogic

vinothkumar_j2e — Tue, 04 Jun 2013 15:05:13 GMT

hi,I have conditional flow with expression ${ instanceVaraiable.getCanSkipPool()} returns boolean.instanceVariable (JAVA BEAN with get & set methods) is set during the process flow. When control reaches the conditional flow , i get below error and instance is not getting created . What needs

Re: Could not lookup beanmanager in jndi in weblogic

frederikherema1 — Tue, 04 Jun 2013 15:20:16 GMT

The "instanceVariable" is serialized, stored in the DB and deserialized again when needed. Possibly the context the bean needs is not serialized and will be de-serialized as "null" or something like that.

Either make a custom variable type (extending SerializableType) that initialized the correct context for the "instanceVariable" POJO before passing it on the the engine. For an example, see org.activiti.engine.impl.variable.JPAEntityVariableType. Another option is to make the POJO smart enough to initialize the right context when it's used for the first time and still store it as you do now.

Re: Could not lookup beanmanager in jndi in weblogic

vinothkumar_j2e — Tue, 04 Jun 2013 16:50:33 GMT

instanceVariable class is already implementing java.io.Serializable interface. Can you please elaborate what you mean by "initialize the right context when it's used for the first time" ? Problem is with the attributes inside the InstanceVariable classes are not initilized is that the problem?

I am able to access the "instanceVariable" in next serviceTask . Issue is seems to be with expression set in the conditional flow. If i set ${false} , no issues instance get created. Why is the conditional expression is not loading the instancevariable

Re: Could not lookup beanmanager in jndi in weblogic

frederikherema1 — Thu, 06 Jun 2013 12:30:15 GMT

Is the "instance variable" set on the execution/process when the conditional flow is reached? If not, this is the issue.

I didn't see you were using activiti-CDI, so ignore the comments above.

Re: Could not lookup beanmanager in jndi in weblogic

vinothkumar_j2e — Thu, 06 Jun 2013 14:08:25 GMT

I removed all the engine table and re-created engine again . Not getting above error anymore. Looks like i was accessing wrong variable or Serializable data was corrupt. Thanks everyone.