IPhone : webViewDidFinishLoad being triggered multiple times

In my app I have a web viewer and in my code I do a 'loadRequest' to populate it. I'm trying to determine when the page finishes loading using the 'webViewDidFinishLoad' delegate. For most pages like yahoo, or google, the delegate is only called once when the load is finished. For abcnew.com, the delegate gets triggered 3 times. I do a NSLog() every time my delegate code is entered, so I'm just counting my log entries from the console window.
I'm wondering why 'webViewDidFinishLoad' is getting called 3 times for abcnews.com but only once for most other sites I try.
Thanks,
Tony

It probably does. I was just trying different pages to see what would happen. That is when I noticed abc.com triggers the delegate three times, yet google.com and yahoo.com only once. I guess I'll have to do some more research to better understand what webViewDidFinishLoad is really doing.

Similar Messages

Email being sent multiple times when actions are triggered after creating an incident. Anyone has a resolution?

Email being sent multiple times (3 times) when actions are triggered after creating an incident.
Below is the snip of "Scheduled Actions" of the created Incident.

Hi Ritesh
Email is triggered based upon conditions and you set
on closer look it is 3 different email on three 3 different requirement for e.g
email triggered to reporter on new status
email trigerred to processor on Proposed solution and New status
Therefore, check the start condition for above 2 email actions and refer below blog
Sending E-Mail from Support Message
Thanks
Prakhar

Finalize() method being called multiple times for same object?

