EOImpl's prepareForDML called twice when PK is updated.

Hi,
I update the DeptNo to an unique number. The prepareForDML is called twice. Why does this happen?
thanks,
Buks

Similar Messages

ItemFocusOut called twice when you are using datagrid

Have you ever encountered itemFocusOut called twice when you
are using datagrid. I use this event to check the text that has
been entered.
Also when I use regex expressions
if((event.itemRenderer as TextInput).text.search(new
RegExp(/.*\..*\./)) != -1){
in the itemFocusOut method and someone enters
234.34.234
I get an error
TypeError: Error #1009: Cannot access a property or method of
a null object reference.
at
mx.controls::DataGrid/destroyItemEditor()[C:\autobuild\3.2.0\frameworks\projects\framewor k\src\mx\controls\DataGrid.as:4000]
at
mx.controls::DataGrid/itemEditorItemEditEndHandler()[C:\autobuild\3.2.0\frameworks\projec ts\framework\src\mx\controls\DataGrid.as:4897]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at
mx.core::UIComponent/dispatchEvent()[C:\autobuild\3.2.0\frameworks\projects\framework\src \mx\core\UIComponent.as:9298]
at
mx.controls::DataGrid/endEdit()[C:\autobuild\3.2.0\frameworks\projects\framework\src\mx\c ontrols\DataGrid.as:4041]
at
mx.controls::DataGrid/mouseDownHandler()[C:\autobuild\3.2.0\frameworks\projects\framework \src\mx\controls\DataGrid.as:4296]
Could some be so kind as shed some light on this
situation

I've worked around the error. I had something to do with the
fact that the event was being twice and I worked my handling code
around to avoid the error. However the problem with the event still
remains. I think it is because the data it in the grid is being
refreshed intentially after the code in the itemFocusOut is called
that is cause the second event to fire.

HT1379 Recived msg 'panic(cpu 0 caller 0xffffff8000659241):' when trying to update system on my notebook

Have powered off unit and powered it on.. the above msg will come up stating "unable to find driver for this platform:
This occored when trying to update system Schreen when gray and stayed that way until powered off then on..

Hi Revamax, did you ever solve this problem? My MBP has just done exactly the same after trying to install a software update.

PrepareForDML method called twice

Have implemented a typical scenario (search - add - edit jspx pages).
Within one application module, one view object with dynamically created where criterion is used for searching, and another view object fetching at most one row is used for inserting/updating. The second view object is based on a join of an updatable entity (that has as primary key trigger-generated sequence number) and several referenced readable entities that bring descriptions of the codes of the updatable entity. Have implemented descriptions as output fields in the jspx, settign partialTriggers to the id of the code-field of the updatable entity having autoSubmit=true. Have concentrated business validation logic within the prepareForDML() of the updatable entity implementation.
Under normal conditions, it works fine.
Under heavy system load in production, or testing with ADF State Management enabled at work environment, I observe the prepareForDML() called twice instead of once.
Thus, the first time the insert is commited, the second time the validation rollback, and at last the whole transaction is rollbacked.
When I commented-out all the fields that bring descriptions and set all autoSubmit=false, prepareForDML() was called once.
However, my problem is that I have to bring the descriptions, that result from pop-up windows so that the end-user can see them after selecting sthg on his/er screen.
Why is prepareForDML() called twice, and how can I avoid this?

(2) Can't change the second trigger-assigned field from DBSequence to simply Number since the Entity Object Editor hides the tab Sequence to declare the sequence from which to get this field's value after insert.
Please see section "6.6.3.8 Trigger-Assigned Primary Key Values from a Database Sequence" of the ADF Developer's Guide for Forms/4GL Developers on the ADF Learning Center at http://www.oracle.com/technology/products/adf/learnadf.html for more information on this. The "Sequence" tab doesn't have any runtime behavior influence. The sequence number is not assigned by ADFBC, it is assigned by your trigger. ADFBC only worries about:
1) Providing a temporary unique negative key so that new detail rows can have a temporary foreign key value to point at until the transaction commits
2) Refreshing the entity object's primary key value from the database-trigger assigned sequence number (however, we really don't know how the trigger populated the value) Theoretically, it may or may not have used a database sequence to assign the number. It would work just the same at the ADFBC level)
3) Refreshing the temporary negative foreign key values in newly-created detail rows for new, composed details of the new composing master row with the definitive primary key value.
So, you should safely be able to change this to a Number, with its Refresh after Insert property set.
(3) Create() on entity implementation was always called once at page load, unexpectedly prepareForDML() always carried on two consequtive rows (either the new row to insert twice or the query's first row retrieved to update and afterwards the new row to insert) having State Management enabled.
If create() is being called only once, then next you should check the value of the "operation" flag that is passed to prepareForDML() to understand if the method is being called for DML_INSERT or DML_UPDATE. Perhaps somehow an existing row is being inadvertently updated so one of the calls to prepareForDML() might be an update? I don't understand how prepareForDML() could fire twice for two new entity objects if the entity object's create() method is only called once. If you have a testcase that illustrates this, please report it to Worldwide Support via Metalink so they can triage and file a bug for you on it.
(4) Swapping selectInputText components with SelectOneChoice, thus avoiding the partial page rendering, I managed prepareForDML() to function logically so that to have only one row to insert, but again since I have validation code in my entity implementation that throws JBO-exceptions, another problem occured. The first time the end-user receives an exception (e.g. invalid Tax Number), the second time he/she corrects it, the created row instance at prepareForDML() doesn't get updated with the new valid Tax Number, but continues to hold the old value at second run. To remind that if insert is successful the navigation moves on to the update page, otherwise it remains at the same (navigation outcome is null).
Are you absolutely sure in this case that a second new row is not getting created?

WDDOMODIFY is getting called twice.

Hi,
I am facing a problem where wddomodify is getting called twice when I am selecting a value from a drop down. While for other drop downs on the same view WDDOMODIFY is not even getting called. I would appreciate, if anyone of you can provide any info regarding the same.
Thanks,
Vishesh

DATA LO_ND_IMPORTING_CREATE TYPE REF TO IF_WD_CONTEXT_NODE.
    DATA LO_EL_IMPORTING_CREATE TYPE REF TO IF_WD_CONTEXT_ELEMENT.
    DATA LS_IMPORTING_CREATE TYPE WD_THIS->ELEMENT_IMPORTING_CREATE.
    DATA LV_DOC_TYPE TYPE WD_THIS->ELEMENT_IMPORTING_CREATE-DOC_TYPE.
navigate from <CONTEXT> to <IMPORTING_CREATE> via lead selection
    LO_ND_IMPORTING_CREATE = WD_CONTEXT->GET_CHILD_NODE( NAME = WD_THIS->WDCTX_IMPORTING_CREATE ).
get element via lead selection
    LO_EL_IMPORTING_CREATE = LO_ND_IMPORTING_CREATE->GET_ELEMENT( ).
get single attribute
    LO_EL_IMPORTING_CREATE->GET_ATTRIBUTE(
      EXPORTING
        NAME = `DOC_TYPE`
      IMPORTING
        VALUE = LV_DOC_TYPE ).
     DATA LO_ND_IF_EDITABILITY TYPE REF TO IF_WD_CONTEXT_NODE.
     DATA LO_EL_IF_EDITABILITY TYPE REF TO IF_WD_CONTEXT_ELEMENT.
     DATA LV_EDIT_SUB_TYPE     TYPE WD_THIS->ELEMENT_IF_EDITABILITY-EDIT_SUB_TYPE.
     DATA LV_EDIT_PARENT       TYPE WD_THIS->ELEMENT_IF_EDITABILITY-EDIT_PARENT.
     DATA LV_DROPDOWN          TYPE REF TO CL_WD_DROPDOWN_BY_KEY.
     DATA LV_INPUTFIELD        TYPE REF TO CL_WD_INPUT_FIELD .
   navigate from <CONTEXT> to <IF_EDITABILITY> via lead selection
     LO_ND_IF_EDITABILITY = WD_CONTEXT->GET_CHILD_NODE( NAME = WD_THIS->WDCTX_IF_EDITABILITY ).
   get element via lead selection
     LO_EL_IF_EDITABILITY = LO_ND_IF_EDITABILITY->GET_ELEMENT( ).
     LO_EL_IF_EDITABILITY->GET_ATTRIBUTE( EXPORTING   NAME = `EDIT_SUB_TYPE`
                                           IMPORTING VALUE = LV_EDIT_SUB_TYPE ).
     LO_EL_IF_EDITABILITY->GET_ATTRIBUTE( EXPORTING   NAME = `EDIT_PARENT`
                                           IMPORTING VALUE = LV_EDIT_PARENT ).
      DATA LO_ND_FUNCTIONALITY TYPE REF TO IF_WD_CONTEXT_NODE.
      DATA LO_EL_FUNCTIONALITY TYPE REF TO IF_WD_CONTEXT_ELEMENT.
      DATA LS_FUNCTIONALITY TYPE WD_THIS->ELEMENT_FUNCTIONALITY.
      DATA LV_OPTION_CHANGED TYPE WD_THIS->ELEMENT_FUNCTIONALITY-OPTION_CHANGED.
      DATA LV_OPTION_SELECTED TYPE WD_THIS->ELEMENT_FUNCTIONALITY-OPTION_SELECTED.
    navigate from <CONTEXT> to <FUNCTIONALITY> via lead selection
      LO_ND_FUNCTIONALITY = WD_CONTEXT->GET_CHILD_NODE( NAME = WD_THIS->WDCTX_FUNCTIONALITY ).
    get element via lead selection
      LO_EL_FUNCTIONALITY = LO_ND_FUNCTIONALITY->GET_ELEMENT( ).
    get single attribute
      LO_EL_FUNCTIONALITY->GET_ATTRIBUTE(
        EXPORTING
          NAME = `OPTION_CHANGED`
        IMPORTING
          VALUE = LV_OPTION_CHANGED ).
      LO_EL_FUNCTIONALITY->GET_ATTRIBUTE(
        EXPORTING
          NAME = `OPTION_SELECTED`
        IMPORTING
          VALUE = LV_OPTION_SELECTED ).
DATA LO_EL_CONTEXT TYPE REF TO IF_WD_CONTEXT_ELEMENT.
DATA LS_CONTEXT TYPE WD_THIS->ELEMENT_CONTEXT.
DATA LV_SET_STATE TYPE WD_THIS->ELEMENT_CONTEXT-SET_STATE.
get element via lead selection
LO_EL_CONTEXT = WD_CONTEXT->GET_ELEMENT( ).
get single attribute
LO_EL_CONTEXT->GET_ATTRIBUTE(
    EXPORTING
      NAME = `SET_STATE`
    IMPORTING
      VALUE = LV_SET_STATE ).
IF LV_SET_STATE = 'X'.
IF LV_DOC_TYPE = 'ABC' AND LV_EDIT_SUB_TYPE IS INITIAL.
     LO_EL_IF_EDITABILITY->SET_ATTRIBUTE(
          NAME = `EDIT_SUB_TYPE`
          VALUE = 'X' ).
      LV_DROPDOWN ?= VIEW->GET_ELEMENT('DRPDWN_SUBTYPE_CHANGE').
      CALL METHOD LV_DROPDOWN->SET_STATE
        EXPORTING
          VALUE = 01
      ELSE.
      LO_EL_IF_EDITABILITY->SET_ATTRIBUTE(
          NAME = `EDIT_SUB_TYPE`
          VALUE = '' ).
      LV_DROPDOWN ?= VIEW->GET_ELEMENT('DRPDWN_SUBTYPE_CHANGE').
      CALL METHOD LV_DROPDOWN->SET_STATE
        EXPORTING
          VALUE = 00
    ENDIF.
    IF LV_EDIT_PARENT IS INITIAL AND
                ( LV_DOC_TYPE = '123' OR LV_DOC_TYPE = 'qwerty').
      LO_EL_IF_EDITABILITY->SET_ATTRIBUTE(
          NAME = `EDIT_PARENT`
          VALUE = 'X' ).
      LV_DROPDOWN ?= VIEW->GET_ELEMENT('DRPDWN_PARENT_CHNG_DOCTYPE').
      CALL METHOD LV_DROPDOWN->SET_STATE
        EXPORTING
          VALUE = 01
      LV_INPUTFIELD ?= VIEW->GET_ELEMENT('IF_PARENT_CHNG_DOCNUM').
      CALL METHOD LV_INPUTFIELD->SET_STATE
        EXPORTING
          VALUE = 01
      ELSE.
      LO_EL_IF_EDITABILITY->SET_ATTRIBUTE(
          NAME = `EDIT_PARENT`
          VALUE = '' ).
      LV_DROPDOWN ?= VIEW->GET_ELEMENT('DRPDWN_PARENT_CHNG_DOCTYPE').
      CALL METHOD LV_DROPDOWN->SET_STATE
        EXPORTING
          VALUE = 00
      LV_INPUTFIELD ?= VIEW->GET_ELEMENT('IF_PARENT_CHNG_DOCNUM').
      CALL METHOD LV_INPUTFIELD->SET_STATE
        EXPORTING
          VALUE = 00
    ENDIF.
     LO_EL_CONTEXT->SET_ATTRIBUTE(     NAME = `SET_STATE`
                                      VALUE =   ' ' ).
ENDIF.
LO_EL_CONTEXT->GET_ATTRIBUTE(
    EXPORTING
      NAME = `SET_STATE`
    IMPORTING
      VALUE = LV_SET_STATE ).
      IF LV_OPTION_CHANGED = 'X' AND LV_OPTION_SELECTED = 'C'.
          DATA LO_ND_ZGGL TYPE REF TO IF_WD_CONTEXT_NODE.
          DATA LO_EL_ZGGL TYPE REF TO IF_WD_CONTEXT_ELEMENT.
        navigate from <CONTEXT> to <ZGGL_RICEFTOOL> via lead selection
          LO_ND_ZGGL = WD_CONTEXT->GET_CHILD_NODE( NAME = WD_THIS->WDCTX_ZGGL).
          LO_ND_ZGGL->INVALIDATE( ).
        get element via lead selection
          LO_EL_ZGGL = LO_ND_ZGGL->GET_ELEMENT( ).
          LO_ND_IMPORTING_CREATE->INVALIDATE( ).
          LO_EL_IMPORTING_CREATE = LO_ND_IMPORTING_CREATE->GET_ELEMENT( ).
          LO_EL_IMPORTING_CREATE->SET_ATTRIBUTE(      NAME = `VISIBILITY_GROUP`
                                                     VALUE =   '2' ).
          LO_EL_IMPORTING_CREATE->SET_ATTRIBUTE(      NAME = `VISIBILITY_TABLE`
                                                     VALUE =   '1' ).
          LO_EL_IMPORTING_CREATE->SET_ATTRIBUTE(
               NAME = `ACTION_RDBTN`
               VALUE = 'C' ).
          LO_EL_IF_EDITABILITY->SET_ATTRIBUTE(
              NAME = `EDIT_CREATE`
              VALUE = ' ' ).
         LO_EL_IF_EDITABILITY->SET_ATTRIBUTE(
              NAME = `EDIT_DISPLAY`
              VALUE = 'X' ).
         LO_EL_FUNCTIONALITY->SET_ATTRIBUTE(    NAME = `OPTION_CHANGED`
                                                 VALUE = ' ' ).
        ENDIF.

LoginModule login method called twice on unsuccessful logins

This is a cross post of a topic in the Application Server - General forum. The login and abort methods of our JAAS LoginModule are called twice when authentication is unsuccessful. It is called once on successful logins. This is problematic as it puts the user closer to locking the user's network account. We have confirmed that this is an issue, perhaps resolvable, with the container itself - version 10.1.2.0.2. I recreated the problem with a simple web application and using Frank Nimphius' simple JAAS login module. Here's a snippet from the redirected out:
07/07/07 15:37:01 Enter login
07/07/07 15:37:01 Performing user authentication for user
07/07/07 15:37:01 User is not authenticated - Password must be "welcome"
07/07/07 15:37:01 Enter abort
07/07/07 15:37:01 Authentication Failed
07/07/07 15:37:01 Authentication: FAILED.
07/07/07 15:37:01 JAAS-OC4J: Authentication failure for user: user
07/07/07 15:37:01 Enter login
07/07/07 15:37:01 Performing user authentication for user
07/07/07 15:37:01 User is not authenticated - Password must be "welcome"
07/07/07 15:37:01 Enter abort
07/07/07 15:37:01 Authentication Failed
07/07/07 15:37:01 Authentication: FAILED.
07/07/07 15:37:01 JAAS-OC4J: Authentication failure for user: user
Has anyone else experienced this problem and found a workaround or setting to prevent this behavior?

Follow-up: I ran the sample application and LoginModule using oc4j 10.1.3.2 and it appears that the problem is resolved. As moving to 10.1.3.2 might not be an option is there some patch to 10.1.2 to correct the issue?

POWL-Feeder-Class is called twice by class CL_POWL_MODEL

Hi all,
we are running sap erecruiting and there's an application called "dashboard" that uses the POWL-Technologie.
Now we noticed, that our feeder class is called twice when one particular "query" is called via dashboard:
once within method "handle_refresh_async" and twice within method "refresh_current" (methods of class "CL_POWL_MODEL").
As we don't want to have double runtime, does anyone know why the feeder class is called twice and how to prevent it?
Thanks in advance
Regards
CHRIS

Hi Kris,
thanks for your reply.
I think the forum message you suggested does not apply to me. They talk about a refresh after an action.
In my case once the dashboard-query is requested by the user the feeder-class is called twice before the result is displayed.
Regards
CHRIS

Page flow actions are called twice from each UI's action=...

Odd observation: my nothing fancy login / pw change / logged in / jsps and pageflow are having the actions in the .jpf called twice for each jsp form action=.
What can cause this?
For example: the login jsp form action=loginAction, the corresponding method in the .jpf is called twice when the user clicks the login button on the login UI. The same behavior is observed for all the other actions in this page flow too.
This has been a real problem for the pw change UI. Until I figured this out, pw change always returned invalid pw due to the second call to the action. :))
tnx curt

