Error compiling with extends attribute

I've got an abstract class I would like to extend in a JSP.
I can get it to work with other classes but not in my JSP.
<%@page extends="com.websource.database.Connections"%>
If I remove this the JSP will compile. But when included I get an error like:
getPageContext(javax.servlet......) cannot be applied to....
Any advice would be most appreciated.

To quote the JSP spec:
"The creation of the implementation class for a JSP page may be done solely by the JSP
container, or it may involve a superclass provided by the JSP page author through the use of
the extends attribute in the jsp directive. The extends mechanism is available for
sophisticated users and it should be used with extreme care as it restricts what some of the
decisions that a JSP container can take, e.g. to improve performance.
The JSP page implementation class will implement Servlet and the Servlet protocol
will be used to deliver requests to the class."
i.e you need to implement all the methods of javax.servlet plus probably HttpJspPage as well. Is this what you are trying to do?

Similar Messages

Error compiling with JFileChooser

Hi all,
I'm having a problem with some code not compiling. I'm using the linux blackdown sdk on FreeBSD. I have created a new class to test this problem and I get the same response I was getting in my main application. The code is as follows:
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class Test extends JFrame {
        JFileChooser chooser = new JFileChooser(".");
        chooser.setFileSelectionMode(JFileChooser.DIRECTORIES_ONLY);
}The error message that I am getting is as follows:
$ javac Test.java
Test.java:9: <identifier> expected
chooser.setFileSelectionMode(JFileChooser.DIRECTORIES_ONLY);
^
Test.java:9: package chooser does not exist
chooser.setFileSelectionMode(JFileChooser.DIRECTORIES_ONLY);
^
2 errors
I can't see what I'm doing wrong here. I've definitely created chooser as a new JFileChooser object.
Any help would be much appreciated!
Thanks,

you can't call one of your object's methods outside of a method/constructor body. Try this:
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class Test extends JFrame {
     JFileChooser chooser;
     public Test() {
          super("Test");
          chooser = new JFileChooser(".");
          chooser.setFileSelectionMode(JFileChooser.DIRECTORIES_ONLY);
Happy Birthday to Me.

Error Compiling With java.mail.Session class

Hi,
The Java compiler issues an error message (below) during compilation of the following line:
Session session = Session.getDefaultInstance( fMailServerConfig, null );
The error message is:
bad class file: c:\j2ee_sdk\lib\j2ee.jar(javax/mail/Session.class)
class file has wrong version 48.0, should be 47.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
javax.mail.Session session = javax.mail.Session.getDefaultInstance( fMailServerConfig, null );
I have tried switching between JDKs by changing the JAVA_HOME environment variable between JDKs 1.3.x to 1.4.x to 1.5.x and also to the JDK installed with the 2005 Q1 J2EE installation that I am using.
Any ideas on how to resolve this problem? And help would be GREATLY appreciated.
Thanks!!!
Stuart Hoffman

in Session session = Session.getDefaultInstance( fMailServerConfig, null ); pass the object of properties class instead of mailServerconfig
now your problem are solved

HT5285 XSAN 3 extended attributes with StorNext clients

Is the info that StorNext clients must not access XSAN volumes with extended attributes enabled still valid with XSAN 3 and StorNext 4.3?
What can happen, if it connects with the volume anyway? Is it only that file permissions get mixed up or will it likely even cause data corruption?
Thanks for your comments!

Yes this is fine. This is my personal expericence and might help you in the future as many have not thought about doing this.
I had a customer who "lost all his data" or so he thought. As a engineer you always tell you customer things and it seems that they just don't hear what you are saying until you politely tell them "nah nah da boo boo, I told you so" I remember specifically telling him that you need to ask before you update your OS version. So he decieded not to do it anyway, but only do it on half. So he had a wonderful mix between OS X 10.6.7 and 10.6.8 which is when on the Apple wolrd extended attributes became different. Basically what happened was the MDC couldn't understand the extended attribute, thus not allowing the SAN to mount. So after fighting the entire day with this, I simply grabbed a Linux machine installed Stornext made a temp license and was able to mount the X-SAN volume via the Linux MDC. We copied all the data off and then back on again. Now he keeps to upgrading to me.
The reason for this story is to tell you that Linux doesn't care about exteded attributes.

[Forms10g (9.0.4)] error 310 with %ROWTYPE

I have a package specification in which i declare a user defined type and a function:
SUBTYPE services_record_type IS services%ROWTYPE;
FUNCTION services(services_record IN OUT services_record_type) RETURN BOOLEAN;
When i compile, i am getting this error:
Error 310 with %ROWTYPE attribute. 'SERVICES' must name a table, cursor or cursor-variable.
I've tried with the schema name:
SUBTYPE services_record_type IS star.services%ROWTYPE;
And it compiles with no error.
But, i rather prefer using my public synonym instead of an absolute reference 'schema-name.table_name'.
I also thought changing my function name 'services' to something else, and it also works.
In the Oracle Forms Developer online help, it is written that:
Unique Names Required within a Package
In PL/SQL V1, when you created a variable with the same name as a procedure or function in the same package, the variable was always used; the identically named procedure or function was ignored. In versions after V1, variables, functions, and procedures within the same package must be unique.
To avoid an error, make sure all procedures within a package have unique names, either by doing so explicitly, or by appending the word Unused to the procedure name.
In the White Paper : Upgrade Developer Forms 4.5 to Oracle Forms 6, it is stated that:
VARIABLES AND PROGRAM UNITS WITH SAME NAME IN SAME PACKAGE
It is no longer legal to have program units and variables with the same name in the same package.
The compiler cannot resolve which to reference. With PL/SQL V1 you may have gotten unexpected results at runtime, meaning that while coding you may have meant to reference the value of a variable, but intead got the return value of a function with the same name.
Oracle recommends prefixing all variable whith a 'v_'.
It seems to me that Forms Builder considers type declarations as being like variable or subprogram declarations and applies the same restriction on the naming of objects.
Yet in the reference books, no where there're issues uppon this restriction on type definition ?
Could someone help me please !
Message was edited by:
[email protected]
null

We can not have object with same name in same schema
I agree with you, but in my case, i'm dealing with a packaged program unit :
PackageName.services.
In the naming space of my user star schema there cannot be conflict between all my object names. On one hand i have a table 'services' and on the other a package 'PackageName' in which i have a function 'services'.
Meanwhile, if i replace my public synonym services%ROWTYPE by an absolute reference to my table star.services%ROWTYPE, we're still in the same schema so same name space, no problem it compiles pretty well !
What do you think about it ?
.

CSI: update_item_instance issues while creating extended attributes

Hello,
For our customer's data conversion, installed base instances have already been created, there is only need to create extended attributes.
Issues I have encountered are:
- Whenever an error is encountered in the API call, all following records are rejected with the same error (even the same instance ID/primary key/attribute ID) as the first error record.
- Extended attributes are randomly entered in the wrong fields (as if one field had gone missing and the others had been updated)
- Date formats have been changed from DD/MM/YYYY to DD-MON-YYYY when consulting from Installed Base (but this happened only once)
Other information: There are 14 extended attributes to be added for each item instance, I removed some of the attributes to make the code more readable.
I followed the metalink note that shows the implementation method for this API and only added the recursive elements that we needed for the 14 attributes + functions to retrieve item_id and such.
The "message()" function replaces is defined as FND_FILE.PUT_LINE(which =>fnd_file.log,buff => p_msg);
PROCEDURE main (errbuf OUT VARCHAR2
                    ,retcode OUT NUMBER
IS
     vl_status                BOOLEAN;
     vl_item_id                NUMBER;
     vl_instance_id           NUMBER;
     v_count               NUMBER;
     v_err_rec CSI_DATASTRUCTURES_PUB.TRANSACTION_ERROR_REC;
     v_trx_id number ;
     v_ret varchar2(240);
     v_msg_count number;
     v_msg_data varchar2(2000);
     v_date date;
     t_msg_dummy NUMBER;
     t_output VARCHAR2(2000);
     vl_attribute_id NUMBER;
     v_inst_rec csi_datastructures_pub.instance_rec;
     v_ext_attr csi_datastructures_pub.extend_attrib_values_tbl;
     v_party_tbl csi_datastructures_pub.party_tbl;
     v_account_tbl csi_datastructures_pub.party_account_tbl;
     v_pr_tbl csi_datastructures_pub.pricing_attribs_tbl;
     v_org_as s_tbl csi_datastructures_pub.organization_units_tbl;
     v_asset_as s_tbl csi_datastructures_pub.instance_asset_tbl;
     v_trx csi_datastructures_pub.transaction_rec;
     v_inst_id_lst csi_datastructures_pub.id_tbl;
BEGIN
     APPS.FND_GLOBAL.Apps_Initialize(FND_PROFILE.value('user_id')
,FND_PROFILE.value('resp_id')
,FND_PROFILE.value('resp_appl_id'));
     IF cur_iea_attributes%ISOPEN
     THEN
          CLOSE cur_iea_attributes;
     END IF;
     IF get_trx_id
     THEN
          message('Transaction ID '||to_char(gv_trx_id));
          FOR v_cur_iea_attributes IN cur_iea_attributes
          LOOP
               v_count:=0; -- Initialisation du compteur du ligne. Attention, le nb de lignes dans interface = 14 x nb lignes dans stg
               IF check_unique_serial(v_cur_iea_attributes.numero_serie)
               -- Recuperation de l'item ID
               THEN
                    get_item_id(p_serial_number => v_cur_iea_attributes.numero_serie
                                   ,p_item_id => vl_item_id
                                   ,p_status => vl_status
                    message('Resultat get_item_id: '||to_char(vl_item_id));
                    get_instance_id(p_item_id => vl_item_id
                                        ,p_serial_number => v_cur_iea_attributes.numero_serie
                                        ,p_instance_id => vl_instance_id
                                        ,p_status => vl_status
                    IF vl_status
                    THEN
                         v_trx.TRANSACTION_DATE:=trunc(SYSDATE);
                         v_trx.SOURCE_TRANSACTION_DATE:=trunc(SYSDATE);
                         v_trx.TRANSACTION_TYPE_ID:=gv_trx_id;
                         message('Entrance v_count'||to_char(v_count));
                         v_inst_rec.instance_id:=vl_instance_id;
                         v_inst_rec.object_version_number := 1;
                         IF v_cur_iea_attributes.IAE_GUARANTEE_END_DATE IS NOT NULL
                         THEN
                              v_count:=v_count+1;
                              v_ext_attr(v_count).instance_id := vl_instance_id;
                              message('v_ext_attr(v_count).instance_id: '||to_char(v_ext_attr(v_count).instance_id));
                              message('vl_instance_id: '||to_char(vl_instance_id));
                              get_attribute_id(p_attribute_code =>'GUARANTEE_END_DATE'
                                                  ,p_attribute_id => vl_attribute_id);
                              message('vl_attribute_id: '||to_char(vl_attribute_id));
                              v_ext_attr(v_count).attribute_id := vl_attribute_id;
                              v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_GUARANTEE_END_DATE ;
                              message('v_cur_iea_attributes.IAE_GUARANTEE_END_DATE: '||v_cur_iea_attributes.IAE_GUARANTEE_END_DATE);
                              message('');
                         END IF;
                         IF v_cur_iea_attributes.IAE_LAST_CTRL_DATE IS NOT NULL
                         THEN
                              v_count:=v_count+1;
                              message('v_count'||to_char(v_count));
                              -- Les 6 champs obligatoires a remplir pour un update
                              v_ext_attr(v_count).instance_id :=vl_instance_id;
                              get_attribute_id(p_attribute_code =>'LAST_CTRL_DATE'
                                                  ,p_attribute_id => vl_attribute_id);
                              v_ext_attr(v_count).attribute_id := vl_attribute_id;
                              v_ext_attr(v_count).attribute_value := v_cur_iea_attributes.IAE_LAST_CTRL_DATE ;
                         END IF;
                         CSI_ITEM_INSTANCE_PUB.update_item_instance
                                   p_api_version => 1
                                   ,p_commit => fnd_api.g_false
                                   ,p_init_msg_list => fnd_api.g_true
                                   ,p_validation_level => fnd_api.g_valid_level_full
                                   ,p_instance_rec => v_inst_rec
                                   ,p_ext_attrib_values_tbl => v_ext_attr
                                   ,p_party_tbl => v_party_tbl
                                   ,p_account_tbl => v_account_tbl
                                   ,p_pricing_attrib_tbl => v_pr_tbl
                                   ,p_org_assignments_tbl => v_org_ass_tbl
                                   ,p_asset_assignment_tbl => v_asset_ass_tbl
                                   ,p_txn_rec => v_trx
                                   ,x_instance_id_lst => v_inst_id_lst
                                   ,x_return_status => v_ret
                                   ,x_msg_count => v_msg_count
                                   ,x_msg_data => v_msg_data
                              -- Output the results
                              if v_msg_count > 0
                              then
                                   for j in 1 .. v_msg_count
                                   loop
                                        fnd_msg_pub.get ( j , FND_API.G_FALSE , v_msg_data , t_msg_dummy );
                                        t_output := ( 'Msg' || To_Char ( j ) || ': ' || v_msg_data );
                                        message( SubStr ( t_output , 1 , 255 ) );
                                   end loop;
                              end if;
                    ELSE
                         message('Update not performed for '||v_cur_iea_attributes.numero_serie||' and '||vl_item_id);
                    END IF;
               ELSE
                    message('Erreur sur '||v_cur_iea_attributes.numero_serie);
               END IF;
               commit;
               message('Commit done for update loop');
          END LOOP;
     ELSE
          message('No Transaction ID - EOP');
     END IF;
EXCEPTION
     WHEN OTHERS
     THEN
          ROLLBACK;
          message('Error in main program, rolling back');
END main;
Thanks!

Todd
The issue seems to because this:
x_instance_rec.inventory_item_id := ib_rec3.inventory_item_id;
You are selecting the item id from your staging table. But the serial number in the csi_item_instances is associated with the instance is a different item id than ib_rec3.inventory_item_id. Hence this error. You cannot change the item in the IB once the instance is created.
You have two choices: comment this out or change the inventory_item_id in staging table to match with the csi_item_instances.
Also a lot depends on what is your serial number uniqueness. If you are using the same serial number for two different items (uniqueness with item_Id) you need to be careful which one you are picking (based on serial number).
Thanks
Nagamohan

When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported. Is this a bug in Mavericks?

When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported.
This happens not just with the SSD in my Mac Mini, but with another SSD in my MacBook (both now running Mavericks). So far as I know, all of the kit I am using is in good order (despite the file corruption reports). So I am beginning to wonder if it could be due to a bug in Mavericks? Both SSD drives have been formatted to MacOS Extended (journaled) format. Should I have used a different format, I wonder?
Has anyone else encountered this issue?
Does anyone have a solution?
Or an explanation that might help my investigation of the issue?
Thanks guys,

I understand that the Corsair Force 3 is not one of the SSD drives that are supported on Apple Macs.
I did try downloading and using Trim Enabler, but the error message came up both when it was off and when it was on.
I understand that not everyone thinks Trim Enabler is a good program, though there is a new version out now, so I may give it another try.

JDev 1013 Error: Internal compilation error, terminated with a fatal except

I've a class I compiled used in JDev 10.1.2.1.
Now I try to compile it with JDev 10.1.3 but I get an error :
Error: Internal compilation error, terminated with a fatal exception
What does it means ?
How can I solve it ?
I tried to use both 5.0 and 1.4.2 compilers but the result is the same.
Tks
Tullio
Here the class
/* The following code was generated by JFlex 1.2.2 on 05/10/04 17.46 */
* Copyright (C) 1998,99 Gerwin Klein <[email protected]>. *
* All rights reserved. *
* This program is free software; you can redistribute it and/or modify *
* it under the terms of the GNU General Public License. See the file *
* COPYRIGHT for more information. *
* This program is distributed in the hope that it will be useful, *
* but WITHOUT ANY WARRANTY; without even the implied warranty of *
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the *
* GNU General Public License for more details. *
* You should have received a copy of the GNU General Public License along *
* with this program; if not, write to the Free Software Foundation, Inc., *
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA *
package axioma.a4j.parser;
import java_cup.runtime.*;
* This class is a scanner generated by
* JFlex 1.2.2
* on 05/10/04 17.46 from the specification file
* <tt>file:/C:/A4j/A4j/Common/Parser/grammatiche/Scanner.flex</tt>
public class AxScanner implements java_cup.runtime.Scanner {
/** this character denotes the end of file */
final public static int YYEOF = -1;
/** lexical states */
final public static int STRING = 1;
final public static int YYINITIAL = 0;
final public static int CHARLITERAL = 2;
* Translates characters to character classes
final private static String yycmap_packed =
"\11\10\1\3\1\2\1\0\1\3\1\1\16\10\4\0\1\3\1\50"+
"\1\16\1\0\1\7\1\0\1\44\1\15\1\31\1\32\1\5\1\41"+
"\1\40\1\42\1\14\1\4\1\12\11\13\1\0\1\37\1\47\1\46"+
"\1\45\2\0\32\11\1\35\1\17\1\36\1\0\1\11\1\0\1\25"+
"\1\51\2\11\1\23\1\24\5\11\1\26\1\6\1\30\3\11\1\21"+
"\1\27\1\20\1\22\5\11\1\33\1\43\1\34\1\0\41\10\2\0"+
"\4\11\4\0\1\11\12\0\1\11\4\0\1\11\5\0\27\11\1\0"+
"\37\11\1\0\u0128\11\2\0\22\11\34\0\136\11\2\0\11\11\2\0"+
"\7\11\16\0\2\11\16\0\5\11\11\0\1\11\21\0\117\10\21\0"+
"\3\10\27\0\1\11\13\0\1\11\1\0\3\11\1\0\1\11\1\0"+
"\24\11\1\0\54\11\1\0\10\11\2\0\32\11\14\0\202\11\1\0"+
"\4\10\5\0\71\11\2\0\2\11\2\0\2\11\3\0\46\11\2\0"+
"\2\11\67\0\46\11\2\0\1\11\7\0\47\11\11\0\21\10\1\0"+
"\27\10\1\0\3\10\1\0\1\10\1\0\2\10\1\0\1\10\13\0"+
"\33\11\5\0\3\11\56\0\32\11\5\0\13\11\13\10\12\0\12\10"+
"\6\0\1\10\143\11\1\0\1\11\7\10\2\0\6\10\2\11\2\10"+
"\1\0\4\10\2\0\12\10\3\11\22\0\1\10\1\11\1\10\33\11"+
"\3\0\33\10\65\0\46\11\13\10\u0150\0\3\10\1\0\65\11\2\0"+
"\1\10\1\11\20\10\2\0\1\11\4\10\3\0\12\11\2\10\2\0"+
"\12\10\21\0\3\10\1\0\10\11\2\0\2\11\2\0\26\11\1\0"+
"\7\11\1\0\1\11\3\0\4\11\2\0\1\10\1\0\7\10\2\0"+
"\2\10\2\0\3\10\11\0\1\10\4\0\2\11\1\0\3\11\2\10"+
"\2\0\12\10\4\11\16\0\1\10\2\0\6\11\4\0\2\11\2\0"+
"\26\11\1\0\7\11\1\0\2\11\1\0\2\11\1\0\2\11\2\0"+
"\1\10\1\0\5\10\4\0\2\10\2\0\3\10\13\0\4\11\1\0"+
"\1\11\7\0\14\10\3\11\14\0\3\10\1\0\7\11\1\0\1\11"+
"\1\0\3\11\1\0\26\11\1\0\7\11\1\0\2\11\1\0\5\11"+
"\2\0\1\10\1\11\10\10\1\0\3\10\1\0\3\10\2\0\1\11"+
"\17\0\1\11\5\0\12\10\21\0\3\10\1\0\10\11\2\0\2\11"+
"\2\0\26\11\1\0\7\11\1\0\2\11\2\0\4\11\2\0\1\10"+
"\1\11\6\10\3\0\2\10\2\0\3\10\10\0\2\10\4\0\2\11"+
"\1\0\3\11\4\0\12\10\22\0\2\10\1\0\6\11\3\0\3\11"+
"\1\0\4\11\3\0\2\11\1\0\1\11\1\0\2\11\3\0\2\11"+
"\3\0\3\11\3\0\10\11\1\0\3\11\4\0\5\10\3\0\3\10"+
"\1\0\4\10\11\0\1\10\17\0\11\10\21\0\3\10\1\0\10\11"+
"\1\0\3\11\1\0\27\11\1\0\12\11\1\0\5\11\4\0\7\10"+
"\1\0\3\10\1\0\4\10\7\0\2\10\11\0\2\11\4\0\12\10"+
"\22\0\2\10\1\0\10\11\1\0\3\11\1\0\27\11\1\0\12\11"+
"\1\0\5\11\4\0\7\10\1\0\3\10\1\0\4\10\7\0\2\10"+
"\7\0\1\11\1\0\2\11\4\0\12\10\22\0\2\10\1\0\10\11"+
"\1\0\3\11\1\0\27\11\1\0\20\11\4\0\6\10\2\0\3\10"+
"\1\0\4\10\11\0\1\10\10\0\2\11\4\0\12\10\22\0\2\10"+
"\1\0\22\11\3\0\30\11\1\0\11\11\1\0\1\11\2\0\7\11"+
"\3\0\1\10\4\0\6\10\1\0\1\10\1\0\10\10\22\0\2\10"+
"\15\0\60\11\1\10\2\11\7\10\4\0\10\11\10\10\1\0\12\10"+
"\47\0\2\11\1\0\1\11\2\0\2\11\1\0\1\11\2\0\1\11"+
"\6\0\4\11\1\0\7\11\1\0\3\11\1\0\1\11\1\0\1\11"+
"\2\0\2\11\1\0\4\11\1\10\2\11\6\10\1\0\2\10\1\11"+
"\2\0\5\11\1\0\1\11\1\0\6\10\2\0\12\10\2\0\2\11"+
"\42\0\1\11\27\0\2\10\6\0\12\10\13\0\1\10\1\0\1\10"+
"\1\0\1\10\4\0\2\10\10\11\1\0\42\11\6\0\24\10\1\0"+
"\2\10\4\11\4\0\10\10\1\0\44\10\11\0\1\10\71\0\42\11"+
"\1\0\5\11\1\0\2\11\1\0\7\10\3\0\4\10\6\0\12\10"+
"\6\0\6\11\4\10\106\0\46\11\12\0\47\11\11\0\132\11\5\0"+
"\104\11\5\0\122\11\6\0\7\11\1\0\77\11\1\0\1\11\1\0"+
"\4\11\2\0\7\11\1\0\1\11\1\0\4\11\2\0\47\11\1\0"+
"\1\11\1\0\4\11\2\0\37\11\1\0\1\11\1\0\4\11\2\0"+
"\7\11\1\0\1\11\1\0\4\11\2\0\7\11\1\0\7\11\1\0"+
"\27\11\1\0\37\11\1\0\1\11\1\0\4\11\2\0\7\11\1\0"+
"\47\11\1\0\23\11\16\0\11\10\56\0\125\11\14\0\u026c\11\2\0"+
"\10\11\12\0\32\11\5\0\113\11\225\0\64\11\40\10\7\0\1\11"+
"\4\0\12\10\41\0\4\10\1\0\12\10\6\0\130\11\10\0\51\11"+
"\1\10\u0556\0\234\11\4\0\132\11\6\0\26\11\2\0\6\11\2\0"+
"\46\11\2\0\6\11\2\0\10\11\1\0\1\11\1\0\1\11\1\0"+
"\1\11\1\0\37\11\2\0\65\11\1\0\7\11\1\0\1\11\3\0"+
"\3\11\1\0\7\11\3\0\4\11\2\0\6\11\4\0\15\11\5\0"+
"\3\11\1\0\7\11\17\0\4\10\32\0\5\10\20\0\2\11\51\0"+
"\6\10\17\0\1\11\40\0\20\11\40\0\15\10\4\0\1\10\40\0"+
"\1\11\4\0\1\11\2\0\12\11\1\0\1\11\3\0\5\11\6\0"+
"\1\11\1\0\1\11\1\0\1\11\1\0\4\11\1\0\3\11\1\0"+
"\7\11\46\0\44\11\u0e81\0\3\11\31\0\11\11\6\10\1\0\5\11"+
"\2\0\3\11\6\0\124\11\4\0\2\10\2\0\2\11\2\0\136\11"+
"\6\0\50\11\4\0\136\11\21\0\30\11\u0248\0\u19b6\11\112\0\u51a6\11"+
"\132\0\u048d\11\u0773\0\u2ba4\11\u215c\0\u012e\11\322\0\7\11\14\0\5\11"+
"\5\0\1\11\1\10\12\11\1\0\15\11\1\0\5\11\1\0\1\11"+
"\1\0\2\11\1\0\2\11\1\0\154\11\41\0\u016b\11\22\0\100\11"+
"\2\0\66\11\50\0\14\11\44\0\4\10\17\0\2\11\30\0\3\11"+
"\31\0\1\11\6\0\3\11\1\0\1\11\1\0\207\11\2\0\1\10"+
"\4\0\1\11\13\0\12\10\7\0\32\11\4\0\1\11\1\0\32\11"+
"\12\0\132\11\3\0\6\11\2\0\6\11\2\0\6\11\2\0\3\11"+
"\3\0\2\11\3\0\2\11\22\0\3\10\4\0";
* Translates characters to character classes
final private static char [] yycmap = yy_unpack_cmap(yycmap_packed);
* Translates a state to a row index in the transition table
final private static int yy_rowMap [] = {
0, 42, 84, 126, 168, 126, 210, 126, 252, 294,
336, 378, 126, 126, 420, 462, 504, 126, 126, 126,
126, 126, 126, 126, 126, 126, 126, 546, 126, 588,
126, 630, 672, 714, 756, 126, 126, 798, 840, 882,
126, 924, 966, 1008, 1050, 336, 1092, 1134, 1176, 1218,
126, 126, 126, 126, 126, 126, 126, 126, 126, 126,
126, 126, 126, 126, 1260, 1302, 1344, 1386, 1428, 1470,
1512, 1554, 126, 1596, 1638, 1680, 1722, 126, 126, 126,
126, 126, 126, 126, 1764, 294, 1806, 294, 294
* The packed transition table of the DFA
final private static String yy_packed =
"\1\4\1\5\2\6\1\7\1\10\1\11\1\12\1\4"+
"\1\12\1\13\1\14\1\4\1\15\1\16\1\4\1\17"+
"\3\12\1\20\3\12\1\21\1\22\1\23\1\24\1\25"+
"\1\26\1\27\1\30\1\31\1\32\1\33\1\34\1\35"+
"\1\36\1\37\1\40\1\41\1\12\1\42\1\43\1\44"+
"\12\42\1\45\1\42\1\46\32\42\1\47\1\50\1\51"+
"\13\47\1\4\1\52\32\47\54\0\1\6\53\0\1\53"+
"\1\54\52\0\1\12\1\55\4\12\4\0\11\12\20\0"+
"\1\12\6\0\6\12\4\0\11\12\20\0\1\12\12\0"+
"\2\56\1\57\47\0\2\14\1\57\43\0\6\12\4\0"+
"\1\12\1\60\7\12\20\0\1\12\6\0\6\12\4\0"+
"\5\12\1\61\3\12\20\0\1\12\6\0\6\12\4\0"+
"\2\12\1\62\6\12\20\0\1\12\43\0\1\63\54\0"+
"\1\64\51\0\1\65\51\0\1\66\3\0\1\42\2\0"+
"\12\42\1\0\1\42\1\0\32\42\2\0\1\44\47\0"+
"\2\67\1\0\12\67\1\70\1\71\1\72\1\73\1\74"+
"\2\67\1\75\3\67\1\76\20\67\1\77\15\0\1\100"+
"\36\0\1\51\47\0\2\67\1\0\12\67\1\101\1\102"+
"\1\103\1\104\1\105\2\67\1\106\3\67\1\104\20\67"+
"\1\107\1\53\1\110\1\111\47\53\52\112\6\0\6\55"+
"\4\0\11\55\20\0\1\55\12\0\2\57\44\0\6\12"+
"\4\0\2\12\1\113\6\12\20\0\1\12\6\0\6\12"+
"\4\0\6\12\1\114\2\12\20\0\1\12\6\0\6\12"+
"\4\0\6\12\1\115\2\12\20\0\1\12\15\0\1\116"+
"\51\0\1\117\51\0\1\120\51\0\1\121\51\0\1\122"+
"\51\0\1\123\51\0\1\124\36\0\1\111\47\0\5\112"+
"\1\125\44\112\6\0\6\12\4\0\3\12\1\126\5\12"+
"\20\0\1\12\6\0\6\12\4\0\7\12\1\127\1\12"+
"\20\0\1\12\6\0\6\12\4\0\6\12\1\130\2\12"+
"\20\0\1\12\4\112\1\111\1\125\44\112\6\0\6\12"+
"\4\0\3\12\1\131\5\12\20\0\1\12";
* The transition table of the DFA
final private static int yytrans [] = yy_unpack(yy_packed);
/* error codes */
final private static int YY_UNKNOWN_ERROR = 0;
final private static int YY_ILLEGAL_STATE = 1;
final private static int YY_NO_MATCH = 2;
final private static int YY_PUSHBACK_2BIG = 3;
/* error messages for the codes above */
final private static String YY_ERROR_MSG[] = {
"Unkown internal scanner error",
"Internal error: unknown state",
"Error: could not match input",
"Error: pushback value was too large"
* YY_ATTRIBUTE[aState] contains the attributes of state <code>aState</code>
private final static byte YY_ATTRIBUTE[] = {
0, 0, 0, 9, 1, 9, 1, 9, 1, 1, 1, 1, 9, 9, 1, 1,
1, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9, 1, 9, 1, 9, 1,
1, 1, 1, 9, 9, 1, 1, 1, 9, 1, 0, 0, 1, 0, 1, 1,
1, 1, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9, 9,
1, 1, 1, 1, 1, 1, 1, 1, 9, 0, 1, 1, 1, 9, 9, 9,
9, 9, 9, 9, 0, 1, 1, 1, 1
/** the input device */
private java.io.Reader yy_reader;
/** the current state of the DFA */
private int yy_state;
/** the current lexical state */
private int yy_lexical_state = YYINITIAL;
/** this buffer contains the current text to be matched and is
the source of the yytext() string */
private char yy_buffer[] = new char[16384];
/** the textposition at the last accepting state */
private int yy_markedPos;
/** the textposition at the last state to be included in yytext */
private int yy_pushbackPos;
/** the current text position in the buffer */
private int yy_currentPos;
/** startRead marks the beginning of the yytext() string in the buffer */
private int yy_startRead;
/** endRead marks the last character in the buffer, that has been read
from input */
private int yy_endRead;
/** number of newlines encountered up to the start of the matched text */
private int yyline;
/** the number of characters up to the start of the matched text */
private int yychar;
* the number of characters from the last newline up to the start of the
* matched text
private int yycolumn;
* yy_atBOL == true <=> the scanner is currently at the beginning of a line
private boolean yy_atBOL;
/** yy_atEOF == true <=> the scanner has returned a value for EOF */
private boolean yy_atEOF;
/** denotes if the user-EOF-code has already been executed */
private boolean yy_eof_done;
/* user code: */
StringBuffer string = new StringBuffer();
private InContestoParser mContesto = null;
private Symbol symbol(int type) {
return new JavaSymbol(type, yyline+1, yycolumn+1);
private Symbol symbol(int type, Object value) {
return new JavaSymbol(type, yyline+1, yycolumn+1, value);
private Symbol axSymbol(Object value) {
int tipo = 0;
CercaValore cercaVal = new CercaValoreComm(value.toString(),mContesto);
Ritorno rito = cercaVal.cercaValore();
int tipoSym = rito.getTipo();
if (tipoSym == Domini.tipoDatoNumerico) {
     tipo = AxSym.VAR_N;
else if (tipoSym == Domini.tipoDatoAlfanumerico) {
tipo = AxSym.VAR_A;
else if (tipoSym == Domini.tipoDatoBooleano) {
     tipo = AxSym.VAR_B;
JavaSymbol myJ = new JavaSymbol(tipo, yyline+1, yycolumn+1, value);
return myJ;
private Symbol axMetodo(Object value) {
int tipo = 0;
CercaValore cercaVal = new CercaValoreComm(value.toString(),mContesto);
Ritorno rito = cercaVal.cercaValore();
int tipoSym = rito.getTipo();
if (tipoSym == Domini.tipoDatoNumerico) {
     tipo = AxSym.MET_N;
else if (tipoSym == Domini.tipoDatoAlfanumerico) {
tipo = AxSym.MET_A;
else if (tipoSym == Domini.tipoDatoBooleano) {
     tipo = AxSym.MET_B;
JavaSymbol myJ = new JavaSymbol(tipo, yyline+1, yycolumn+1, value);
return myJ;
* Set the reader and reset variables
public void setReader(java.io.Reader in) {
this.yy_lexical_state = YYINITIAL;
this.yy_atEOF = false;
this.yy_atBOL = false;
this.yy_eof_done = false;
this.yy_state = 0;
this.yy_pushbackPos = 0;
this.yy_markedPos = 0;
this.yy_currentPos = 0;
this.yy_startRead = 0;
this.yy_endRead = 0;
this.yyline = 0;
this.yychar = 0;
this.yycolumn = 0;
this.yy_reader = in;
public void setContesto(InContestoParser xpContesto) {
mContesto = xpContesto;
public InContestoParser getContesto() {
return mContesto;
* Creates a new scanner.
* There is also java.io.Reader version of this constructor.
* @param in the java.io.Inputstream to read input from.
public AxScanner() throws java.io.IOException { this(System.in); }
* Creates a new scanner
* There is also a java.io.InputStream version of this constructor.
* @param in the java.io.Reader to read input from.
AxScanner(java.io.Reader in) {
this.yy_reader = in;
* Creates a new scanner.
* There is also java.io.Reader version of this constructor.
* @param in the java.io.Inputstream to read input from.
AxScanner(java.io.InputStream in) {
this(new java.io.InputStreamReader(in));
* Unpacks the compressed DFA transition table.
* @param packed the packed transition table
* @return the unpacked transition table
private static int [] yy_unpack(String packed) {
int [] trans = new int[1848];
int i = 0; /* index in packed string */
int j = 0; /* index in unpacked array */
while (i < 492) {
int count = packed.charAt(i++);
int value = packed.charAt(i++);
value--;
do trans[j++] = value; while (--count > 0);
return trans;
* Unpacks the compressed character translation table.
* @param packed the packed character translation table
* @return the unpacked character translation table
private static char [] yy_unpack_cmap(String packed) {
char [] map = new char[0x10000];
int i = 0; /* index in packed string */
int j = 0; /* index in unpacked array */
while (i < 1614) {
int count = packed.charAt(i++);
char value = packed.charAt(i++);
do map[j++] = value; while (--count > 0);
return map;
* Gets the next input character.
* @return the next character of the input stream, EOF if the
* end of the stream is reached.
* @exception IOException if any I/O-Error occurs
private int yy_advance() throws java.io.IOException {
/* standard case */
if (yy_currentPos < yy_endRead) return yy_buffer[yy_currentPos++];
/* if the eof is reached, we don't need to work hard */
if (yy_atEOF) return YYEOF;
/* otherwise: need to refill the buffer */
/* first: make room (if you can) */
if (yy_startRead > 0) {
System.arraycopy(yy_buffer, yy_startRead,
yy_buffer, 0,
yy_endRead-yy_startRead);
/* translate stored positions */
yy_endRead-= yy_startRead;
yy_currentPos-= yy_startRead;
yy_markedPos-= yy_startRead;
yy_pushbackPos-= yy_startRead;
yy_startRead = 0;
/* is the buffer big enough? */
if (yy_currentPos >= yy_buffer.length) {
/* if not: blow it up */
char newBuffer[] = new char[yy_currentPos*2];
System.arraycopy(yy_buffer, 0, newBuffer, 0, yy_buffer.length);
yy_buffer = newBuffer;
/* finally: fill the buffer with new input */
int numRead = yy_reader.read(yy_buffer, yy_endRead,
yy_buffer.length-yy_endRead);
if ( numRead == -1 ) return YYEOF;
yy_endRead+= numRead;
return yy_buffer[yy_currentPos++];
* Closes the input stream.
final public void yyclose() throws java.io.IOException {
yy_atEOF = true; /* indicate end of file */
yy_endRead = yy_startRead; /* invalidate buffer */
yy_reader.close();
* Returns the current lexical state.
final public int yystate() {
return yy_lexical_state;
* Enters a new lexical state
* @param newState the new lexical state
final public void yybegin(int newState) {
yy_lexical_state = newState;
* Returns the text matched by the current regular expression.
final public String yytext() {
return new String( yy_buffer, yy_startRead, yy_markedPos-yy_startRead );
* Returns the length of the matched text region.
final public int yylength() {
return yy_markedPos-yy_startRead;
* Reports an error that occured while scanning.
* @param errorCode the code of the errormessage to display
private void yy_ScanError(int errorCode) {
try {
System.out.println(YY_ERROR_MSG[errorCode]);
catch (ArrayIndexOutOfBoundsException e) {
System.out.println(YY_ERROR_MSG[YY_UNKNOWN_ERROR]);
System.exit(1);
* Pushes the specified amount of characters back into the input stream.
* They will be read again by then next call of the scanning method
* @param number the number of characters to be read again.
* This number must not be greater than yylength()!
private void yypushback(int number) {
if ( number > yylength() )
yy_ScanError(YY_PUSHBACK_2BIG);
yy_markedPos -= number;
* Contains user EOF-code, which will be executed exactly once,
* when the end of file is reached
private void yy_do_eof() throws java.io.IOException {
if (!yy_eof_done) {
yy_eof_done = true;
yyclose();
* Resumes scanning until the next regular expression is matched,
* the end of input is encountered or an I/O-Error occurs.
* @return the next token
* @exception IOException if any I/O-Error occurs
public java_cup.runtime.Symbol next_token() throws java.io.IOException {
int yy_input;
int yy_action;
while (true) {
boolean yy_counted = false;
for (yy_currentPos = yy_startRead; yy_currentPos < yy_markedPos;
yy_currentPos++) {
switch (yy_buffer[yy_currentPos]) {
case '\r':
yyline++;
yycolumn = 0;
yy_counted = true;
break;
case '\n':
if (yy_counted)
yy_counted = false;
else {
yyline++;
yycolumn = 0;
break;
default:
yy_counted = false;
yycolumn++;
if (yy_counted) {
if ( yy_advance() == '\n' ) yyline--;
if ( !yy_atEOF ) yy_currentPos--;
yy_action = -1;
yy_currentPos = yy_startRead = yy_markedPos;
yy_state = yy_lexical_state;
yy_forAction: {
while (true) {
yy_input = yy_advance();
if ( yy_input == YYEOF ) break yy_forAction;
int yy_next = yytrans[ yy_rowMap[yy_state] + yycmap[yy_input] ];
if (yy_next == -1) break yy_forAction;
yy_state = yy_next;
int yy_attributes = YY_ATTRIBUTE[yy_state];
if ( (yy_attributes & 1) > 0 ) {
yy_action = yy_state;
yy_markedPos = yy_currentPos;
if ( (yy_attributes & 8) > 0 ) break yy_forAction;
switch (yy_action) {
case 83:
{ yybegin(YYINITIAL); return symbol(AxSym.CHARACTER_LITERAL, new Character('\b')); }
case 90: break;
case 82:
{ yybegin(YYINITIAL); return symbol(AxSym.CHARACTER_LITERAL, new Character('\f')); }
case 91: break;
case 81:
{ yybegin(YYINITIAL); return symbol(AxSym.CHARACTER_LITERAL, new Character('\r')); }
case 92: break;
case 80:
{ yybegin(YYINITIAL); return symbol(AxSym.CHARACTER_LITERAL, new Character('\t')); }
case 93: break;
case 78:
{ yybegin(YYINITIAL); return symbol(AxSym.CHARACTER_LITERAL, new Character('\"')); }
case 94: break;
case 77:
{ yybegin(YYINITIAL); return symbol(AxSym.CHARACTER_LITERAL, new Character('\'')); }
case 95: break;
case 88:
{ return symbol(AxSym.BOOLEAN_LITERAL, new Boolean(false)); }
case 96: break;
case 87:
{ return symbol(AxSym.NULL_LITERAL); }
case 97: break;
case 85:
{ return symbol(AxSym.BOOLEAN_LITERAL, new Boolean(true)); }
case 98: break;
case 79:
{ yybegin(YYINITIAL); return symbol(AxSym.CHARACTER_LITERAL, new Character('\\')); }
case 99: break;
case 71:
case 72:
{ /* ignore */ }
case 100: break;
case 63:
{ yybegin(YYINITIAL); return symbol(AxSym.CHARACTER_LITERAL, new Character(yytext().charAt(0))); }
case 101: break;
case 62:
{ string.append( '\b' ); }
case 102: break;
case 61:
{ string.append( '\n' ); }
case 103: break;
case 60:
{ string.append( '\f' ); }
case 104: break;
case 59:
{ string.append( '\r' ); }
case 105: break;
case 58:
{ string.append( '\t' ); }
case 106: break;
case 57:
{ string.append( '\\' ); }
case 107: break;
case 56:
{ string.append( '\"' ); }
case 108: break;
case 55:
{ string.append( '\'' ); }
case 109: break;
case 25:
{ return symbol(AxSym.PLUS); }
case 110: break;
case 24:
{ return symbol(AxSym.COMMA); }
case 111: break;
case 23:
{ return symbol(AxSym.SEMI); }
case 112: break;
case 22:
{ return symbol(AxSym.RQUADRA); }
case 113: break;
case 21:
{ return symbol(AxSym.LQUADRA); }
case 114: break;
case 20:
{ return symbol(AxSym.RGRAFFA); }
case 115: break;
case 19:
{ return symbol(AxSym.LGRAFFA); }
case 116: break;
case 18:
{ return symbol(AxSym.RPAREN); }
case 117: break;
case 17:
{ return symbol(AxSym.LPAREN); }
case 118: break;
case 3:
case 37:
case 38:
case 41:
{ throw new RuntimeException("Illegal character \""+yytext()+"\" at line "+yyline+", column "+yycolumn); }
case 119: break;
case 4:
case 5:
{ /*return symbol(AxSym.INVIO);*/ /* ignore */ }
case 120: break;
case 6:
{ return symbol(AxSym.DIVIDE); }
case 121: break;
case 7:
{ return symbol(AxSym.TIMES); }
case 122: break;
case 8:
case 9:
case 14:
case 15:
case 16:
case 47:
case 48:
case 49:
case 74:
case 75:
case 76:
case 86:
{ return axSymbol(yytext()); }
case 123: break;
case 10:
case 11:
{ return symbol(AxSym.INTEGER_LITERAL, new Integer(yytext())); }
case 124: break;
case 12:
{ yybegin(STRING); string.setLength(0); }
case 125: break;
case 13:
{ yybegin(CHARLITERAL); }
case 126: break;
case 26:
{ return symbol(AxSym.MINUS); }
case 127: break;
case 27:
{ return symbol(AxSym.ORB); }
case 128: break;
case 28:
{ return symbol(AxSym.ANDB); }
case 129: break;
case 29:
{ return symbol(AxSym.GT); }
case 130: break;
case 30:
{ return symbol(AxSym.EQ); }
case 131: break;
case 31:
{ return symbol(AxSym.LT); }
case 132: break;
case 32:
{ return symbol(AxSym.NEG); }
case 133: break;
case 33:
{ string.append( yytext() ); }
case 134: break;
case 34:
case 35:
{ throw new RuntimeException("Unterminated string at end of line"); }
case 135: break;
case 36:
{ yybegin(YYINITIAL); return symbol(AxSym.STRING_LITERAL, string.toString()); }
case 136: break;
case 39:
case 40:
{ throw new RuntimeException("Unterminated character literal at end of line"); }
case 137: break;
case 44:
{ return axMetodo(yytext()); }
case 138: break;
case 46:
{ return symbol(AxSym.FLOATING_POINT_LITERAL, new Float(yytext())); }
case 139: break;
case 50:
{ return symbol(AxSym.DUEP); }
case 140: break;
case 51:
{ return symbol(AxSym.GE); }
case 141: break;
case 52:
{ return symbol(AxSym.LE); }
case 142: break;
case 53:
{ return symbol(AxSym.NE); }
case 143: break;
case 54:
case 64:
case 65:
case 66:
case 67:
case 68:
case 69:
case 70:
{ throw new RuntimeException("Illegal escape sequence \""+yytext()+"\""); }
case 144: break;
default:
if (yy_input == YYEOF && yy_startRead == yy_currentPos) {
yy_atEOF = true;
yy_do_eof();
{     return new java_cup.runtime.Symbol(AxSym.EOF);
else {
yy_ScanError(YY_NO_MATCH);
}

I setted use Javac checkbox and it worked ???
Could someone explain me what happened ?
The problem seems to be in the very long privated final string I defined, making it shorther the problem is solved again .
Tks
Tullio

No permission to copy file (to NAS with AFP support) - extended attributes?

For certain files that I copy from one of my drives to the NAS here (Synology 206j), ever since upgrading to Snow Leopard, Finder's behaviour has changed. It will simply refuse to copy the file, stating that "The operation can’t be completed because you don’t have permission to access some of the items."
The source is an external USB drive in Mac OS Extended format, I do have full permissions on the files and in any case the drive is set to ignore ownership.
The target is, like most NASes, in EXT3 format. It's sharing via its own AFP implementation.
I'd have tried repairing permissions, but for whatever reason, it's greyed out on my external drives. Since then I've figured that it was probably not that anyway, which will become apparent:
I tried copying the file via the terminal and it actually worked, but also gave an error: "cp: myfile: could not copy extended attributes to /Volumes/media backup/myfile: Operation not permitted"
This suggests to me that, as expected, the target volume doesn't support extended attributes. But rather than popping up with the message that Leopard did (something along the lines of "your target volume doesn't support extended attributes so your file's metadata may be lost, do you wish to continue") it just aborts instead.
I'm not sure if this is a Snow Leopard problem or a change that Synology need to catch up with. A workaround is to compress the file to ZIP first.
Thought I'd mention it here before trying to report it as a bug somewhere. Anyone else having similar issues, either with a NAS or some other storage, in which case please specify?
Message was edited by: Cloudane

Thanks guys, yeah I've been monitoring the netatalk mailing list myself: they're onto the same problem, have come to the same conclusions about it being Extended Attributes and have much better proof of such than I
It looks like they're currently debating the best way to fix it (pretending to support EAs but sending them to a black hole being the quick and dirty way, but I suspect they'll go for implementation)
It'll be a while for sure, but the Synology guys are very good with Mac support so I'm sure they'll apply the update fairly quickly once the netatalk crew get something public. FWIW, I did detect a certain sense of urgency from the netatalk discussions.
Although it's essentially answered, I'll leave the question marked as unanswered in case Apple come up with a better one
Message was edited by: Cloudane

"Error writing metadata to" message and extended attributes

After being frustrated by this error message in Bridge while trying to apply keywords to various image files I finally took the time to investigate, and I think I found the cause of the issue. In a nutshell, if the extend attribute "com.apple.FinderInfo" has not yet been created for a given file, then this message appears.
The start of the puzzle was that some files would take the keyword and others would not. After observing identical permissions on files that worked and files that did not, I noticed that in a terminal listing of the files in question, some files had extended attributes and some did not (extended attributes are identified by an @ symbol when running ls -la in a terminal window. For example:
-rw-rw-rw-@   1 mike staff 26131946 21 Jan 23:56 120114-133059-4612.cr2
-rw-rw-rw-    1 mike staff      5710 21 Jan 22:42 120114-133059-4612.xmp
-rw-rw-rw-@   1 mike staff 27200794 17 Jan 17:52 120114-133145-4613.cr2
-rw-rw-rw-    1 mike staff      5702 21 Jan 22:42 120114-133145-4613.xmp
-rw-rw-rw-@   1 mike staff 26973498 21 Jan 23:07 120114-133149-4614.cr2
-rw-rw-rw-@   1 mike staff      6648 21 Jan 23:19 120114-133149-4614.xmp
As you can see, the file called 120114-133145-4613.xmp has not extended attribute, but the file 120114-133149-4614.xmp does. The former throws an error when applying a keyword, the latter does not.
So I dug a bit further and it appears that when the file attribute called com.apple.FileInfo is missing from an xmp file, metadata cannot be witten. The contents of this extended attribute for a working XMP file look like this
$ xattr -l 120114-133058-4611.xmp
com.apple.FinderInfo:
00000000 54 45 58 54 43 52 61 77 00 00 00 00 00 00 00 00 |TEXTCRaw........|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020
According to specs I found googling, the first 4 bits identify the file type (TEXT), and the next four identify the file creator (CRaw). IOW no file-specific info seems to be present.
So as a test, I simply copied the contents of com.apple.FinderInfo from a file that had it to a file that didn't. Once the file that didn't received the new attribute, metadata writes worked. The command I used for the copy was
xattr -wx com.apple.FinderInfo "`xattr -px com.apple.FinderInfo 120114-133534-4633.xmp`" 120114-133041-4602.xmp
It also appears that this metadata is written by Bridge based on some unknown trigger, because occasionally during my investigation a file that previously would not take metadata suddenly did, and once I knew to look for extended attributes, in every case the file in question suddenly had com.apple.FinderInfo extended attribute.
So...I'm not sure if this is a bug in finder or in bridge, but it is definitely a bug and needs to be addressed.
...Mike

I have tried purging the cache, and also deleting it entirely and starting over, to no effect.
Mike
just did a quick try and don't know if it is the right way.
Using Lightroom 3.6 (not very familiar with Lightroom) and Bridge 4.0.5.11 on MacOSX 10.6.8
I randomly choose some CR2 files that where somewhere on my system and copied them to a new folder. Imported them in Lightroom and added some rating and a few keywords. (with setting metadata to XMP file active)
Then went to Bridge and opened the same folder. After caching Bridge showed the info as filed in Lightroom. Added some keywords to all files without problem. Went back to Lightroom (restarted it and had to choose read metadata menu. After this no problem to read new keywords form Bridge. But they only show in Italic because the have not been made persistent in the Bridge keyword list, however this is as expected behavior.
Tried a develop setting and that was also showing in Bridge correctly. Went a few times back and fort (files in Lightroom showing a memo with Exclamation sign top right of the in Bridge changed thumbnail asking for reading metadata).
Is this about the way you mean to describe?
And when having set Automatically export changes to XMP have you set this option in both Lightroom and Bridge (this s to be found in the Camera Raw preferences 'save image settings in: sidecar XMP')
And there are a few things to refresh also in Bridge besides the deleting of the cache file, you can also delete the Bridge plist file from the user library preferences and restart Bridge holding down option key and chose reset preferences. And did you run the check and repair permissions for your system also?
I tried to look in terminal but could not find a way to use the ls -la command on the folder with changed files so no comparing on that side I'm afraid.

Huh?: "Error processing extended attributes"

I just tried upgrading to the new versions of Quicktime and iTunes through "Software Update," and at the end of each one I got the following error messages: "NSURLErrorDomain -1005" (this was the message in the "Software Update" window) and "imac cp: error processing extended attributes: operation not permitted" (this was on the System log). Before this I have had no trouble upgrading new releases from Apple (like the Java update). The only thing I have done recently that may be causing a problem is that I downloaded OnyX system maintainence software and used it to run the daily, weekly, and monthly Apple maintainence scripts (the ones that are supposed to run early in the morning). Could that be causing the problem? Does anyone know why all of a sudden I would start having problems downloading Apple software updates? Any help would be greatly appreciated.
imac g3 400Mhz graphite 1G/80G Mac OS X (10.4.8)

A server for Software Update to connect from my node is up and running now. I confirmed it with "Software Update..." in the Apple menu and followed by two utilities as below.
Netstat menu (Network Utility) with "Display the state of all current socket connections":
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 192.168.1.2.51904 swscan.apple.com.http ESTABLISHED
A "netstat -an" command execution from Terminal application:
tcp4 0 0 192.168.1.2.51904 17.250.248.95.80 ESTABLISHED
Verify whether your ISP's DNS server is all right. Type "dig" and press a return key to see whether any odd events are returned.
But if it was a connection problem, would both downloads have completed up to the very end and then terminated?
That is strange. It seems that the server cannot verify some consistency on the filesystem on your client machine. I'll figure it out for some possible reasons after I read your posts.
Message was edited by: Fumiaki Kawashima

Cp leads to "error processing extended attributes: Argument list too long"

With certain PDF files to which I've added a lot of extended attributes (using Skim.app, a PDF reader/annotator which stores its notes in extended attributes), Chronosync and Finder drag-drops don't preserve extended attributes like they're supposed to (i.e. the notes aren't viewable on copies of the document). When I use cp to do they copying, the following message appears in system.log:
error processing extended attributes: Argument list too long
Googling it returns no results

Hi Derick,
error processing extended attributes: Argument list too long
I have no idea why you get this error when copying a file...
There is a max size for each extended attribute (about 3800bytes), and if I try to create (by using a simple C program) an attribute larger than this limit then I get "Argument list too long" error. But in your case you are trying to make a copy of an existing PDF file whose extended attributes should be smaller than the limit, of course (Skim has no magical power of creating an attribute larger than the limit; if the note is too large then I guess Skim just splits the note into two or more attributes).
Q1: do you get the error only if you (try to) copy a PDF file with large notes? or you also get the error for a file with only small notes? How about a PDF file with many small notes?
Q2: are you copying the PDF file to external volumes? If so, are you sure it is HFS+? What happens if you copy the PDF file to the same internal disk volume, for example
cp your.pdf tmp.pdf
PowerMacG4, PowerBookG4, iMac(C2D) Mac OS X (10.4.9)

SUNWspro iostream error while compiling with SunStudio 10

We are getting the following error when we try to compile the C++ code using SunStudio 10 on Sun Solaris Sparc server.
We made couple of changes in the source code 1) whereever we have stream.h we replaced it with iostream.h and 2) include fstream.h whereever required.
Can anyone tell us where did it go wrong.
+ /opt/SUNWspro/bin/CC -g -O -DHAWK -mt -lclntsh -lsocket -lnsl -I/export/home/StandardComponents/SC/include -I../../mylib -I../../include -I/opt/SUNWspro/prod/include/CC/Cstd -I. -I- -D_TRACE_ -c collectDborMtoInfo.c
"/opt/SUNWspro/prod/include/CC/Cstd/iostream.h", line 20: Error: Use ";" to terminate declarations.
"/opt/SUNWspro/prod/include/CC/Cstd/iostream.h", line 20: Error: A declaration was expected instead of "'\n'".
"/opt/SUNWspro/prod/include/CC/Cstd/iostream.h", line 20: Error: Use ";" to terminate declarations.
"/opt/SUNWspro/prod/include/CC/Cstd/iostream.h", line 20: Error: A declaration was expected instead of "'\n'".
4 Error(s) detected.

Remove the -I directive that points into the compiler installation. You should not have have -I or -L options that point into the compiler installation area, into /usr/include, or into /usr/lib. The CC compiler driver knows where to find system headers and libraries, and in what order to search the directories. If you force a different search order, you can break something.
If removing -I/opt/SUNWspro/prod/include/CC/Cstd does not fix the problem, compiling with -P or -E will show you the preprocessor output, and looking at the lines with the errors will usually show the source of the problem quickly.
BTW, you should be aware that the ".h" form of the C++ headers, like <iostream.h> and <fstream.h>, is not standard. Using them is not portable, because not all C++ implementations provide them, and those that do often have different content.

Critical Error while compiling with AIR16 (*.ipa export)

Hey,
my application crashed while compiling with AIR16. (Flex 4.13.0-AIR 16.0)
With AIR15 it works well.
First I thougt, the reason might be the included ANE, but it isnt. The ANE works fine with another project.
In fact other projects also work with AIR16.
Any ideas?
Error message:
Error occurred while packaging the application:
Undefined symbols for architecture armv7:
"_traits:AOTBuildOutput-0000000101_6:234::Span", referenced from:
      _AOTBuildOutput-0000000101_6:9729:Edge in AOTBuildOutput-0000000101_6.o
"_traits:AOTBuildOutput-0000000101_6:234::Edge", referenced from:
      _AOTBuildOutput-0000000101_6:9706:flashx.textLayout.compose::Parcel/allocateEdge in AOTBuildOutput-0000000101_6.o
"_traits:AOTBuildOutput-0000000100_5:18::LocaleID", referenced from:
      _AOTBuildOutput-0000000100_5:265:mx.resources::LocaleSorter$/sortLocalesByPreference in AOTBuildOutput-0000000100_5.o
ld: symbol(s) not found for architecture armv7
Compilation failed while executing : ld64
EDIT:
I tried it also with Flex 4.14.0-AIR 16.0. Got this message:
Error occurred while packaging the application:
Undefined symbols for architecture armv7:
"_traits:AOTBuildOutput-0000000101_6:248::Span", referenced from:
      _AOTBuildOutput-0000000101_6:11261:Edge in AOTBuildOutput-0000000101_6_1.o
"_traits:AOTBuildOutput-0000000101_6:248::Edge", referenced from:
      _AOTBuildOutput-0000000101_6:11238:flashx.textLayout.compose::Parcel/allocateEdge in AOTBuildOutput-0000000101_6_1.o
"_traits:AOTBuildOutput-0000000101_6:207::CellCoords", referenced from:
      _AOTBuildOutput-0000000101_6:8073:flashx.textLayout.elements::TableElement/normalizeCells in AOTBuildOutput-0000000101_6.o
      _AOTBuildOutput-0000000101_6:8072:flashx.textLayout.elements::TableElement/getBlockedCoor ds in AOTBuildOutput-0000000101_6.o
"_traits:AOTBuildOutput-0000000100_5:18::LocaleID", referenced from:
      _AOTBuildOutput-0000000100_5:340:mx.resources::LocaleSorter$/sortLocalesByPreference in AOTBuildOutput-0000000100_5.o
ld: symbol(s) not found for architecture armv7
Compilation failed while executing : ld64

We've built a lot of test-apps including the same components and libraries as in this app, but we are not able to reproduce this crash in other projects.
The project works fine in the Simulator without any crashes or compile errors!

PCC-S-02014 error while compiling with in Sun Solaris

We are porting our application from HP-UX to Sun Solaris and as part of that I am trying the compile a Pro*C program in Sun Solaris using SUNWspro C++ compiler. Precompiling is failing with following error.
PRECOMP set: /u01/app/oracle/product/10.2.0/bin/proc dbms=native code=cpp mode=ansi include=/u01/app/oracle/product/10.2.0/precomp
ireclen=255 oreclen=255
define=__sparc define=__SUNPRO_C include=/usr/include include=. include=/u01/app/SUNWspro/prod/include/CC/stlport4 include=/u01/app/oracle/product/10.2.0/rdbms/public/ include=/u01/app/oracle/product/10.2.0/network/public/ include=/u01/app/oracle/product/10.2.0/rdbms/demo/ errors=yes select_error=no
sqlcheck=limited ltype=NONE
release_cursor=no hold_cursor=no
Pro*C/C++: Release 10.2.0.3.0 - Production on Thu Dec 18 03:09:59 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
System default option values taken from: /u01/app/oracle/product/10.2.0/precomp/admin/pcscfg.cfg
Syntax error at line 44, column 30, file /u01/app/SUNWspro/prod/include/CC/stlport4/algorithm:
Error at line 44, column 30 in file /u01/app/SUNWspro/prod/include/CC/stlport4/a
lgorithm
# include STLPNATIVE_HEADER(algorithm)
.............................1
PCC-S-02014, Encountered the symbol "(" when expecting one of the following:
: [ ] + / . .. an identifier, a numeric constant, newline,
define, elif, else, endif, error, if, ifdef, ifndef, include,
line, pragma, undef, exec, sql, begin, end, var, type,
oracle, an immediate preprocessor command, a C token, create,
function, package, procedure, trigger, or, replace,
Normal C++ files are getting compiled with out eny issues. This particular file is having functions written in C fashion. Any idea what is missing in the compiler option.
regards
Vinu

Hi Vinu,
I'm not sure if this is still an issue for you. When I have encountered issues like this with Pro*C I have ended up specifying parse=none to the proc command and then putting all declarations between "EXEC SQL BEGIN DECLARE SECTION" and "EXEC SQL END DECLARE SECTION" markers. I have also moved any "special" declarations into a specific header file and then placed the "#include <special header file>" inside the declare section as well.
Perhaps that will help a bit,
Regards,
Mark

Error compiling with extends attribute

Similar Messages

Maybe you are looking for