I think that was part of it. And the use of the default package is now
deprecated in Java so properly every class name should have a package anyway.
My feeling is that FQ names in the model is just The Right Thing.
On Sep 10, 2010, at 12:53 PM, Mike Schrag wrote:
> Good call .. You're right
Good call .. You're right, and maybe that was part of the reason we recommended
the change? It's completely a blur now.
ms
On Sep 10, 2010, at 3:40 PM, Chuck Hill wrote:
> Then you would have the problem of possibly getting the wrong class. My
> preference is for FQ names in the model. Other
Then you would have the problem of possibly getting the wrong class. My
preference is for FQ names in the model. Otherwise, how doe veogen know where
to put the classes?
Chuck
On Sep 10, 2010, at 12:29 PM, Mike Schrag wrote:
> I seem to recall Wonder changed this to enforce that you use ful
I seem to recall Wonder changed this to enforce that you use fully-qualified
class names because not everything in EOF actually properly does an
_NSUtilities.classNamed call. We probably could automagically rewrite your
class names at startup if they're simple names, though ... I'll think about
Thanks Chuck for correction.
Mike, AppUser.class.getSimpleName() should give the non FQ class name.
Farrukh
On 10, ستمبر 2010, at 10:01 PM, Chuck Hill wrote:
>
> On Sep 10, 2010, at 11:58 AM, Michael Gargano wrote:
>
>> ENTITY_NAME is the class name
>
> Also wrong. :-)
>
> There are three
the reason I thought it was the source is because it was complaining about a FQ
class name. it was actually that I needed to but the FQ class name in the
model. Never had to do that before, but this is my first wonder app, so I
guess the ER stuff is different. normal, i'd just map the models
On Sep 10, 2010, at 11:58 AM, Michael Gargano wrote:
> ENTITY_NAME is the class name
Also wrong. :-)
There are three names, all of which can be different:
1. Entity: User
2. Class: com.foo.bar.User
3. Table: MyUser
> , but still is not a substitute for getName() as that gives the FQ class na
ENTITY_NAME is the class name, but still is not a substitute for getName() as
that gives the FQ class name
Sent from my iPhone
On Sep 10, 2010, at 2:55 PM, Farrukh Ijaz
wrote:
> Hi,
>
> Try moving the classes inside a java package instead of the default package.
> AppUser.ENTITY_NAME repres
On Sep 10, 2010, at 11:55 AM, Farrukh Ijaz wrote:
> Hi,
>
> Try moving the classes inside a java package instead of the default package.
> AppUser.ENTITY_NAME represents the table name
No, it represents the Entity name. The Entity and Table names may be
different.
> hence can't be replaced
Hi,
Try moving the classes inside a java package instead of the default package.
AppUser.ENTITY_NAME represents the table name hence can't be replaced with
AppUser.class.getName()
Farrukh
Sent from my iPhone
On 10, ستمبر 2010, at 9:22 PM, Michael Gargano wrote:
> the classes are in packages
Are the packages also set up in the EOModel? Use something like JarInspector
to see what classes are where in what is running.
On Sep 10, 2010, at 11:22 AM, Michael Gargano wrote:
> the classes are in packages under the sources folder. I was using AppUser.
> ENTITY_NAME which is not FQ, but
the classes are in packages under the sources folder. I was using AppUser.
ENTITY_NAME which is not FQ, but I also replaced that with
AppUser.class.getName() and I got the same error. I'm stumped. This isn't a
complicated app.
Sent from my iPhone
On Sep 10, 2010, at 2:19 PM, Chuck Hill wro
Are the class names in the model fully qualified? Are the Java classes in
packages and under the Sources folder?
On Sep 10, 2010, at 11:17 AM, Michael Gargano wrote:
> no, I the project's resource folder. it's getting pulled into the build.
>
> Sent from my iPhone
>
> On Sep 10, 2010, at 2:
no, I the project's resource folder. it's getting pulled into the build.
Sent from my iPhone
On Sep 10, 2010, at 2:13 PM, Chuck Hill wrote:
> That sounds like you have the model in the project but not the code. Is this
> model in a framework?
>
>
> On Sep 10, 2010, at 11:11 AM, Michael Ga
That sounds like you have the model in the project but not the code. Is this
model in a framework?
On Sep 10, 2010, at 11:11 AM, Michael Gargano wrote:
> Yes, all of the above. :)
>
> AppUser
> user=(AppUser)EOUtilities.objectMatchingValues(session().defaultEditingContext(),AppUser.ENTITY_
Yes, all of the above. :)
AppUser
user=(AppUser)EOUtilities.objectMatchingValues(session().defaultEditingContext(),AppUser.ENTITY_NAME,loginDict);
Error is ERROR er.extensions.eof.ERXEntityClassDescription - Error registering
model: PerfTestEOModel
ClassNotFoundException: AppUser
it's a
Details? Code? Exceptions? Hints?
On Sep 10, 2010, at 10:59 AM, Michael Gargano wrote:
> hi all,
>
> I'm having an issue with EOUtilities.objectMatchingValues... it keeps
> giving me ClassNotFoundExceptions telling me it cannot find the class for the
> entity. I tried entity.ENTITY_NAME
hi all,
I'm having an issue with EOUtilities.objectMatchingValues... it keeps giving
me ClassNotFoundExceptions telling me it cannot find the class for the entity.
I tried entity.ENTITY_NAME and entity.class.getName(). and nothing, it tells
me I need the FQ class name still. (this is a wo
18 matches
Mail list logo