I have narrowed it down even more. What is happening is that you select the first item in the list it throws a validation error. I found this by adding and inline message. The weird thing is that if you select any other item in the list but the first everything flows as normal.
This is a list of dates bound to a date type column in a database.
Any Idea's why selecting the first item in a list would throw the validation message?

ADF selectonechoice valuebinding called twice

Does anyone have any idea why the valuebinding method of an ADF SelectOneChoice component would be called twice? I have one drop down with values and when I select something in that drop down the valuebinding for the second drop down is called twice, when it should only be called once. Any help would be appreciated.

Hi,
what is the refresh setting of the region binding in the page's PageDef file? Put a print statement to the task flow initializer to verify the region is executed twice
Frank

TS1702 I am getting an unknown error when trying to update or purchase apps from the apps store. This is new, after the new OS update. Help

Hi, I get this unknown error message, twice when trying to update or purchase new apps. It was working fine, then just stopped. I changed my password, but that hasn't worked. Help!

Sign out of your account, restart the iPad and then sign in again.
1. Settings>Store>Apple ID.
2. Tap your ID and sign out.
3. Restart the iPad by holding down on the sleep button until the red slider appears and then slide to shut off.
4. To power up hold the sleep button until the Apple logo appears and let go of the button.
Go back to Settings>Store>Sign in and then try to download again.

