On 2012-09-10, at 11:09 AM, Ângelo Andrade Cirino wrote:

> Hi Chuck,
> 
> Em 10/09/2012, às 14:16, Chuck Hill escreveu:
> 
>> I don't think that Eclipse is to blame for all of them (UTF-8 in the path 
>> excepted).  I think you are just blaming Eclipse for problems whose source 
>> lies elsewhere.
>> 
>>> For instance, one application with ERAttachments that was working, after I 
>>> experimented some changes in the database with migrations,
>> 
>> Did you change the model?
>> That looks like a model / MySQL problem, not something caused by Eclipse.
> 
> No, I did not change the model. I just experimented migrations with 
> postUpgrade creation of new entities, step after step, one entity, then other 
> and so on, until I stumbled on a specific one that caused me trouble. I 
> revised the model and tried some advices for MySQL configuration but found no 
> solution.
> 
>> 
>> Because the reason is not apparent to you, does not mean that the reason is 
>> Eclipse.  Most of us here use it on a daily basis and we don't have these 
>> problems.  If we did, we would fix it.
> 
> I understand that there is a lot of people running Eclipse successfully on a 
> daily basis. When I have this kind of problem my first thought is: what is my 
> mistake? Then I look for errors I could have made. I normally put the blame 
> on myself first, perhaps a problem of a low esteem programmer…
> 
>> 
>> See java.lang.NoClassDefFoundError: 
>> com/webobjects/_eoproject/_WBInterfaceDescriptor.  That means that the 
>> JavaEOProject framework needs to be added to the project you are generating 
>> SQL from.  I think this may only be added to Application projects by 
>> default.  Or perhaps you removed it?
> 
> The model is in the framework I made specifically to hold it, alongside with 
> the rules I use (I created a rule file for each entity and load them in the 
> properties file). The framework indeed do not have JavaEOProject for default, 
> probably because the project template doesn't include it. I added it to the 
> framework and the error persists.

I think that if you look closely, you will see that the error message is 
different.  You are missing another framework too.  JavaEOProject usually goes 
with one or two others, I don't recall the names.  The error message should 
hint at them.



>> Without seeing the full log, I can't guess why.  But differences in the 
>> frameworks included in each project could be the reason.  Frameworks used by 
>> a Framework project are NOT available to an Application project.  They need 
>> to be added to the Application project as well.
>> 
>> 
>>> I even used Practical Web Objects' EOFJDBCConnectionAnalyzer to debug the 
>>> connection with no luck in finding the problem. The third application will 
>>> connect to the database but ERAttachments will raise PK exceptions. All 
>>> based on the same framework.
>> 
>> Something is different.  :-)
> 
> I have three applications that use the models framework, the three do not 
> touch the model and show different behaviors. Two of the applications are D2W 
> apps where the differences between them are the entities they work with and 
> the rule files specific for each. These are the administrative backend 
> applications. The third application is a regular DirectAction-based WO 
> application that will be the store-front for our customers' customers (bad 
> English here?).

Your English is correct.  Check that each of them includes the same frameworks. 
 If they are the same, are they in a different order (I don't know if that 
matters, but it is something to look at).


> 
>> 
>> 
>>> One of the problematic applications I was able to start from scratch by 
>>> deleting the project and its files, copying a different working one and 
>>> modifying it with the classes and user interface I started developing for 
>>> the former. My feeling is that Eclipse is the cause of the problems and I 
>>> am starting to hate it.
>> 
>> No, Eclipse is not the cause of these problems.  
>> 
>> 
>> Chuck
> 
> I can assure you that creating a new workspace and copying the projects to it 
> sometimes solved the problems I was having. If this is not a workspace 
> problem I do not know what could cause it. Maybe my environment, my Java 
> installation, other extensions or something in the system is causing the 
> problems. I am seriously considering buying a HD to do a clean install of 
> Mountain Lion and dedicate it to Eclipse development.


Sometimes workspaces do get corrupted.  But it is a daily or weekly thing.  Not 
even monthly for me.  You might want to check your machine for memory or hard 
drive errors.

Chuck


-- 
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall 
knowledge of WebObjects or who are trying to solve specific problems.    
http://www.global-village.net/gvc/practical_webobjects









 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to