Object life cycle in Display method! See pex attachment!Again! ( sorry

from Mr. Mohee Jarada
Email(s):
[email protected]
Budapest - Hungary
[email protected]
Hamburg - Germany
<<ObjectLife.pex>>
Hi,
After importing the attached pex file, you will notice that the object is
died or de-instantiate immediately after the "self.close()" method in
display() method!

Please read the "Servlet 2.2 Specification", chapter 3 - The Servlet Interface, item 3.3 - Servlet Life Cycle

Similar Messages

  • Object life cycle in Display method! See pexattachment!

    from Mr. Mohee Jarada
    Email(s):
    [email protected]
    Budapest - Hungary
    [email protected]
    Hamburg - Germany
    Hi,
    After importing the attached pex file, you will notice that the object is
    died or de-instantiate immediately after the "self.close()" method in
    display() method!
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    from Mr. Mohee Jarada
    Email(s):
    [email protected]
    Budapest - Hungary
    [email protected]
    Hamburg - Germany
    Hi,
    After importing the attached pex file, you will notice that the object is
    died or de-instantiate immediately after the "self.close()" method in
    display() method!
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • Object Life Cycle service Vs. Naming service

    Hi,
    In tuxedo CORBA, I find that Object Life Cycle service & Naming service have something
    similar that the are both used to find object reference, aren't they?Then, I'm
    interested in what make them diferrent in this action(find object reference) and
    why to use one but not the other one?I can't be very clear from the docs.
    Thanks and Regards
    George

    You are correct in that there is some overlap here (ask OMG about
    this...). BEA historically recommended the use of the FactoryFinder
    (BEA did not initially even support the Naming Service) since the whole
    intent of the FactoryFinder was to "provide a naming service for Factory
    objects" (rather than for instances). BEA believed that this was a
    "best practices design pattern" to building scalable applications. Of
    course, there is nothing preventing you from using the Naming Service to
    do exactly the same thing and in fact, many existing applications were
    written using the Naming Service in this way (since most other ORB
    vendors did not implement the FactoryFinder) and as such, BEA added
    support for the Naming Service.
    Hope this helps,
    Robert
    George Lin wrote:
    Hi,
    In tuxedo CORBA, I find that Object Life Cycle service & Naming service have something
    similar that the are both used to find object reference, aren't they?Then, I'm
    interested in what make them diferrent in this action(find object reference) and
    why to use one but not the other one?I can't be very clear from the docs.
    Thanks and Regards
    George

  • Life cycle of a web dynpro callable object

    What is the life cycle of a web dynpro callable object.
    Means when that Web dynpro callble object is used in a GP process which method of that component called first and what is the sequence of the method execution in that.
    Can anyone please explain me.

    Sorry ritu there was one mistake in the above two replies.
    The actual execution of the methods when a callable objects is get executed is as following
    1.component controller's  init() method
    2. interface's  init() method
    3.view's  init() method.
    4.interface's execute() method
    5.view's wDoModifyView() method.
    If you want to change anything on your view according to the change in the interfac's execute method.
    Then you have to do that coding in view's wDoModifyView() method.
    with regards
    shanto aloor.

  • Component life cycle doesn't apply to objects created w/in ActionScript block??

    i don't understand why init() is never called. typically one can initialize variables in the constructor, but since this is mxml, the constructor is automatically created for us and the programmer seems to have no access or override privileges. so what to do?? am i failing to grasp some aspect of the component life cycle process?? how should i go about initializing properties??
    --------------------------- Main.mxml -----------------------------
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
             xmlns:s="library://ns.adobe.com/flex/spark"
             xmlns:mx="library://ns.adobe.com/flex/halo">
      <fx:Script>
        <![CDATA[
          import components.MyComp;
          [Bindable] private var myComp:MyComp = new MyComp();
        ]]>
      </fx:Script>
      <s:Label text="{myComp.myString}"
           horizontalCenter="0" verticalCenter="0"/>
    </s:Application>
    ------------------------ components/MyComp.mxml ---------------------------------------
    <?xml version="1.0" encoding="utf-8"?>
    <s:Group xmlns:fx="http://ns.adobe.com/mxml/2009"
         xmlns:s="library://ns.adobe.com/flex/spark"
         xmlns:mx="library://ns.adobe.com/flex/halo"
         initialize="init()">
      <fx:Script>
        <![CDATA[
          [Bindable] public var myString:String = "hello, world!";
          private function init():void {
            myString = "hello, cruel world!";
        ]]>
      </fx:Script>
    </s:Group>
    NOTE: the code above might seem a little ridiculous, but that's b/c i reduced it down. imagine a baseComponent and derivedComponent where the myString has a default value in the base case and needs to be overridden in the derived case. appreciate any insights and thanks,
    - e

    Thanks Corey and Mike
    I suppose I should have been more aware about when the initialize event gets dispatched -- the concept just wasn't registering for me and I was totally miffed about how to initialize variables on construction.
    Do you have to initialize before the instance is added to the display list?
    Yes, I was mixing both mxml and AS classes and the derived classes had no display objects to attach to the stage (they were mostly classes made to modify run time behavior). You can check out my previous post, which gives the code for where or why this might be needed.
    I ended up initializing mxml class variables during construction in the following way:
    ------------------------------ classes/BaseClass.as ------------------------------
    package classes
      public class BaseClass
        public var myString:String = "hello, world";
        public function BaseClass() {
          init();
        protected function init():void {
          // intentionally left empty 
    ------------------------------ classes/DerivedClassI.mxml ------------------------------
    <?xml version="1.0" encoding="utf-8"?>
    <classes:BaseClass xmlns:fx="http://ns.adobe.com/mxml/2009"
             xmlns:s="library://ns.adobe.com/flex/spark"
             xmlns:mx="library://ns.adobe.com/flex/halo"
             xmlns:classes="classes.*"
             myString="hello, cruel world!">
    </classes:BaseClass>
    ------------------------------ classes/DerivedClassII.mxml ------------------------------
    <?xml version="1.0" encoding="utf-8"?>
    <classes:BaseClass xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/halo"
               xmlns:classes="classes.*">
      <fx:Script>
        <![CDATA[
          override protected function init() : void {
            myString = "hello, cruel cruel world!";
        ]]>
      </fx:Script>
    </classes:BaseClass>
    ------------------------------- Main.mxml ------------------------------
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
             xmlns:s="library://ns.adobe.com/flex/spark"
             xmlns:mx="library://ns.adobe.com/flex/halo">
      <fx:Script>
        <![CDATA[
          import classes.*;
          import mx.collections.ArrayCollection;
          [Bindable] private var list:ArrayCollection = new ArrayCollection( [
            new BaseClass(),
            new DerivedClassI(),
            new DerivedClassII(),
        ]]>
      </fx:Script>
      <s:List dataProvider="{list}" labelField="myString" />
    </s:Application>
    - e

  • What method is called only once in the life cycle?

    Hello,
    What method is called only once in the life cycle of an Entity Bean and Session Bean?
    Is it ejbRemove()?
    Thanks

    hi,
    ejbCreate() and setSessionContext() are called once by the container after the bean instace is created.when the bean instance goes to pool and again return to ready state to handle client requests these methods r never called .only bussiness methods r called.this is in case of stateless session bean.
    in case of stateful session bean, each bean instance is associated with client.so,when new client requests, new bean instance is created and above 2 methods are called. no pool terminology in case of stateful session bean.
    ejbRemove() is called by the container when it is abt to remove bean instance,so it its obvious tht it is called only once.

  • Life cycle method logic

    Hi. I want to ask a few questions about the life cycle methods of Windows Phone App:
    the OnNavigatedTo and OnNavigatedFrom, when is that methods called and what method is called when app goes to background, the screen locks(screen saver) and when app resumes? Thank you.

    Hi,OnNavigatedTo
    this method call after the initialization section.I recommend you load your data asynchronously. OnNavigatedTo is
    one place where you can start the loading.
    OnNavigatedFrom:- This
    method call when application leave the page.OnNavigatedFrom is one place where release application page resources/clean
    memory/clean Back stack entry etc.eg-If application running and you press back button/start button then this method call.
    Don't
    forget to mark the right answer and vote up if helps you.

  • Creator Page Life Cycle Callback Methods

    Hi,
    In JSC Field Guide, we can read that in with JSC 2 we can use Page Life Cycle Callback Methods.
    It 's a good thing but what about compatibility with JSF implementation ?
    Best regards,
    Regis

    Hi,
    Could you please explain what you mean by "compatibility with JSF implementation"?
    Cheers
    Giri

  • Want report to display Sales Life Cycle for Particular Sales Area

    Hi all,
    What are the select-options,parameters and tables for the report sales life cycle for a particular sales area and if possible send me the code for the same.
    Thanks in advance
    Santosh R

    Hi Sandy,
    You would probably be better to post this in Crystal Reports Design forum category.
    You could add a unjion into the data source so that it always returns a dummy row for each category.
    Regards
    Alan

  • Problems with display() method

    import javax.swing.*;
    import java.awt.*;
    import java.awt.event.*;
    public class lifeCycle extends JApplet implements ActionListener
         JLabel messageInit = new JLabel("init ");
         JLabel messageStart = new JLabel("start ");
         JLabel messageDisplay = new JLabel("display ");
         JLabel messageAction = new JLabel("action ");
         JLabel messageStop = new JLabel("stop ");
         JLabel messageDestroy = new JLabel("destroy ");
         JButton pushButton = new JButton("Hit me!");
         int countInit, countStart, countDisplay, countAction, countStop, countDestroy;
              public void init(){
                  Container con = getContentPane();
                  con.setLayout (new FlowLayout());
                  ++countInit;
                  con.add(messageInit);
                  con.add(messageStart);
                  con.add(messageDisplay);
                  con.add(messageAction);
                  con.add(messageStop);
                  con.add(messageDestroy);
                  con.add(pushButton);
                  pressButton.addActionListener(this);
                  display();
                  showStatus("complete");
              public void start(){
              ++countStart;
              display();
              showStatus("complete");
              public void stop(){
                  ++countStop;
                  display();
                  showStatus("complete");
              public void destroy(){
                  ++countDestroy;
                  display();
                  showStatus("complete");
              public void actionPerformed(ActionEvent e){
                  Object source = e.getSource();
                  if(source == pushButton){
                   ++countAction;
                   display();
                   showStatus("complete");
    }Just trying to learn the basics of life cycles in the swing applet. The display() method is where we're having problems, I'm getting the "cannot resolve symbol" message. I was just wondering what I'm doing wrong here. Thanks!
    Kate

    hi,
    I'm not sure what your applet is suppose to do but i've made some changes. I've moved your Container object declaration out of the "init()", and instead of "pressButton" I changed it to "pushButton" and "display()" to "con.setVisible(true)".
    hope this will resolve your issue. Here is the edited code:
    import javax.swing.*;
    import java.awt.*;
    import java.awt.event.*;
    public class lifeCycle extends JApplet implements ActionListener
         JLabel messageInit = new JLabel("init ");
         JLabel messageStart = new JLabel("start ");
         JLabel messageDisplay = new JLabel("display ");
         JLabel messageAction = new JLabel("action ");
         JLabel messageStop = new JLabel("stop ");
         JLabel messageDestroy = new JLabel("destroy ");
         JButton pushButton = new JButton("Hit me!");
         int countInit, countStart, countDisplay, countAction, countStop, countDestroy;
            Container con = getContentPane(); // Moved from init() to here
              public void init(){             
                  con.setLayout (new FlowLayout());
                  ++countInit;
                  con.add(messageInit);
                  con.add(messageStart);
                  con.add(messageDisplay);
                  con.add(messageAction);
                  con.add(messageStop);
                  con.add(messageDestroy);
                  con.add(pushButton);
                  pushButton.addActionListener(this);
                        // edited from "pressButton" to "pushButton"
                  con.setVisible(true); //used the Container object you created
                                              // instead of "display()";
                  showStatus("complete");
              public void start(){
              ++countStart;
              con.setVisible(true);   //used the Container object you created
                                            // instead of "display()";
              showStatus("complete");
              public void stop(){
                  ++countStop;
                  con.setVisible(true);   //used the Container object you created
                                                // instead of "display()";
                  showStatus("complete");
              public void destroy(){
                  ++countDestroy;
                  con.setVisible(true);  //used the Container object you created
                                                // instead of "display()";
                  showStatus("complete");
              public void actionPerformed(ActionEvent e){
                  Object source = e.getSource();
                  if(source == pushButton){
                   ++countAction;
                   con.setVisible(true);  //used the Container object you created
                                                   // instead of "display()";
                   showStatus("complete");
    }

  • Re: [SunONE-JATO] Re: Using an object to store and display data

    Personally, I think there is little or no value to creating a "domain"
    object that itself relies on a JATO QueryModel internally, but hides that
    fact and requires use of BeanAdapterModel.
    It would be more appropriate (and much less work, and more scalable) to just
    derive a QueryModel subclass and add the domain-specific behavior to the
    model. In other words, what's the point of creating an object that hides
    JATO inside it when you're running in JATO to begin with? Now if the domain
    object were doing plain JDBC, and thus trying to be JATO independent, that
    would be different. However, you could still implement the Model interface
    on the object (or use BeanAdapterModel) to integrate it seamlessly with the
    View tier.
    Todd
    ----- Original Message -----
    From: "grschroeder" <grschroeder@y...>
    Sent: Wednesday, July 31, 2002 12:00 PM
    Subject: [SunONE-JATO] Re: Using an object to store and display data
    Craig,
    I think it all finally makes sense. First, your assumption is
    correct regarding the process flow. The ViewBean will interact with
    a custom Javabean which will then in turn interact with a SQL Model
    to access the database. So now let me make sure I understand what I
    need to do. Basically the custom Javabean will have a method to get
    the SQLModel. I would then invoke the setValue method on the
    SQLModel and call the appropriate execute method( e.g.,
    executeUpdate, etc. ) just like I would do from a ViewBean. Does
    this sound correct?
    Thanks,
    Greg
    --- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
    wrote:
    Greg,
    see below...
    grschroeder wrote:
    Thanks for the help Craig. I looked at the sample code that makes
    use of the BeanAdapterModel. Basically it looks like it allows a
    view to interact with a bean the same way it would interact with
    any
    other model. That part I think I understand.
    This is correct.
    The part I'm a little
    unclear on still is how to interface this BeanAdapterModel( which
    is
    a very basic model ) that I now have with a query model toactually
    interact with the database.
    Not sure what you mean by "interface this BeanAdapterModel ... witha
    query model". Does this mean that you have a ViewBean the interactswith
    a custom JavaBean via the BeanAdpterModel wrapper, and from the
    JavaBean you are interacting with the SQL Model?
    So it looks like this: ViewBean > BeanAdapterModel(Custom JavaBean)
    SQL Model > RDBMS
    That's what I am reading anyway. Please explain this to me.
    Would I need to make direct JDBC calls
    from my custom model instead of letting JATO dynamically create
    the
    calls for me?
    If my assumptions above are correct, then the custom JavaBean cansimply
    use the SQL Model in exactly the same manner as the ViewBean,otherwise,
    if no SQL Model is involved, then yes, you need to handle JDBCdirectly,
    which is fine, if you do it "right" (connection pooling, result set
    handling, etc.).
    Thanks,
    Greg
    --- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
    wrote:
    I think the best approach would be to treat your Domain Objects
    (DO) as
    the Database (the enterprise tier) from JATO's perspective. You
    could
    create custom models that interface with our DO's and then the
    JATO
    Views could easily bind to the custom DO models just like anyother
    model. This should eliminate the need for pushing data/objectsfrom
    >
    view
    to model to database.
    There is a JATO class called BeanAdapterModel that might be just
    what
    you need, however, I am not experienced with using it. Maybe
    someone
    else on my team or in the community could better explain how to
    use
    >
    this
    class.
    craig
    grschroeder wrote:
    Venki,
    Thanks for the response. Actually, I'm not sure if I can answer
    all
    of your questions because those are some of the same questions
    that
    we're trying to answer ourselves. Basically, what we're trying
    to
    >do
    is incorporate our domain object model into the JATO framework.
    My
    thinking was that one way we could accomplish this was by
    storing
    >a
    Javabean object in the HTTPSession to represent an object in the
    domain model, and that the Viewbean and JATO Model could get and
    set
    data from there. If you have a better suggestion of how to
    accomplish this, I'm definitely open to hearing it.
    Thanks,
    Greg
    --- In SunONE-JATO@y..., Venki <heyvenki@y...> wrote:
    OK grschroeder , first let me get this straight:
    0. Are you going to pass this object to the model, or are u
    going
    >
    to pass the session object to the model?
    1. Is there any specific reason for this approach you are
    taking?
    2. Will there be a notification from the object u havementioned
    >to
    have the model persist the data?
    3. What about the reverse case, when the model refreshes the
    data,
    how are you going to refresh you object?
    4. The JavaBean Object that u are talking about, is it your own
    object or is it implementation of an existing JATO interface?
    ~Venki
    grschroeder wrote:I'm fairly new to JATO, but I think I now
    have
    >a
    basic understanding
    of how Viewbeans and Models interact. However, I want to
    incorporate
    the use of a Javabean object that will be stored in the HTTP
    session
    and will act as the connection between the Viewbean and Model
    instead
    of having the Viewbean and Model interact directly with each
    other.
    Basically I would like to have the Model set data in the object
    stored in the session so that the Viewbean can pull it out to
    display
    it. And vice versa, once the user modifies the data and is
    ready
    >
    to
    persist it, I would like to have the Viewbean set data in the
    object
    stored in the session so that the Model can pull it out to
    store
    >it
    in the database. I'm not sure what the best approach would be
    to
    accomplish this. Any help you could give would be greatly
    appreciated.
    Thanks,
    Greg
    To download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    Service.
    Venki
    IT Solutions
    #6, Pycrofts Garden Road, Nugambakkam, Chennai - 600 006
    91-44-4925740(Home) 91-44-8212877(Work)
    * Luck is what happens when Preparation meets Opportunity.
    To download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    >To download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    To download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp

    Personally, I think there is little or no value to creating a "domain"
    object that itself relies on a JATO QueryModel internally, but hides that
    fact and requires use of BeanAdapterModel.
    It would be more appropriate (and much less work, and more scalable) to just
    derive a QueryModel subclass and add the domain-specific behavior to the
    model. In other words, what's the point of creating an object that hides
    JATO inside it when you're running in JATO to begin with? Now if the domain
    object were doing plain JDBC, and thus trying to be JATO independent, that
    would be different. However, you could still implement the Model interface
    on the object (or use BeanAdapterModel) to integrate it seamlessly with the
    View tier.
    Todd
    ----- Original Message -----
    From: "grschroeder" <grschroeder@y...>
    Sent: Wednesday, July 31, 2002 12:00 PM
    Subject: [SunONE-JATO] Re: Using an object to store and display data
    Craig,
    I think it all finally makes sense. First, your assumption is
    correct regarding the process flow. The ViewBean will interact with
    a custom Javabean which will then in turn interact with a SQL Model
    to access the database. So now let me make sure I understand what I
    need to do. Basically the custom Javabean will have a method to get
    the SQLModel. I would then invoke the setValue method on the
    SQLModel and call the appropriate execute method( e.g.,
    executeUpdate, etc. ) just like I would do from a ViewBean. Does
    this sound correct?
    Thanks,
    Greg
    --- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
    wrote:
    Greg,
    see below...
    grschroeder wrote:
    Thanks for the help Craig. I looked at the sample code that makes
    use of the BeanAdapterModel. Basically it looks like it allows a
    view to interact with a bean the same way it would interact with
    any
    other model. That part I think I understand.
    This is correct.
    The part I'm a little
    unclear on still is how to interface this BeanAdapterModel( which
    is
    a very basic model ) that I now have with a query model toactually
    interact with the database.
    Not sure what you mean by "interface this BeanAdapterModel ... witha
    query model". Does this mean that you have a ViewBean the interactswith
    a custom JavaBean via the BeanAdpterModel wrapper, and from the
    JavaBean you are interacting with the SQL Model?
    So it looks like this: ViewBean > BeanAdapterModel(Custom JavaBean)
    SQL Model > RDBMS
    That's what I am reading anyway. Please explain this to me.
    Would I need to make direct JDBC calls
    from my custom model instead of letting JATO dynamically create
    the
    calls for me?
    If my assumptions above are correct, then the custom JavaBean cansimply
    use the SQL Model in exactly the same manner as the ViewBean,otherwise,
    if no SQL Model is involved, then yes, you need to handle JDBCdirectly,
    which is fine, if you do it "right" (connection pooling, result set
    handling, etc.).
    Thanks,
    Greg
    --- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
    wrote:
    I think the best approach would be to treat your Domain Objects
    (DO) as
    the Database (the enterprise tier) from JATO's perspective. You
    could
    create custom models that interface with our DO's and then the
    JATO
    Views could easily bind to the custom DO models just like anyother
    model. This should eliminate the need for pushing data/objectsfrom
    >
    view
    to model to database.
    There is a JATO class called BeanAdapterModel that might be just
    what
    you need, however, I am not experienced with using it. Maybe
    someone
    else on my team or in the community could better explain how to
    use
    >
    this
    class.
    craig
    grschroeder wrote:
    Venki,
    Thanks for the response. Actually, I'm not sure if I can answer
    all
    of your questions because those are some of the same questions
    that
    we're trying to answer ourselves. Basically, what we're trying
    to
    >do
    is incorporate our domain object model into the JATO framework.
    My
    thinking was that one way we could accomplish this was by
    storing
    >a
    Javabean object in the HTTPSession to represent an object in the
    domain model, and that the Viewbean and JATO Model could get and
    set
    data from there. If you have a better suggestion of how to
    accomplish this, I'm definitely open to hearing it.
    Thanks,
    Greg
    --- In SunONE-JATO@y..., Venki <heyvenki@y...> wrote:
    OK grschroeder , first let me get this straight:
    0. Are you going to pass this object to the model, or are u
    going
    >
    to pass the session object to the model?
    1. Is there any specific reason for this approach you are
    taking?
    2. Will there be a notification from the object u havementioned
    >to
    have the model persist the data?
    3. What about the reverse case, when the model refreshes the
    data,
    how are you going to refresh you object?
    4. The JavaBean Object that u are talking about, is it your own
    object or is it implementation of an existing JATO interface?
    ~Venki
    grschroeder wrote:I'm fairly new to JATO, but I think I now
    have
    >a
    basic understanding
    of how Viewbeans and Models interact. However, I want to
    incorporate
    the use of a Javabean object that will be stored in the HTTP
    session
    and will act as the connection between the Viewbean and Model
    instead
    of having the Viewbean and Model interact directly with each
    other.
    Basically I would like to have the Model set data in the object
    stored in the session so that the Viewbean can pull it out to
    display
    it. And vice versa, once the user modifies the data and is
    ready
    >
    to
    persist it, I would like to have the Viewbean set data in the
    object
    stored in the session so that the Model can pull it out to
    store
    >it
    in the database. I'm not sure what the best approach would be
    to
    accomplish this. Any help you could give would be greatly
    appreciated.
    Thanks,
    Greg
    To download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    Service.
    Venki
    IT Solutions
    #6, Pycrofts Garden Road, Nugambakkam, Chennai - 600 006
    91-44-4925740(Home) 91-44-8212877(Work)
    * Luck is what happens when Preparation meets Opportunity.
    To download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    >To download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    To download the latest version of JATO, please visit:
    http://www.sun.com/software/download/developer/5102.html
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp

  • Re: Inherited display method

    Dave
    You need to make an explicit call to super.Display() in the Display() method of your subclasses. Alternatively, you can delete the Display() method in your subclasses if there is no additional functionality there.
    You seem to be getting a bit confused over inheritance and overriding. If you override a method in a subclass (ie have a method with the same name and parameters), you will lose the functionality of the superclass's method - unless you explicitly call the super method. If you DON'T override it, you will inherit it automatically!
    If you write a good framework for your application, you will rarely need to have a Display() method in your bottom level classes, as all required functionality will be inherited. Please let me know if you would like some tips on the development of such a framework (or if I haven't made any sense).
    Regards
    Sam Keall
    [email protected] on 27/07/98 17:03:00
    To: [email protected]
    cc: (bcc: Sam Keall/GB/ABNAMRO/NL)
    Subject: Inherited display method
    I am trying to modify the display method in a custom window super class.
    Within my application, the user should be able to hit the F3 key to
    exit. I have coded it in a display method on a particular window and it
    works. However, when I attempt to move the code to the parent window
    class (so that I don't need to repeat the code for every window
    subclass) it doesn't work. It seems that the display method isn't being
    inherited (even though the books say that they are). After having
    modified my display method in the window super class, I created a
    subclass based on the super class. When I opened the display method for
    the subclass, only the default code appeared, not the custom code that I
    had created for the superclass.
    Any assistance would be appreciated. It seems to defeat the purpose of
    OO if I can't create a custom display method in a super class and have
    it inherited by the subclass.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    hi,
    Well as cbacher has mentioned, if your Thread is running and you call the start method a InvalidThreadStateException will be raised, what you can do is like this, you can have ur class implement runnable as this will also you to call the run method multiple times using the start().
    Your run code could have some kind of a check to see if the external event has occured, if not it should continue doing the process else it should finish the execution of the run method, thereafter you could call the start method again to restart the thread, that way you will not be essentially creating a new Thread object( you are calling start on an existing object). Hope this was useful.
    cheerz
    ynkrish

  • Where in the MIDlet life-cycle should I create multiple forms with LWUIT ?

    Hi all,
    I must create two LWUIT forms in my application. Where should I create the two forms ? I created the first form in the startApp life-cycle method , and when I tried to create also the second form in the startApp method then there is a NullPointerException raised when running the application !
    So where , or how , should I create the second form ?
    Thank you very much indeed
    Edited by: andrianiaina on May 20, 2011 1:59 AM

    I think the problem here is that Arlhoolie wants all of the different TEBs to behave as if they were part of a single interaction that submits only ONE result to the quiz.  Using multiple TEBs in Captivate means that you have multiple scored objects and therefore multiple results being submitted to the quiz.
    If you want a single Success or Failure result submitted to the quiz based on the results from multiple interactive objects then there really is no simple way to do it.  But you could try using the Infosemantics Interactive Master widget to combine all the TEBs as slave objects that report to the Master Widget, which then reports a single score to the quiz based on the results from the slave objects.
    You can learn more about the Master widget here:
    http://www.infosemantics.com.au/adobe-captivate-widgets/interactive-master
    http://www.infosemantics.com.au/interactivemaster/help
    You can download a free trial version of the widget here:
    http://www.infosemantics.com.au/adobe-captivate-widgets/download-free-trial-widgets
    One caveat you should be aware of is that this widget is not HTML5 compatible.

  • Regarding SLCM (Student Life Cycle Management)

    Hi
    does any one working on Student Life Cycle Management(SLCM)
    can any one pls let me know what are the function modules present in the predefined business package and how to know what are the predefined functonalites given by sap.
    when i test the predefined Iviews i get an error for some of iview as student object id not found.
    can any one pls let me know about this
    Bye

    Ok Fine
    I have some points to share thise issue with u
    first thing is , iam using wrong application for the requirement.
    and even i use wrong apps some thing result should be show, as i said the error i got
    we raised an sap Oss for this, they provided the solution as stating that we are using the apps which are specific to the advisor but not for the students specially.
    So if u want to use those apps for student purpose we need to get that student object and pass in our application.
    for this purpose we need an abaper help who is well versed in the coding part.
    just modify the code of required application where u fetch the object id (BY Coding) in ithe intialization method,
    then the appication works fine
    this is the solution i got and all my apps are working fine now.
    Thanxs
    sandeep

  • Jsf 1s phase of life cycle how knows ths components of the jsp with jsf tag

    i wish to know how faces servlet knows the jsp s view components while creaTI NG component tree at first request to input jsp which may have jsf tags.in the first phase faces servlet doesnot know input jsp with jsf tags what componnets it has. it is actually atthe response send or forward time which is the final phase when the tag ge executed and output is sent to client.i did understandin jsf life cycle in 1 st phase component tree is created at first request in 1 st phase .

    Hi,
    though a FacesContext holds the values used by a request, it doesn't mean it lives for as long as the request. The best explanation I found is from the JavaDocs
    release
    public abstract void release()
    +Release any resources associated with this FacesContext instance. Faces implementations may choose to pool instances in the associated FacesContextFactory to avoid repeated object creation and garbage collection. After release() is called on a FacesContext instance (until the FacesContext instance has been recycled by the implementation for re-use), calling any other methods will cause an IllegalStateException to be thrown.+
    The implementation must call setCurrentInstance(javax.faces.context.FacesContext) passing null to remove the association between this thread and this dead FacesContext instance.
    Throws:
    java.lang.IllegalStateException - if this method is called after this instance has been released
    Frank

Maybe you are looking for