You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by sqlien <sm...@yahoo.fr> on 2007/07/17 14:25:17 UTC

Hi all,

where is defined the screen that the variable ${detailScreen} point to ?   

${detailScreen} is invoked in the file :
ecommerce/widget/CatalogScreen.xml

Thanks in advance
-- 
View this message in context: http://www.nabble.com/%3Cinclude-screen-name%3D%22%24%7BdetailScreen%7D%22-%3E-tf4096557.html#a11648299
Sent from the OFBiz - User mailing list archive at Nabble.com.


Re:

Posted by Amine AZZI <ba...@gmail.com>.
some parameters are put as context variable in the web.xml, try to take a
look at the web.xml corresponding to your module

2007/7/17, sqlien <sm...@yahoo.fr>:
>
>
> but, I have take look at the file category.bsh, and i find this code:
> category = delegator.findByPrimaryKeyCache("ProductCategory",
> UtilMisc.toMap("productCategoryId", productCategoryId));
> if (category != null) {
>     if (category.get("detailScreen") != null)
>         detailScreen = category.getString("detailScreen");
>          ...............
>          ..............
>          context.put("detailScreen", detailScreen);
>
> ** category.getString("detailScreen") return null because field
> detailScreen
> is empty in the table ProductCategory. so ${detailScreen}==null in
> <include-screen name="${detailScreen}"/>.
>
>
>
> pankaj savita wrote:
> >
> > Hi,
> >     Just look at the flow in the screens.  For "category-include" screen
> > "detailScreen" parameter has been set in the context in the
> > category.bshwhich is invoked in the screen "category".  The "category"
> > screen includes
> > screen "category-include".
> >     For "product" the "detailScreen" parameter is set in context in the
> > product.bsh which is invoked in the "product" screen itself.
> >
> > On 7/17/07, sqlien <sm...@yahoo.fr> wrote:
> >>
> >>
> >> Hi all,
> >>
> >> where is defined the screen that the variable ${detailScreen} point to
> ?
> >>
> >> ${detailScreen} is invoked in the file :
> >> ecommerce/widget/CatalogScreen.xml
> >>
> >> Thanks in advance
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/%3Cinclude-screen-name%3D%22%24%7BdetailScreen%7D%22-%3E-tf4096557.html#a11648299
> >> Sent from the OFBiz - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Thanks & Regards
> >
> > Pankaj Savita
> > HotWax Media Inc.
> > pankaj.savita@hotwaxmedia.com
> > http://www.hotwaxmedia.com
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/%3Cinclude-screen-name%3D%22%24%7BdetailScreen%7D%22-%3E-tf4096557.html#a11650719
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>
>

Re:

Posted by sqlien <sm...@yahoo.fr>.
but, I have take look at the file category.bsh, and i find this code:
category = delegator.findByPrimaryKeyCache("ProductCategory",
UtilMisc.toMap("productCategoryId", productCategoryId));
if (category != null) {
    if (category.get("detailScreen") != null) 
        detailScreen = category.getString("detailScreen");
         ...............
         ..............
         context.put("detailScreen", detailScreen);

** category.getString("detailScreen") return null because field detailScreen
is empty in the table ProductCategory. so ${detailScreen}==null in 
<include-screen name="${detailScreen}"/>.



pankaj savita wrote:
> 
> Hi,
>     Just look at the flow in the screens.  For "category-include" screen
> "detailScreen" parameter has been set in the context in the
> category.bshwhich is invoked in the screen "category".  The "category"
> screen includes
> screen "category-include".
>     For "product" the "detailScreen" parameter is set in context in the
> product.bsh which is invoked in the "product" screen itself.
> 
> On 7/17/07, sqlien <sm...@yahoo.fr> wrote:
>>
>>
>> Hi all,
>>
>> where is defined the screen that the variable ${detailScreen} point to ?
>>
>> ${detailScreen} is invoked in the file :
>> ecommerce/widget/CatalogScreen.xml
>>
>> Thanks in advance
>> --
>> View this message in context:
>> http://www.nabble.com/%3Cinclude-screen-name%3D%22%24%7BdetailScreen%7D%22-%3E-tf4096557.html#a11648299
>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> Thanks & Regards
> 
> Pankaj Savita
> HotWax Media Inc.
> pankaj.savita@hotwaxmedia.com
> http://www.hotwaxmedia.com
> 
> 

-- 
View this message in context: http://www.nabble.com/%3Cinclude-screen-name%3D%22%24%7BdetailScreen%7D%22-%3E-tf4096557.html#a11650719
Sent from the OFBiz - User mailing list archive at Nabble.com.


Re:

Posted by pankaj savita <pa...@gmail.com>.
Hi,
    Just look at the flow in the screens.  For "category-include" screen
"detailScreen" parameter has been set in the context in the
category.bshwhich is invoked in the screen "category".  The "category"
screen includes
screen "category-include".
    For "product" the "detailScreen" parameter is set in context in the
product.bsh which is invoked in the "product" screen itself.

On 7/17/07, sqlien <sm...@yahoo.fr> wrote:
>
>
> Hi all,
>
> where is defined the screen that the variable ${detailScreen} point to ?
>
> ${detailScreen} is invoked in the file :
> ecommerce/widget/CatalogScreen.xml
>
> Thanks in advance
> --
> View this message in context:
> http://www.nabble.com/%3Cinclude-screen-name%3D%22%24%7BdetailScreen%7D%22-%3E-tf4096557.html#a11648299
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>
>


-- 
Thanks & Regards

Pankaj Savita
HotWax Media Inc.
pankaj.savita@hotwaxmedia.com
http://www.hotwaxmedia.com