I got a dilly of a pickle here.
Looks like according to the Tomcat output log file that the finalize method of class User is being called MANY more times than is being constructed.
Here is the User class:
package com.db.multi;
import java.io.*;
import com.db.ui.*;
import java.util.*;
* @author DBriscoe
public class User implements Serializable {
    private String userName = null;
    private int score = 0;
    private SocketImage img = null;
    private boolean gflag = false;
    private Calendar timeStamp = Calendar.getInstance();
    private static int counter = 0;
    /** Creates a new instance of User */
    public User() { counter++;
    public User(String userName) {
        this.userName = userName;
        counter++;
    public void setGflag(boolean gflag) {
        this.gflag = gflag;
    public boolean getGflag() {
        return gflag;
    public void setScore(int score) {
        this.score = score;
    public int getScore() {
        return score;
    public void setUserName(String userName) {
        this.userName = userName;
    public String getUserName() {
        return userName;
    public void setImage(SocketImage img) {
        this.img = img;
    public SocketImage getImage() {
        return img;
    public void setTimeStamp(Calendar c) {
        this.timeStamp = c;
    public Calendar getTimeStamp() {
        return this.timeStamp;
    public boolean equals(Object obj) {
        try {
            if (obj instanceof User) {
                User comp = (User)obj;
                return comp.getUserName().equals(userName);
            } else {
                return false;
        } catch (NullPointerException npe) {
            return false;
    public void finalize() {
        if (userName != null && !userName.startsWith("OUTOFDATE"))
            System.out.println("User " + userName + " destroyed. " + counter);
    }As you can see...
Every time a User object is created, a static counter variable is incremented and then when an object is destroyed it appends the current value of that static member to the Tomcat log file (via System.out.println being executed on server side).
Below is the log file from an example run in my webapp.
Dustin
User Queue Empty, Adding User: com.db.multi.User@1a5af9f
User Dustin destroyed. 0
User Dustin destroyed. 0
User Dustin destroyed. 0
User Dustin destroyed. 0
User Dustin destroyed. 0
USER QUEUE: false
INSIDE METHOD: false
AFTER METHOD: false
User Dustin destroyed. 1
User Dustin destroyed. 1
User Dustin destroyed. 1
User Dustin destroyed. 1
USER QUEUE: false
INSIDE METHOD: false
AFTER METHOD: false
User Dustin destroyed. 2
User Dustin destroyed. 2
User Dustin destroyed. 2
User Dustin destroyed. 2
User Dustin destroyed. 2
User Dustin destroyed. 2
User Dustin destroyed. 2
User Dustin destroyed. 2
USER QUEUE: false
INSIDE METHOD: false
AFTER METHOD: false
User Dustin destroyed. 3
User Dustin destroyed. 3
User Dustin destroyed. 3
User Dustin destroyed. 3
User Dustin destroyed. 3
User Dustin destroyed. 3
User Dustin destroyed. 3
User Dustin destroyed. 3
User Dustin destroyed. 3
USER QUEUE: false
INSIDE METHOD: false
AFTER METHOD: false
User Dustin destroyed. 4
User Dustin destroyed. 4
User Dustin destroyed. 4
User Dustin destroyed. 4
User Dustin destroyed. 4
User Dustin destroyed. 4
User Dustin destroyed. 4
User Dustin destroyed. 4
User Dustin destroyed. 4
USER QUEUE: false
INSIDE METHOD: false
AFTER METHOD: false
User Dustin destroyed. 5
User Dustin destroyed. 5
User Dustin destroyed. 5
User Dustin destroyed. 5
User Dustin destroyed. 5
User Dustin destroyed. 5
User Dustin destroyed. 5
User Dustin destroyed. 5
User Dustin destroyed. 5
USER QUEUE: false
INSIDE METHOD: false
AFTER METHOD: false
User Dustin destroyed. 6
User Dustin destroyed. 6
User Dustin destroyed. 6
User Dustin destroyed. 6
User Dustin destroyed. 6
User Dustin destroyed. 6
User Dustin destroyed. 6
User Dustin destroyed. 6
User Dustin destroyed. 6
User Dustin destroyed. 6
Joe
USER QUEUE: false
INSIDE METHOD: false
AFTER METHOD: false
User Dustin pulled from Queue, Game created: Joe
User Already Placed: Dustin with Joe
User Dustin destroyed. 7
User Dustin destroyed. 7
User Dustin destroyed. 7
User Dustin destroyed. 7
User Dustin destroyed. 7
User Dustin destroyed. 7
User Dustin destroyed. 7
User Dustin destroyed. 7
User Dustin destroyed. 7
User Dustin destroyed. 7
INSIDE METHOD: false
INSIDE METHOD: false
USER QUEUE: true
INSIDE METHOD: false
INSIDE METHOD: false
User Dustin destroyed. 9
User Joe destroyed. 9
User Dustin destroyed. 9
User Dustin destroyed. 9
User Dustin destroyed. 9
User Dustin destroyed. 9
INSIDE METHOD: true
INSIDE METHOD: false
USER QUEUE: true
INSIDE METHOD: false
INSIDE METHOD: false
INSIDE METHOD: true
INSIDE METHOD: false
USER QUEUE: true
INSIDE METHOD: false
INSIDE METHOD: false
It really does seem to me like finalize is being called multiple times for the same object.
That number should incremement for every instantiated User, and finalize can only be called once for each User object.
I thought this was impossible?
Any help is appreciated!

Thanks...
I am already thinking of ideas to limit the number of threads.
Unfortunately there are two threads of execution in the servlet handler, one handles requests and the other parses the collection of User objects to check for out of date timestamps, and then eliminates them if they are out of date.
The collection parsing thread is currently a javax.swing.Timer thread (Bad design I know...) so I believe that I can routinely check for timestamps in another way and fix that problem.
Just found out too that Tomcat was throwing me a ConcurrentModificationException as well, which may help explain the slew of mysterious behavior from my servlet!
The Timer thread has to go. I got to think of a better way to routinely weed out User objects from the collection.
Or perhaps, maybe I can attempt to make it thread safe???
Eg. make my User collection volatile?
Any opinions on the best approach are well appreciated.

On Execute operation, the bean getter is being called multiple times

Hi,
I have a JCR data control, i am trying to write a method that returns predicate, but this method is being called multiple times, when executing the advanced search operation.
public List<Predicate> getPredicates() {
ArrayList<Predicate> predicates = new ArrayList<Predicate>();
   // predicates.add(new Predicate("jcr:content/idc:metadata/idc:xScope",Operator.EQUALS,"GLOBAL"));
DCBindingContainer bc=(DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();
JUCtrlListBinding attrBinding=(JUCtrlListBinding) bc.findCtrlBinding("StateId");
Object stateId= attrBinding.getSelectedValue();
if(stateId instanceof Row){
predicates.add(new Predicate("jcr:content/idc:metadata/idc:xState"
, Operator.EQUALS
,((Row)stateId).getAttribute("StateId").toString()));
attrBinding=(JUCtrlListBinding) bc.findCtrlBinding("DistrictId");
Object districtId=attrBinding.getSelectedValue();
if(districtId instanceof Row){
      predicates.add(new Predicate("jcr:content/idc:metadata/idc:xDistrict",Operator.EQUALS,((Row)districtId).getAttribute("DistrictId").toString()));
    attrBinding=(JUCtrlListBinding) bc.findCtrlBinding("Scope");
    Object scopeId=attrBinding.getSelectedValue();
    if(scopeId instanceof Row){
        predicates.add(new Predicate("jcr:content/idc:metadata/idc:xScope",Operator.EQUALS,((Row)scopeId).getAttribute("ScopeType")));
    AttributeBinding tempAttrBinding=(AttributeBinding)bc.findCtrlBinding("CreatedDate");
    Object createdDate=tempAttrBinding.getInputValue();
    if(createdDate!=null){
        predicates.add(new Predicate("jcr:content/jcr:created",Operator.EQUALS,createdDate.toString()));
    if (predicates.size()>0){
      return predicates;
return Collections.emptyList();
} The problem is while it's being called multiple times different list's are being returned which is causing the method not to work . The bean is in pageFlowScope .

That is bc ADF life cicle... Is always executing 2 times...

Simple Event being Displayed Multiple Times

I have a simple event from the past that is being displayed multiple times. There are no other UIDs that are the same in iCal and no other event has the same SUMMARY name.
This particular event shows up 9 times. I can also reproduce the result from Automator by searching the specific calendar and looking for events in the date range.
The event is as follows:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Apple Inc.//iCal 3.0//EN
CALSCALE:GREGORIAN
BEGIN:VEVENT
SEQUENCE:5
TRANSP:OPAQUE
UID:EC6F5DBC-9BCC-4007-87F2-4A9C796C8551
DTSTART:20070330T000000
DTSTAMP:20071206T205550Z
SUMMARY:Babysit Paul
CREATED:20080919T173959Z
DTEND:20070401T120000
END:VEVENT
END:VCALENDAR
I am not very familiar with the format but it looks pretty straight forward.
The calendar is being synched via Mobile Me and is shared by another two computers. Not sure why this should be relevant since the entry on the computer and on Mobile Me both show this duplication of the event.
The reason I was looking at all was because of the hangs in iCal since I set the sync to automatic.
Any ideas welcome,
Richard

Post Author: foghat
CA Forum: Data Connectivity and SQL
If all the records you are displaying in your report
truly are duplicated, you could try check off 'select distinct records'
from the File --> Report Options menu. While this may solve the problem for you, it would be worthwhile to determine if you are actually joining your tables correctly.
likely the records aren't an exact duplicate and the problem is with your join criteria. To verify this you can: start by removing table b from the database expert altogether. does
that solve your problem of multiple rows? If it does, you are not joining to table b correctlyIf you still have
multiple rows, loan_id on its own must not make a record unique. Is
loan_id duplicated in either of your tables? Just because loan_id is a
primary key does not necessarily mean it is unique - often a record
will have 2 or more primary keys and only when all primary keys are
used is the record unique. If you display all of the columns
from both tables, you will hopefully see some (maybe just one) columns
where the value is different between your seemingly duplicate data.
You may need to join on this value as well.as for the type of join you are using (inner, not enforced) you should be fine. Good luck

Why LOOP AT XVBAP is triggering multiple times in user-exit in 1 item order

Hi,
Just curious,
I put the break point at LOOP AT XVBAP in user-exit of MV45A include of sales order transaction, then I created a sales order with ONLY one item(10) of 1 quantity (meaning, ONLY one schedule line)....then, Why my break-point(LOOP AT XVBAP) is triggering multiple times? even though there is ONLY one item/1 quantity? is supposed to trigger only 1 time(one iteration) right?
why mupltiple iterations are happening?
thank you

Hello ,
yeah thats true , that exit programs will called several types by SAP itself , so u need to find right FORM exits for ur requirements.
regards
Prabhu

HT201210 my iphone is being dissmissed every time i try to conectt to my home wifi

my iphone is being dissmissed every time i try to conectt to my home wifi

Hi there,
You may want to take a look at some of the troubleshooting steps found in the article below.
iOS: Troubleshooting Wi-Fi networks and connections
http://support.apple.com/kb/ts1398
Hope that helps,
Griff W.

Some fields in text box are being displayed multiple times

Hi All,
I am getting a strange error in Crystal Reports.
It is displaying a particular field multiple times while the query returns a single row.
I have used a text box in which I have dragged and dropped that field.
The version used to design the reports is Crystal Reports XI while client is having Crystal Reports 11.5.
Regards,
Misra P.

Hi Salah,
Thanks a lot for quick reply.
1- I am using SQL queries ,not tables.
2- The field is in page header for one report and in group header for the other one.
3- If i grag and drop simply,then it shows correct result,i.e. a single record.
e.g i am displaying a customer name with title.
Like Mr XYZ(page header,query is returning a single row).
and it is being displayed as
Mr XYZ
Mr
Mr
Mr
Mr
Mr
Thanks again.
Regards,
Misra P.

Photoshop CC 2014 Extension - CEP Event callback is triggered multiple times per single event

Trying to make my extensions listen for bunch of events and it's turning out to be a real pain in the ***.
I'm hoping there's someone here who has a bit more experience playing around with these.
I used the example code from here ( Page 43 ): http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/CC14_Extension_S DK.pdf
I've modified the code just a little. I removed some unnecessary things from it. I also added a counter, to try to visualize the issue.
Every time I pasted the code here, the global variable seemed to duplicate. So, eeeeh... the example code can be found here.
The problem is:
I close one document to trigger the event, but for some reason the callback seems to run multiple times.
Even better, it doesn't seem to be super consistent about it. Sometimes it repeats only couple of times and sometimes it repeats 160 times.
It seems like every time the extension panel is reopened, it comes up with a new number.
Currently, if I close a document, it seems to trigger the callback 15 times
Since this is screenshot, you'll have to take my word for it. I only closed a single document and the code ran 15 times.
Am I doing something wrong by any chance?
edit:
I believe I just found out the reason and a way to recreate the issue.
I've occasionally tested the extension by closing and opening the panel, which seems to have caused the issue.
It looks like every time I close and then open the panel, it... adds one more run time to the stack.
- Refreshing the panel from chrome doesn't seem to affect it.
When I restart photoshop, it resets. So after the very first opening of the panel, the event triggers the callback only once.
I forgot to mention that the host application events work just fine without these issues.
In fact, I tried to use documentAfterActivate before, but as far as I could find, there is no way to kind of filter out specific events within host application events.
For instance, I can't specify something different to happen when a new document is opened.
As very much a side note:
documentAfterActivate has its own side effect due to the way photoshop works.
It is triggered when you:
Create a new document
Open a new document
Switch to an open document
It's the "Switch to an open document" part that makes this event listener also trigger when you close a document.
Because when you close a document, photoshop switches back to the previous document and that in turn triggers the event listener when it shouldn't, I suppose.
Of course it doesn't trigger the event when you close the last document as there is no document to switch to at that point.
...but this is beyond the scope of the original question.

I was so tired last night that when I found out the cause of it, I never even thought about unregistering...
I decided to unregister it when the panel is opened instead.
This does indeed get rid of the issue.
Thanks, cbuliarca.
(function () {
var csInterface = new CSInterface();
function init() {
       themeManager.init();
       function registerPhotoshopEvent(in_eventId, register) {
            // Added the next line
            var register = register === "clear" ? "UnRegisterEvent" : "RegisterEvent";
            // Modified the next line
            var event = new CSEvent("com.adobe.Photoshop" + register, "APPLICATION");
            event.extensionId = csInterface.getExtensionID();
            event.appId = csInterface.getApplicationID();
            event.data = in_eventId
            csInterface.dispatchEvent(event);
       var number = 0;
       csInterface.addEventListener("PhotoshopCallback" , function(event) {
            number = number + 1;
            console.log( number );
       var closeEventid = "1131180832"
       // Added the next line
       registerPhotoshopEvent(closeEventid, "clear");
       registerPhotoshopEvent(closeEventid);
init();

Process Chain Triggers Multiple times

Hi All,
I have Meta process chain say ZAAA which has multiple Local Chains example ZBBB , ZCCC and ZDDD. .This Local chain ZCCC trigger multiple times of in one day . we had a issues today with deactivation of Transformations and DTP in different levels because of that Local Process chain ZCCC is failed along with other process chains . when I reach to ZCCC started by repeat or repair ,before Local Chain ZCCC finished whole process ,ZCCC triggers second time .
Now first times triggered process chain ZCCC is in yellow , and second time triggered process chain ZCCC gone through all the way to gree , and Meta chain showes red.
what I have do make Meta chain green.
Regards
Hari

Hi Hari,
I wonder what you mean by below statement:
one of the sub pc still yellow first time trigger and went to red and second time trigger whole process is green. all Sub PC are green
For the sub pc mentioned above, you trigger it all over again? Or you repeat/repair the step failed?
If you trigger it the second times all over again it is a new run and the first run remain fail,ed so the meta chain will never get green, if you want to make the meta chain green, you need to repeat/repair the step failed in first run.
Regards
Bill

Default button being clicked multiple times when enter key is pressed

Hello,
There seems to be a strange difference in how the default button behaves in JRE 1.4.X versus 1.3.X.
In 1.3.X, when the enter key was pressed, the default button would be "pressed down" when the key was pressed, but wouldn't be fully clicked until the enter key was released. This means that only one event would be fired, even if the enter key was held down for a long time.
In 1.4.X however, if the enter key is pressed and held for more than a second, then the default button is clicked multiple times until the enter key is released.
Consider the following code (which is just a dialog with a button on it):
public class SimpleDialog extends JDialog implements java.awt.event.ActionListener
private JButton jButton1 = new JButton("button");
public SimpleDialog()
this.getContentPane().add(jButton1);
this.getRootPane().setDefaultButton(jButton1);
jButton1.addActionListener(this);
this.pack();
public void actionPerformed(ActionEvent e)
if (e.getSource() == jButton1)
System.out.println("button pressed");
public static void main(String[] args)
new SimpleDialog().show();
When you compile and run this code under 1.3.1, and hold the enter key down for 10 seconds, you will only see one print line statement.
However, if you compile and run this code under 1.4.1, and then hold the enter key down for 10 seconds, you will see about 100 print line statements.
Is this a bug in 1.4.X or was this desired functionality (e.g. was it fixing some other bug)?
Does anyone know how I can make it behave the "old way" (when the default button was only clicked once)?
Thanks in advance if you have any advice.
Dave

Hello all,
I think I have found a solution. The behaviour of the how the default button is triggered is contained withing the RootPaneUI. So, if I override the default RootPaneUI used by the UIDefaults with my own RootPaneUI, I can define that behaviour for myself.
Here is my simple dialog with a button and a textfield (when the focus is NOT on the button, and the enter key is pressed, I don't want the actionPerformed method to be called until the enter key is released):
package focustests;
import java.awt.*;
import javax.swing.*;
import java.awt.event.*;
import java.util.*;
public class SimpleDialog extends JDialog implements java.awt.event.ActionListener
private JButton jButton1 = new JButton("button");
public SimpleDialog()
this.getContentPane().add(new JTextField("a text field"), BorderLayout.NORTH);
this.getContentPane().add(jButton1, BorderLayout.SOUTH);
this.getRootPane().setDefaultButton(jButton1);
jButton1.addActionListener(this);
this.pack();
public void actionPerformed(ActionEvent e)
if (e.getSource() == jButton1)
System.out.println("button pressed");
public static void main(String[] args)
javax.swing.UIManager.getDefaults().put("RootPaneUI", "focustests.MyRootPaneUI");
new SimpleDialog().show();
and the MyRootPaneUI class controls the behaviour for how the default button is handled:
package focustests;
import javax.swing.*;
* Since we are using the Windows look and feel in our product, we should extend from the
* Windows laf RootPaneUI
public class MyRootPaneUI extends com.sun.java.swing.plaf.windows.WindowsRootPaneUI
private final static MyRootPaneUI myRootPaneUI = new MyRootPaneUI();
public static javax.swing.plaf.ComponentUI createUI(JComponent c) {
return myRootPaneUI;
protected void installKeyboardActions(JRootPane root) {
super.installKeyboardActions(root);
InputMap km = SwingUtilities.getUIInputMap(root,
JComponent.WHEN_IN_FOCUSED_WINDOW);
if (km == null) {
km = new javax.swing.plaf.InputMapUIResource();
SwingUtilities.replaceUIInputMap(root,
JComponent.WHEN_IN_FOCUSED_WINDOW, km);
//when the Enter key is pressed (with no modifiers), trigger a "pressed" event
km.put(KeyStroke.getKeyStroke(java.awt.event.KeyEvent.VK_ENTER,
0, false), "pressed");
//when the Enter key is released (with no modifiers), trigger a "release" event
km.put(KeyStroke.getKeyStroke(java.awt.event.KeyEvent.VK_ENTER,
0, true), "released");
ActionMap am = SwingUtilities.getUIActionMap(root);
if (am == null) {
am = new javax.swing.plaf.ActionMapUIResource();
SwingUtilities.replaceUIActionMap(root, am);
am.put("press", new HoldDefaultButtonAction(root, true));
am.put("release", new HoldDefaultButtonAction(root, false));
* This is a copy of the static nested class DefaultAction which was
* contained in the JRootPane class in Java 1.3.1. Since we are
* using Java 1.4.1, and we don't like the way the new JRE handles
* the default button, we will replace it with the old (1.3.1) way of
* doing things.
static class HoldDefaultButtonAction extends AbstractAction {
JRootPane root;
boolean press;
HoldDefaultButtonAction(JRootPane root, boolean press) {
this.root = root;
this.press = press;
public void actionPerformed(java.awt.event.ActionEvent e) {
JButton owner = root.getDefaultButton();
if (owner != null && SwingUtilities.getRootPane(owner) == root) {
ButtonModel model = owner.getModel();
if (press) {
model.setArmed(true);
model.setPressed(true);
} else {
model.setPressed(false);
public boolean isEnabled() {
JButton owner = root.getDefaultButton();
return (owner != null && owner.getModel().isEnabled());
This seems to work. Does anyone have any comments on this solution?
Tjacobs, I still don't see how adding a key listeners or overriding the processKeyEvent method on my button would help. The button won't receive the key event unless the focus is on the button. There is no method "enableEvents(...)" in the AWTEventMulticaster. Perhaps you have some code examples? Thanks anyway for your help.
Dave

Same system being shown multiple time in Solution for Early Watch Report

Hi Gurus ,
I have some satellite system configured to Solution Manager . Today I can see the same system entry multiple time in the
Operations: Solution Monitoring -> Early Watch Alert.
eg .,
I have a system whose SID is ABC , i can see the ABC entry for todays date (i.e., 4 FEB 08) nearly 4 time .And this systems are not rescheduled for the next EWR (i.e scheduled for 11 FEB 08- since we have kept a period of 7 days )
Please suggest
Anthony

Hi Anthony,
There was an error, that EWA sessions for one systems were scheduled multiple times per week.
Please check [SAP Note 1083108 - Duplicate EarlyWatch Alerts|http://service.sap.com/sap/support/notes/1083108]
Search for SAP Notes with key words: EWA, multiple, duplicate.
Application area: SV-SMG-OP
What's the software configuration of your SolMan?
Best regards,
Ruediger

IPhone - Sybase RFC called multiple times

Hi,
I have an RFC that is adding some data in the system. This works, how ever it gets called multiple times with the same data. Every time a synchronization is done it adds a new row with all the same data. (even with 1 entry so it's not because of the loop).
This is how my save function looks, newEntriesMBO is an array with Synchronization parameters. Should I do anything more than [sync delete]?
        for (TimeSheets_EnterTimeDataSynchronizationParameters *sync in newEntriesMBO)
            [sync save];
            while ([TimeSheets_TimeSheetsDB hasPendingOperations])
                [NSThread sleepForTimeInterval:0.2];
            [sync delete];
Edited by: PJ Deraedt on Sep 19, 2011 11:06 AM

Hi
Once the personalization parameters are set ,you should call [pp save];
the next step would be to check for pending operations
while (TimeSheets_TimeSheetsDB hasPendingOperations)
NSThread sleepForTimeInterval:0.2;
Thats it no more code. sync delete etc is all not required. The reason why u get multiple calls is because pp save function is called multiple times.
Thanks
Pradeep

EO entity level validations being executed multiple times

Hi,
I'm using JDev 10.1.3.4, BC, JSF
I have defined multiple entity level method validators in my entity object. On commit I get the desired results except for the fact that each of my method validators runs multiple times when they should only run once. So I end up with twice the method validator messages that I should. And if I put any additional messaging in in the validators themselves I end up with 10 times the desired messages.
What are some of the reasons that would cause this looping through the validators. I assume I have done something to cause this but can not figure out what it is. Any ideas on what I should look for?
Note : Also using JHeadstart but I don't think it should be a factor at the entity level.
Thanks,
Jim
Edited by: 170412 on May 5, 2009 4:11 PM

Hi,
1) Set the Foreign key using setAttribute Methods ? When u create a VO based on Multiple EO's, there should be some relationship between those 8 EO's like Primary key & Foregin key. And when u perform Commit on this all the value from ur beans will get saved to the database. But the Foreign u need to set independently using setAttribute method becoz it wont get saved by its own.
2) If i'm doing the validations at EO level, those setters and getters will be called before the Create(), Update() and Delete()
methods in the EOImpl class. Is that true?Yes, you are right it will get called for create and update operation but not for Delete.
Regards,
Gyan

Orchestration Instance - message data being inserted multiple times to database

Hello,
I have a Transactional Scope orchestration which has an expression shape which writes unique messages to a custom database using helper - ADO.Net. We are noticing that when the BizTalk server (BTS 2009) is under stress few messages are
getting inserted multiple times. On further researching we have narrowed down the cause to be that when there is a delay in ADO.NET insert command completion, the orchestration engine wait threshhold is met and decides to dehydrate. But if around
the same time the ADO.NET insert completes and then after some time orchestration rehydrates and resumes from last persistence point, it inserts the message again causing the duplicates. Has anyone seen such behavior?
Thanks in Advance!

Yeah, we knew only other alternative is to use the WCF-SQL Adapter and include in Orchestration transaction - saw this pattern somewhere, do not want to use atomic scopes as it could lead to blocking. I'm sure there are several implementations out there
that user helper classes to do DB insert/updates and should have seen a similar issue.
I just want to make sure we are not missing something here. I strongly feel Microsoft BizTalk team should clearly state in their documentation that helper DB insert/updates should be avoided or put it in their best practices so that developers
dont have to figure this out the hard way.
Thanks!
You may try to call helper class from map inside Receive/send port using XSLT templates. Then you don't have to worry about orch. And in send port advanced properties you can set re-try to '0' so it doesn't try again 3 times. Either it fails first go and completes
once.

IPhone : webViewDidFinishLoad being triggered multiple times

Similar Messages

Maybe you are looking for