| Thank you, thank you, thank you. I actually did try adding it to both the Application Server and the Applicationname tagets, but didn't try Application Server only. I never have quite gotten my arms around the different targets. Actually I think I have understood them in the past, but by the time I have trouble with them again (like now) I've forgotten quite what the nuances are between them.
Thanks again, Jeff On Apr 6, 2006, at 9:15 PM, Art Isbell wrote: On Apr 6, 2006, at 4:06 PM, netBrackets wrote: I simply want to add a new Java class to my webojbects project in xcode. I choose File->New File and pick Webobjects Java Class as the type of file in the wizard. I add it to my ApplicationName target and neither of the other ones. The java file is created fine and looks like this:
import com.webobjects.foundation.*; import com.webobjects.eocontrol.*;
public class temp {
}
Then, when I compile my build, making no other changes to the file, I get a compiler error that the imported packages in the new class (temp) don't exist. I have many other Java classes in this same project which import these same exact packages, and they compile fine. How can this be???
Because JavaFoundation.framework and JavaEOControl.framework are not in the ApplicationName target (nor should they be). I can't think of a reason why a Java source file would ever be in the ApplicationName target. Try removing temp.java from the ApplicationName target and adding it to the Application Server target which should also contain JavaFoundation.framework and JavaEOControl.framework.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Help/Unsubscribe/Update your Subscription:
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
