You're welcome, Ramesh
A followup:
2) You will also need the selection binding to bind the currently
selected object from the list of choices.
3) There is no concept of dev/prod mode during build (compile) time,
the bits are same.
Debug features (ie, XRay, debug options panel), remote debugging,
rapid turnaround of resources, and class reloading is turn on by the
default ant command.
To turn off:
a) debug features and remote debugging, set the ant property
debug.off property to false.
b) rapid turnaround of resource, set the aw.search.path ant
property to "" or set the env var ARIBA_AW_SEARCH_PATH to ""
c) class reloading, set the aw.reload ant property to false or set
the env var ARIBA_AWRELOAD to false.
-Kingsley
On Feb 25, 6:12 pm, Ramesh Mandaleeka <
ramesh.mandale...@gmail.com>
wrote:
> The pointers you shared are very helpful. Thank you Kingsley.
> Regards,
> Ramesh
>
> On Wed, Feb 25, 2009 at 9:09 PM, <
ariba...@gmail.com> wrote:
>
> > Hi Ramesh,
>
> > 1) I am assuming you are asking how to do this using lower level AW
> > core (not MetaUI), and you are fetching the DB values yourself.
> > We already have a component to render the HTML select (AWPopup). It
> > takes in a list binding and an item binding.
> > So here’s an example:
>
> > In YourComponent.awl
> > <AWPopup list=”$myValues” item=”$currentValue”>
> > $currentValue.label
> > </AWPopu>
>
> > In YourComponent.java
> > public Object currentValue;
> > public List myValues;
> > public List myValues ()
> > {
> > If (myValues == null) {
> > myValues = <populate from DB>
> > }
> > return myValues;
> > }
>
> > You can find the complete reference to AWPopup in the Demo app under
> > the Documentation tab.
> > (Note: The .awl files parse into an AWTemplate instances, not compiled
> > into a classes)
>
> > 2)
http://aribaweb.org/resource/hero/FullStack.gifroughly shows the