LoggedInRegularUser and Where clause

pixerp

In the sample CRM application, I have added attribute Test1 to BO RegularUser.

As admin (operation-Testmode), I change my login details and store 142 in attribute Test1.

In a process (invoked from a ContactNote form), the first rule is :

PICK FROM Atable WHERE Atable.channel CONTAINS 'LoggedInRegularUser.test1'

=> no records listed

If I change the rule to :

PICK FROM Atable WHERE Atable.channel CONTAINS '142'

=> 1 record is displayed (as expected !)

What am I doing wrong ?

I'm running V3 build 1035.

tford

pixerp,

I did a sample bsv & this does not work in V4.1 build 1159 either.

FYI -- I did not use CRM for the sample since nothing that you showed in your notes really referred to the CRM application. I testing just running the queries from Standard menu & not from a form.

Tom

tford

PS -- I sent a sample bsv over to support to review.

Tom

pixerp

Tom,

Thanks for validating the issue. Waiting for our support friend, now.

Regards,
Ernest

aware_support

I haven't checked the BSV yet, but the rule should be:

PICK FROM Atable WHERE Atable.channel CONTAINS LoggedInRegularUser.test1

Note that there are no apostrophes around LoggedInRegularUser

tford

Oops -- I missed that.

It works just fine without the apostrophes.

No need to test that BSV.

Tom

pixerp

Well, after further testing, the problem shows up when the BO points to an external DB table (mysql):

PICK FROM BOexternal WHERE BOexternal.Attrib1 CONTAINS BOinternal.AttribA
-> java.lang.NullPointerException ( see below full msg)

whereas if BOinternal.AttribA is replaced with '999' (ie. a constant) the query will display the expected result.

It seems like the attribute BOinternal.AttribA is not resolved before querying the external DB. I have also tried ThisBOinternal.AttribA and LoggedInRegularUser.AttribA with the same error.

Tomcat error log:
java.lang.NullPointerException
at com.bas.webapp.actions.QueryAction.a(Unknown Source)
at com.bas.webapp.actions.QueryAction.M(Unknown Source)
at com.bas.webapp.actions.QueryAction.U(Unknown Source)
at com.bas.webapp.actions.QueryAction.doExecute(Unknown Source)
at com.cc.framework.adapter.struts.ActionUtil.execute(Unknown Source)
at com.cc.framework.adapter.struts.FWAction.execute(Unknown Source)
at com.cc.framework.adapter.struts.FWAction.execute(Unknown Source)
at com.cc.framework.adapter.struts.RequestProcessorUtil.processAction(Unknown Source)
at com.cc.framework.adapter.struts.FWRequestProcessor.processActionPerform(Unknown Source)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
at com.cc.framework.adapter.struts.FWRequestProcessor.processForwardConfig(Unknown Source)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198-)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118-)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Unknown Source)

aware_support

What is your build number?

pixerp

About AwareIM in Config tool says 1035
but AwareIM/bin/build.number says 1036 ...

Not too sure.

christopherb

Pixerp,
You are far behind on the current build of AwareIM. This mat constitute any troubles you may be having. You can view the current change log here....

http://www.awareim.com/changelog/

Good Luck,

pixerp

Thanks for your remark - Christopher.

But (as always) after a quick install of build 1159, I can tell that the problem is still there.

I noticed in the changelog of build 1036, that a bug was addressed relating to "Usage of values resolved dynamically in CONTAINS/STARTS WITH expressions in queries on non-Aware IM tables could cause problems".

For our support friend :
I'd like to stay with version 3 for the moment. Could I get the latest V3 build to test ?

Thanks in advance.