Why is the ActionForms validate-Method called twice?

Hello forum,
I'm new to struts and want to develop a form, where an internetuser can leave a comment to an article. Just like most sides, an image with an text is displayed, the text has to be written into an inputfield before the comment is commited in order to be saved.
When an user puts in no text or a wrong one, a errormessage is displayed, the old image is deleted and an new one is created and shown to the user. His input still stays in the fields.
I proof the correctness of the word in the validate-Method of the ActionForm and it works fine.
Now I've the following problem:
If the user puts in the correct text, the comment is saved and the side is displayed again including his comment.. But also all the input of the form should be erased. But for some reason, its not and the validate method is called again and since there is a new wordvarifyingimage and a new text to be inserted, it throws an error which is displayed again. Also, all the input of his last message is present!
So, I guess I miss a big point about the ActionForm handling. Why is the ActionForm called twice and why doesn't it erase the old input? I try to do this in the Action class after saving the comment, setting all the formparameters to "" or null.
Can anybody give me a hint?
Would be a big big help since I've not found anything googling about this issue.
If you need code, just tell me which part I put in here (ActionForm, Action, struts-config or jsp-file)
Thanxs in advance,
strutsnewbytopro

my jsp:
<%@ taglib uri="/WEB-INF/tld/struts-bean.tld" prefix="bean" %>
<%@ taglib uri="struts/html-el" prefix="html" %>
<%@ taglib uri="jstl/c" prefix="c" %>
<%@ taglib uri="/WEB-INF/tld/struts-logic.tld" prefix="logic" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<style type="text/css" title="currentStyle" media="screen">
          @import "../library/css/blog.css";
     </style>
<script language="javascript">
     function sendMail(){
          document.forms[0].formaction.value ='mail';
          document.forms[0].submit();
     function saveComment(){
          document.forms[0].formaction.value ='comment';
          document.forms[0].submit();
     </script>
</head>
<body>
<html:form action="/blog">
<div id="container">
     <div id="leftside">
          <logic:messagesPresent>
               <div id="errors">
                    <div style="color:#CC3333; ">
                    <p><span id="errorHeaders"><bean:message key="errors.validation.header"/></span>
                         <html:messages id="error">
                         <c:out value="${error}"/>
                         </html:messages>
                    </p></div>
               </div>
          </logic:messagesPresent>
             .... show blogentry ...
          <logic:present name="comments">
               <div id="divblogcomment">
               <logic:iterate name="comments" id="com">
               <div class="breaker10" style="clear:left; "></div>
<div class="rowblogcommentdate" style="width:150px;"<a href="<bean:write name="com" property="website" />"><bean:write name="com" property="username" /></a> am <bean:write name="com" property="postdate" /></div>
               <div class="rowblogcomment"><bean:write name="com" property="comment" /></div>
               </logic:iterate>
               <div class="breaker10" style="clear:left; "></div>
</div>
          </div>
                         </logic:present>
                         <logic:notPresent name="savedcomment">
                              <div id="writeblogcomment">
                              <div class="topbig"><div class="headsmall">enter Comment</div></div>
                              <div id="bginhaltwriteblogcomment">
                                   <div class="breaker10" style="clear:left; "></div>
                                   <div align="center">
                                        <table cellpadding="0" cellspacing="0" border="0">
                                             <tr>
                                                  <td>Name:</td>
                                                  <td> </td>
                                                  <td><html:text size="50" name="blogForm2" styleClass="inputtext" property="username"/></td>
                                                  <td> </td>
                                                  <td>Web:</td>
                                                  <td> </td>
                                                  <td><html:text size="50" name="blogForm2" styleClass="inputtext" property="webaddress"/></td>
                                             </tr>
                                             <tr>
                                                  <td>Enter Code:</td>
                                                  <td> </td>
                                                  <td><html:text size="66" name="blogForm2" styleClass="inputtext" property="commentword"/></td>
                                                  <td> </td>
                                                  <td >Code:</td>
                                                  <td> </td>
                                                  <td><img src="<bean:write name="entry" property="commentpicurl" />"></td>
                                             </tr>
                                              <tr>
                                                  <td colspan="7">Comment<br><html:textarea name="blogForm2" styleClass="comment" property="comment" /></td>
                                             </tr>
                                             <tr>
                                                  <td colspan="7"><html:submit styleClass="inputtext" onmousedown="javascript:saveComment();"><bean:message key="button.save"/></html:submit></td>
                                             </tr>
                                        </table>
                                   </p>
                                   </div>
                                   <div class="bottombig"></div>
                              </div>
                         </div>
                         </logic:notPresent>
                         <logic:present name="savedcomment">
                         <div id="writeblogcomment">
                              <div class="topbig">Comment saved<div class="headsmall">Kommentar gespeichert</div></div>
                              <div id="bginhaltwriteblogcomment">
                                   <div class="breaker10" style="clear:left; "></div>
                                   <div align="center">
                                        <table cellpadding="0" cellspacing="0" border="0">
                                             <tr>
                                                  <td>Comment saved</td>
                                             </tr>
                                        </table>
                                   </p>
                                   </div>
                                   <div class="bottombig"></div>
                              </div>
                         </div>
                         </logic:present>
                         </div>
</div>
<html:hidden name="blogForm2" property="formaction"/><br>
<html:hidden name="blogForm2" property="id"/><br>
<% session.removeAttribute("savedcomment"); %>
</html:form>
</body>
</html>

Similar Messages

Why valueChaged( ) method called twice

Dear All,
I have made a class MyList by extending JList and implements ListSelectionListener and override valueChanged method. When we clicked on the list item this method called twice. Can you please explain the region?
I write my code like that:
Public void valueChanged(ListSelectionEvent lse)
System.out.println(�Hello�);
Out put:
Hello
Hello
Thanks
Bipin Kuma

It's expected - check the details and you'll see why.
If, say, the user had selected item 3 and then select item 8 then you might get two events:
1. first 3, last 3, isAdjusting true
2. first 8, last 8, isAdjusting false
It's a poor event protocol if you ask me but there you go.

What's the chain of methods called for painting components?

Hi, I'm trying to find out at what point components are painted within a container, as in what methods are being called for that component to be rendered to the graphics context.
I've tried watching for calls going to paint, paintAll and paintComponents, but if a component has been added to a container it seems that even if I override all of those methods of the container the components that have been added still get displayed.
So I suppose I have two questions:
* - What is the chain of methods called when a container is told to paint/repaint itself?
* - What are the purpose of paintAll & paintComponents, I can't find anything that actually uses these calls.
Thanks in advance,
L

Well it seems that the paint method of the component is being called from sun.awt.RepaintArea.paint(...) which itself is being kicked off from handling an event that's been thrown.
That's clearer now....but has anyone seen when paintAll, paintComponents or the printXXX counterparts have actually been called by a part Sun's code? I can see how they (Sun) would advocate a practice lke this, but it would seem kinda lame for them to suggest it and then for them not to use it themselves.....that's why I think there's probably something in the JRE that does call these methods at sometime....can anyone cast some light on this?

How to use ActionForm validate() method in ADF/Struts project

Hi
We are developing a project using ADF/Struts. We are not planning to use entity level validation. Rather we prefer to have it at Struts Form Bean level. So we need to have validate() method in Form Bean.
That mean we need to have seperate bean for all the actions /jsp. The ADF's DataForm form bean is not gonna work for us. Is that correct.
Please let me know...am I in the right direction.
That could be a different discussion why we don't prefer entity level validation

You can use the Struts validator plug-in (there's a howto on doing that on OTN) and it will handle the basics for you through XML definitions.
If you want to specifically have a Form bean with a Validate() then the issue is that the current "DataForm" is a generic bean driven of the databinding files, so yes you'd have to write a bean per screen to use instead and loose that benefit of having a universal Bean. (Internally the DataPage and DataActions will respect the ActionForm APIs so you can pluf your own ActionForm subclass in with no problem.
Plan B might be to leave the DataForm Bean in place and instead override the lifecycle of the datapage, probably in prepareModelUpdates()

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?

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

Rest Service method called twice in wcf

Hi all,
I have created a rest service using wcf.
I am writing Entity framework code within a service method to fetch data from database.
Every call from browser is hitting the service method twice or thrice.
I found no exception within the method. I encountered same problem before and solved it adding DataContract attribute to all the models(not helping now).
What may be the possible reasons? Please help.
Regards
Ashish

Hi,
I want to know if you are using the WebGet (Http GET). If so, please try to change that API to WebInvoke (Http POST).
Because IIS has some setting for HTTP GET as 40sec replay, so if within 40sec the server does not get response, then it will query itself again. Then it will be called twice or more.
For more information, please try to refer to:
#RESTful API in WCF get called more than one time:
http://www.codeproject.com/Tips/338142/RESTful-API-in-WCF-get-called-more-than-one-time-b .
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

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?

EO Validation method called twice

Hi,
I have written an EO based field Validation method. But the problem is it is being called twice. First time ,it is validating correctly. But the second time it is not taking the field value and giving the error
I have included it like this in my jspx.
<af:inputText value="#{bindings.SubOrgName.inputValue}"
label="#{bindings.SubOrgName.label}"
required="#{bindings.SubOrgName.mandatory}"
columns="#{bindings.SubOrgName.displayWidth}"
binding="#{backing_Org.inputText3}"
id="inputText3"
rows="1">
<af:validator binding="#{bindings.SubOrgName.validator}"/>
</af:inputText>
Please help.

Thanks for sharing! ;-)

Want to know how to debug the Business Object Method called from CRM

Hi all,
I have to debug a Method of a custom Business Object. This is being called when a certain action is performed
on the CRM ( CIC0 screen). I can not see an option to set an external break point in the Program of the Business Object
Method.
This Business Object calls a standard SAP FM. I tried setting an external break point in that FM and tried executing that.
But it is not stopping there.
Can any one please let me know how I can debug this when triggered from CRM?
Thanks in advance.
Thanks & regards,
Y Gautham

Hi,
I have tried checking the option 'IP MATCHING' option. I have given my user id and also the 'WEBUSER' as well.
But still I am unable to debug the application.
Can you please let me know if I am missing anything further.
Thanks & regards,
Y Gautham

Why does the phone spontaneously make calls when stored away and locked?

Even when the screen is locked, the phone will make calls. What can I do to stop this? Thanks much!

The basic troubleshooting steps are reset, restart, and restore.
Are you sure the device is staying locked? Do you have a lock code set?

Swing: actionPerformed method called twice

Hi All,
In a Swing application, is it correct to do as below piece of code, In a button click event handler call the actionPerformed method once again when the validation fails. Will it have any effects on the performance.
The reason for me to ask this is because my Swing application works fine for a level of time. Then suddenly starts to call the actionPerformed method twice without any reason for each button click event.
All I can suspect is the below piece of code. Pls help. Let me know if I am not clear.
button_actionPerformed(ActionEvent e) {
Actions .......
If(!Validate) {
        button_actionPerformed(ActionEvent e);
}

ActionListener is there only once
button.addActionListener(new java.awt.event.ActionListener() {
   public void actionPerformed(ActionEvent e) {
         try{
            button_actionPerformed(e);
         catch (Exception ex)
            ex.printStackTrace();
});

Action Listener Method called multiple times

I have a page (fragment .jsff), containing a simple input text and a button called "search". When I click on "Search" the action listener is triggered multiple times. (The results are displayed in a table inside a panel collection).
The results are actually coming back ok.
When I debug the code, I can see the action listener method called twice.
Do you know why is that?
What should I be taking care of?
This is my code :
*** Fragment ****
<af:commandButton text="#{identityBundle.search_label}" id="cb1"
actionListener="#{UserDetailsBean.searchUsersListener}"
disabled="#{!bindings.searchUsers.enabled}"/>
*** Managed bean ***
public void searchUsersListener(ActionEvent actionEvent) {
// Add event code here...
DCBindingContainer bindings = (DCBindingContainer)getBindings();
DCIteratorBinding iter = bindings.findIteratorBinding("userIterator");
DCDataRow row = (DCDataRow)iter.getCurrentRow();
User user = (User)row.getDataProvider();
boolean isSearchCriteriaPresent = false;
if(user != null){
String fn = user.getFirstname();
if(fn != null && !fn.trim().equals("")){
isSearchCriteriaPresent = true;
user.setLastname(fn);
user.setNonMTUserLogin(fn);
try {
Map <Object, Object> userMap = PropertyUtils.describe(user);
for(Map.Entry<Object, Object> entry: userMap.entrySet()){
if(entry.getKey() != null && entry.getValue() != null && !entry.getKey().toString().equalsIgnoreCase("class")){
isSearchCriteriaPresent = true;
break;
} catch (IllegalAccessException e) {
e.printStackTrace();
} catch (InvocationTargetException e) {
e.printStackTrace();
} catch (NoSuchMethodException e) {
e.printStackTrace();
if(!isSearchCriteriaPresent){
user.setFirstname("*");
OperationBinding opBinding = (OperationBinding)bindings.getOperationBinding("searchUsers");
opBinding.getParamsMap().put("user", user);
opBinding.execute();
AdfFacesContext adfFacesCtx = AdfFacesContext.getCurrentInstance();
Map<String, Object> scopePageFlowScopeVar= adfFacesCtx.getPageFlowScope();
scopePageFlowScopeVar.put("userSearchCriteria", user);
ADFContext adfCtx = ADFContext.getCurrent();
Map sessionScope = adfCtx.getSessionScope();
sessionScope.put("userSearchCriteria", user);
setUserSearchCriteria(user);
if(selectedUserID != null){
selectedUserID.setValue(null);
RichTable table = getUserResultsTable();
DCIteratorBinding searchUsersIterator = (DCIteratorBinding)bindings.get("searchUsersIterator");
Row[] rows = searchUsersIterator.getAllRowsInRange();
if(rows.length > 0){
RowKeySetImpl rks = new RowKeySetImpl();
ArrayList keyList = new ArrayList();
keyList.add(rows[0].getKey());
rks.add(keyList);
table.setSelectedRowKeys(rks);
table.setDisplayRowKey(keyList);
refreshState(table);
if(!isSearchCriteriaPresent){
user.setFirstname(null);
else{
deleteUserButton.setDisabled(true);
resetPasswordButton.setDisabled(true);
enableUserButton.setDisabled(true);
disableUserButton.setDisabled(true);
Thanks in advance for your help

Hi,
Can you try this?
1. set partialSubmit=true for the "search" button
2. set "search" button id as partialTrigger in your result table
-Prasad

Null reference method call behaving oddly

Hi all, and a very happy new year!!
My question concerns the null reference; simply, why does the following code chooses to call any other method than the Object version (try it out). No matter what type i choose to replace the current String version with... I have not paid much thought to this, but i would have guessed the null reference calls the Object version in such a situation.
If i leave only the Object method and comment out all others, the code compiles fine and calls the Object version at runtime - but in case there are sub class versions, those will be called. WHY?
(im running jre 1.4.1).
The code:
public class NullTest {
     public void method(Object o) {
          System.out.println("Object Version");
     public void method(String s) {
          System.out.println("String Version");
     public static void main(String args[]) {
NullTest nullTest = new NullTest();
          nullTest.method(null);
}

schapel, the question related specifically to
null, in a context where no runtime type can be
inferred. It wasn't about overloading in general.Yes, I understand that. But here is the rule from the JLS:
"If more than one method declaration is both accessible and applicable to a method invocation, it is necessary to choose one to provide the descriptor for the run-time method dispatch. The Java programming language uses the rule that the most specific method is chosen."
Note that it does not refer specifically to a null argument.
The question is "why is the most specific method called?" The reason is that there are only a few possibilities for this rule:
1. The least specific method should be called. In this case, overloaded methods with more specific types could not be called.
2. If there is more than one method, it is a compile time error. Again, this would cause overloading to be useless.
3. The most specific method is called. It is only with this rule that overloading works. That's why Java uses this rule.

AcquireConnection method call to the connection manager Excel connection Manager failed

I used VS Studio 2008 (BIDS version 10.50.2500.0) on an WinXp machine (v 5.1.2600 SP3 Build 2600) to create a package that writes multiple query results to different tabbed sheets of a single excel spreadsheet. The package was working just fine and has run
successfully multiple times, but all of a sudden when opening the project, every single Data Flow task with an Excel Connection Manager displayed error icons. Each raises the following error message when attempting to open the Advanced Editor:
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005 Description: "Unspecified error". Error at DataFlow task name: SSIS error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method
call to the connection manager Excel connection Manager failed with error code 0xC0202009. There may be error messages posted before this with more information on why the Acquire Connection method call failed. Exception from HRESULT: 0Xc020801c (Microsoft.SQlServer.DTSPipelineWrap)
From the time I created the original package (when it worked fine) until now:
1) I have been using the same computer, the same login account and the same permissions.
2) I have been writing to the same (32 bit) 2010 Excel file (which I created) in a folder on my local machine.
3) The filename and location have not changed; a template file is used each time to move and overwrite the previous file. Both are in the same locations.
4) I can independently open the target Excel file and the template Excel files with no errors.
6) The ConnectionString has not changed. The Connnection String I am using is
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Conversion\Conversion\Results_dt01.xlsx;Extended Properties="EXCEL 12.0 XML;HDR=YES;".
7) Run64BitRuntime is set to False.
8) Delay Validation is set to true
9) This is not running under a SQL job
10) There are no child packages being run
I CAN create a NEW Excel Connection Manager, assigning it the exact same target Excel spreadsheet, successfully, but when I attempt to assign it to the Data Flow destination this error occurs:
"Test connection failed because of an error in initializing provider. Unspecified error."
Thinking that the driver might be corrupt, I opened a second SSIS package, which also uses the Excel Connection Manager (same driver) and this package continues to work fine on the same workstation with no errors.
I have searched online for causes of this error for many hours and found nothing that helps me to solve this issue.
Does anyone have any suggestions for me?

Yes, I have verified that the Excel file is not in use or opened by anyone, including me. It has been two months since I opened this particular package, although I have been working with other packages in this project. I just discovered that another
package in the same project has the same problem - all Data Flows that output to an Excel Destination now have the same error icons. This second packages outputs to an entirely different Excel file than in the first package. A summay:
Package #1 has error on every Excel Destination and uses templateA to overwrite fileA and then writes to fileA
Package #2 has error on every Excel Desintation and uses templateB to overwrite fileB and then writes to fileB
Package #3 has no error on any Excel Destination and is linked to multiple files (none are A or B)
Package #1 and #2 are in the same project, but Package #3 is in a separate project .
I will try replacing the Excel files with new ones for Package 1 and 2.

Why is the ActionForms validate-Method called twice?

Similar Messages

Maybe you are looking for