JavaScript Function Calls it is called twice only when add the component

Hi,
I am developing a SAP Design Studio Extension and I noticed that when I add the component on Application, SAP Design Studio calls the JavaScript SDK Functions twice only when I drag and drop the component.
I found out about this just put an alert message in which JavaScript Function (init, beforeUpdate and afterUpdate).
Is it ok to work this way?
I am really curious if anyone else has come across this issue.
Thank you,
Fabio Almeida

Hi Fabio,
Yes, there does appear to be an issue with SDK component functions being called twice. Mike Howles has implemented a workaround in this Toolbar example code. Refer to the code in the this.init function at the end.
Regards,
Mustafa.

Database call fired twice when using actionListener in dataTable

Hi all,
I have a question regarding the request bean lifecylce in the current use case (using Sun JSF 1.2)
I have a managed bean in request scope that contains an ArrayList which is used as the data provider in a dataTable on a faces page.
The bean contains an init() method to populate the ArrayList using a database call.
The dataTable also contains a column with a commandLink that calls a method via actionListener inside the managed bean to delete the current row.
When I click the link the action gets called and deletes the row from the database. I also reload the data from the database and assign it to my ArrayList.
However, the init Method is also called before the action is executed. So the database call is fired twice when hitting the link:
- First time in the init() method of the bean
- Second time in the actionListener method when reloading the data
I can not remove the call from the actionListener, because the data has not deleted yet.
Question:*
How can I make sure the database call is fired once only? (and also making sure the ArrayList is populated appropriate)
Maybe I am doing something wrong here? Thanks in advance for any help.
Maik
This is the request scope bean:
public class UserBean implements Serializable {
    private List all;
    private Long userId = null;
    @PostConstruct
    public void init() {
        if(all == null) {
            new ArrayList();
            loadUserList();
     * Constructor
    public UserBean() {
        super();
     * @return the userId
    public Long getUserId() {
        return userId;
     * @param userId
     *            the userId to set
    public void setUserId(Long userId) {
        this.userId = userId;
     * @param all
     *            the all to set
    public void setAll(List all) {
        this.all = all;
    public List getAll() throws GeneralModelException {
        return all;
    public void loadUserList() {
        EntityManager em = Contexts.getEntityManager();
        Query q = em.createNamedQuery("user.findAll");
        all = q.getResultList();
    public void deleteAction(ActionEvent ae) {
        EntityManager em = Contexts.getEntityManager();
        Query q = em.createNamedQuery("user.byId");
        q.setParameter("id", userId);
        try {
            User user = (User) q.getSingleResult();
            if (user != null) {
                em.remove(user);
                loadUserList();
        } catch (NoResultException e) {
            // TODO
}

No, I do not call the init() method.
Basically the init() is called before the deleteAction() so the ArrayList still contains the old value, unless a second database call is triggered after the entity has been deleted.
Maybe I am missing something here...
See also here (JSF 1.2 RI - Bean Instantiation and Annotation)
[http://weblogs.java.net/blog/jhook/archive/2007/05/jsf_12_ri_backi.html]
Here is the init() call stack trace
Daemon Thread [http-8080-2] (Suspended (breakpoint at line 32 in UserBean))
     UserBean.init() line: 32
     NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
     NativeMethodAccessorImpl.invoke(Object, Object[]) line: not available
     DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not available
     Method.invoke(Object, Object...) line: not available
     DefaultAnnotationProcessor.postConstruct(Object) line: 79
     Tomcat6InjectionProvider.invokePostConstruct(Object) line: 118
     ManagedBeanBuilder(BeanBuilder).invokePostConstruct(Object, InjectionProvider) line: 223
     ManagedBeanBuilder(BeanBuilder).build(InjectionProvider, FacesContext) line: 108
     BeanManager.createAndPush(String, BeanBuilder, ELUtils$Scope, FacesContext) line: 368
     BeanManager.create(String, FacesContext) line: 230
     ManagedBeanELResolver.getValue(ELContext, Object, Object) line: 88
     FacesCompositeELResolver(CompositeELResolver).getValue(ELContext, Object, Object) line: 53
     FacesCompositeELResolver.getValue(ELContext, Object, Object) line: 72
     AstIdentifier.getValue(EvaluationContext) line: 61
     AstValue.getTarget(EvaluationContext) line: 59
     AstValue.setValue(EvaluationContext, Object) line: 129
     ValueExpressionImpl.setValue(ELContext, Object) line: 249
     JspValueExpression.setValue(ELContext, Object) line: 85
     RestoreViewPhase.doPerComponentActions(FacesContext, UIComponent) line: 240
     RestoreViewPhase.doPerComponentActions(FacesContext, UIComponent) line: 245
     RestoreViewPhase.doPerComponentActions(FacesContext, UIComponent) line: 245
     RestoreViewPhase.execute(FacesContext) line: 195
     RestoreViewPhase(Phase).doPhase(FacesContext, Lifecycle, ListIterator<PhaseListener>) line: 100
     RestoreViewPhase.doPhase(FacesContext, Lifecycle, ListIterator<PhaseListener>) line: 104
     LifecycleImpl.execute(FacesContext) line: 118
     FacesServlet.service(ServletRequest, ServletResponse) line: 265

Is this a Bug?: FocusListener called twice

Hey all,
Im having this problem since realease 1.4.2_04.
Folks, try this code:
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class FocusTest {
    public static void main(String[] args) {
        JFrame frame = new JFrame("Focus test");
        final JTextField field1 = new JTextField("Test1");
        final JTextField field2 = new JTextField("Test2");
        field1.addFocusListener(new FocusAdapter(){
            public void focusGained(FocusEvent e){}
            public void focusLost(FocusEvent e){
                if( !e.isTemporary() ){
                    System.out.println("ID: " + e.getID());
                    JOptionPane.showMessageDialog(null, "Focus lost in 1");
                    field1.requestFocus();
        frame.getContentPane().add(field1, BorderLayout.WEST);
        frame.getContentPane().add(field2, BorderLayout.CENTER);
        frame.setDefaultCloseOperation(JFrame.DISPOSE_ON_CLOSE);
        frame.setBounds(0,0,200,300);
        frame.show();
} The problem is: when TF1 looses its focus, and is validated, then i force the focus to keep on TF1 by calling TF1.requestFocus(), somehow the event focusLsot is called twice for my TF.
If i do not requestFocus() it work but I must force the focus on TF1.
Im going nuts. Does anyonw apear to have this problems?? In old realeses, the same code work perfect. until 1.4.2 beta.
Tks
Bruno

Hello all!
I found out that somehow JDialog with requestfocus after, fires twice the lostFocus event. I dont know why. I opened a bug report so they can figure it out why is happaning.
Tks folks!
Bruno

HELP!!! why derived class's function be called twice?

I am a newbie to java.
Recently I encounter a problem.
I run the below file,the output is:
output begin
B.f called !!!!
A.A called
B.f called !!!!
B.B called
output end-
My Question is :
why B's f() be called twice?
(In C++, A.f() will be called one time!)
class A
A()
f();
System.out.println("A.A called");
int f()
System.out.println("A.f called !!!");
return 123;
class B extends A
B()
f();
System.out.println("B.B called");
int f()
System.out.println("B.f called !!!!");
return 456;
public class Demo
public static void main(String args[])
B bobj = new B();
-----------------------------------

Hi,jsalonen:
In the following code, variable i cann't be initialized properly.
    class A
         int i=0;
        A()
            f();
            System.out.println("A.A called");
            System.out.println("i="+i);
        int f()
            i=11;
            System.out.println("A.f called !!!");
            return 123;
    class B extends A
         int j;
        B()
            f();
            System.out.println("B.B called");
            System.out.println("j="+j);
            System.out.println("i="+i);
        int f()
            j=12;
            System.out.println("B.f called !!!!");
            return 456;
    public class Demo
        public static void main(String args[])
            B bobj = new B();
output begin
B.f called !!!!
A.A called
i=0 // BAD here
B.f called !!!!
B.B called
j=12
i=0 // BAD here
output end -
Although the question can be solved! I am still confused: why Java do this? when A's constructor call f(), B is still incomplete!!
Java is a good language,but I dislike it on this
Regards.
Sunway

Method CreateChildren in ApplicationControllBar class called twice after setting dock=true

Hi during creating of a custom ApplicationControllBar
component in ActionScript I probably found a (nasty) bug?!
package net.neijman.julia.jaContainers
import mx.containers.ApplicationControlBar;
public class JAApplicationControlBar2 extends
ApplicationControlBar
public function JAApplicationControlBar2(): void
this.dock = true;
super();
override protected function createChildren(): void
trace("CREATECHILDREN EXECUTED");
When I am using my simple custom component in my application:
<jaContainer:JAApplicationControlBar2 />
The trace message trace("CREATECHILDREN EXECUTED"); is
executed twice (meaning CreateChildren is called twice BUT ONLY
AFTER SETTING dock = true (see constructor). When setting dock =
false CreateChildren is executed once. I want to build a framework
on the standard components (depending heavily on the
CreateChildren-method).
In other words, creating dynamic components in the docked
ApplicationControlBar in the method CreateChildren results in a
double placement in the DisplayList.
Has anyone has a clue what's going wrong here? (my
workarround for now is to start the createChildren method with
removeAllChildren();)
Thanks Tom Neijman

Interesting. I would file it as a bug here:
http://bugs.adobe.com/jira/secure/Dashboard.jspa
And then see what happens. If it's not a bug, you'll probably
get a decent reason why this occurs in the bug notes.
matt horn
flex docs

EOImpl's prepareForDML called twice when PK is updated.

Similar Messages

Maybe you are looking for