Re: Eclipse source of problems?
Re: Eclipse source of problems?
- Subject: Re: Eclipse source of problems?
- From: Chuck Hill <email@hidden>
- Date: Mon, 10 Sep 2012 22:02:46 -0700
On 2012-09-10, at 1:48 PM, Ângelo Andrade Cirino wrote:
> Dear Pascal and Chuck,
>
> The frameworks order solved my problem. But I remain with two other problems. First I still get an error trying to generate SQL:
>
> java.lang.RuntimeException: Failed to generate SQL.
> at org.objectstyle.wolips.eomodeler.core.sql.EOFSQLGeneratorFactory$ReflectionSQLGenerator.generateSchemaCreationScript(EOFSQLGeneratorFactory.java:67)
> at org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog.generateSql(GenerateSQLDialog.java:298)
> at org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog$1.run(GenerateSQLDialog.java:279)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.objectstyle.wolips.eomodeler.core.sql.EOFSQLGeneratorFactory$ReflectionSQLGenerator.generateSchemaCreationScript(EOFSQLGeneratorFactory.java:65)
> ... 3 more
> Caused by: java.lang.NullPointerException
> at com.webobjects.jdbcadaptor.JDBCContext._fetchJDBCInfo(JDBCContext.java:600)
That sounds related to MySQL. I will have to let someone else address that.
> at com.webobjects.jdbcadaptor.JDBCPlugIn.jdbcInfo(JDBCPlugIn.java:1046)
> at com.webobjects.jdbcadaptor._MySQLPlugIn.jdbcInfo(_MySQLPlugIn.java:715)
> at com.webobjects.jdbcadaptor.JDBCAdaptor.jdbcInfo(JDBCAdaptor.java:233)
> at com.webobjects.jdbcadaptor.JDBCExpressionFactory.createExpression(JDBCExpressionFactory.java:26)
> at com.webobjects.eoaccess.EOSQLExpressionFactory.expressionForString(EOSQLExpressionFactory.java:79)
> at com.webobjects.eoaccess.synchronization.EOSchemaSynchronizationFactory._expressionForString(EOSchemaSynchronizationFactory.java:1003)
> at com.webobjects.jdbcadaptor._MySQLPlugIn$MySQLSynchronizationFactory.dropPrimaryKeySupportStatementsForEntityGroups(_MySQLPlugIn.java:593)
> at com.webobjects.eoaccess.synchronization.EOSchemaSynchronizationFactory.schemaCreationStatementsForEntities(EOSchemaSynchronizationFactory.java:872)
> at com.webobjects.eoaccess.synchronization.EOSchemaSynchronizationFactory.schemaCreationScriptForEntities(EOSchemaSynchronizationFactory.java:685)
> at com.webobjects.eoaccess.EOSynchronizationFactory.schemaCreationScriptForEntities(EOSynchronizationFactory.java:233)
> at org.objectstyle.wolips.eomodeler.core.sql.EOFSQLGenerator53.generateSchemaCreationScript(EOFSQLGenerator53.java:483)
> ... 8 more
>
> And I wonder why does the embedded EOModeler interact with the frameworks and libraries of the project. Shouldn't it be independent of the build path of the project?
The code to generate the SQL is part of WebObjects, not part of the WOLips plugin of Eclipse. It needs to be able to load parts of WebObjects to generate the SQL. Making it independent would require re-implementing part of WebObjects in WOLips. Possibly illegal and certainly a lot of work for the benefit.
> Second, I have to figure out why a rule file that is loaded with er.directtoweb.ERD2WModel.additionalModelNames in the properties file isn't loaded.
Sorry, can't help you with that either.
Chuck
>
> Em 10/09/2012, às 15:47, Pascal Robert escreveu:
>
>> Like Chuck said, it's not a "Eclipse" problem. It might be a class path problem, a configuration problem, or other reason, but don't re-install everything! From experience of helping people with Eclipse, most of the time, re-installing everything is creating more problems than it solves.
>>
>> The first thing you should do is to compare the class path of your working project with the class path of the non-working class paths. You can do it with the diff command-line tool, like this:
>>
>> diff project1/.classpath project2/.classpath
>>
>> Since you're using MySQL, make sure to use the plugin coming from Project Wonder, and that in the class path, MySQLPlugIn is higher than the WO frameworks (Java*.framework).
>>
>> If that doesn't solve the issues, compare the Properties file of each project.
>
--
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden