Problem with Forte Express, on priorities of the ORDERBYconstraints .

Question

In my businessModel I've got 2 Tables :
Table MACHINE : - MACHINE_ID, MACHINE_NAME, MACHINE_BRAND, MACHINE_MODEL,
USERS_ID (which is a foreign key of the table USERS.)
Table ACTIVITY : - ACTIVITY_ID, ACTIVITY_NAME.
In my applicationModel I've got a businessClass : MACHINE -> OutlineField.
In this Outlinefield, I display : MACHINE_NAME, MACHINE_BRAND,
MACHINE_MODEL, ACTIVITY_NAME (Which is a joint with the table ACTIVITY, made
by
Express).
So, the MACHINEQuery contains 6 constants : ATTR_MACHINE_ID,
ATTR_MACHINE_NAME, ATTR_MACHINE_BRAND, ATTR_MACHINE_MODEL, ATTR_USERS_ID,
ATTR_ACTIVITY
With your help, last time I've been able to order data by every kinds of
field.
But, when I put several ORDERBY restrictions in the restricUserSearch(),the
priority is not respected any more.
Here I want to order data first by ACTIVITY and then by MACHINE_NAME.
So I've writen this code :
in the RestrictUserSearch(searchCriteria:BusinessQuery) event of MACHINE :
/* ******** Here I Order MACHINE DATA by activity *********************** */
myActivityQ : ACTIVITYQuery = new() ;
myActivityQ.AddConstraint(
attr = ACTIVITYQuery.ATTR_ACTIVITY_NAME,
operation = ConstraintOperation.OP_ORDERBY);
//Set fields to retrieve from USERS table
myActivityQ.AddAttr(attr = ACTIVITYQuery.ATTR_ACTIVITY_NAME ) ;
searchCriteria.AddAttr(
attr = MACHINEQuery.ATTR_ACTIVITY
query = myUsersQ);
/* ******** Here I order MACHINE by MACHINE_NAME *********************** */
searchCriteria.AddConstraint(
attr = MACHINEQuery.ATTR_MACHINE_NAME,
operation = ConstraintOperation.OP_ORDERBY);
The result of this code is that DATA are ordered only by MACHINE_NAME. I
don't understand why .
Any suggestions would be greatly appreciated,
Thanks for your help. :o)
Sébastien MARIE
E-MAIL : [email protected]
TEL : [phone]

Answer 1

I suppose you don't use qualified parameters.
http://download-uk.oracle.com/docs/cd/B14099_13/portal.1014/b14135/pdg_java_adv.htm#CBBGHHDC
7.2.3.3.2 URL Parameters
"The portlet developer must ensure that the portlet:
properly qualifies its own parameters when they are built into links and forms.
leaves unchanged any parameters that do not belong to it.
The following API call transforms an unqualified parameter name into a qualified parameter name:
HttpPortletRendererUtil.portletParameter(HttpServletRequest request, String param);
HttpPortletRendererUtil is in the package oracle.portal.provider.v2.render.http.
For example:
qualParamQ = HttpPortletRendererUtil.portletParameter(r, "q");
To fetch the value of a portlet parameter from the incoming request, you can use the following API:
Note:
The API converts the parameter name into the qualified parameter name before fetching the value from the incoming request. Hence, you need not perform this step.
PortletRenderRequest.getQualifiedParameter(String name)"