I had a similar problem once. Back then the DirectAction class was "overshadowed" by a class with the same name, but in a different package. Forexample: the direct action class User and the enterprise object User - the enterprise class then blocked the direct action, problably because it was found before the other class.
Cheers Tonny On Dec 16, 2007 4:20 PM, Mike Schrag <[EMAIL PROTECTED]> wrote: > > your DirectAction class should be in anonymous package. > > otherwise url will be like > > wa/my.package.DirectAction/welcome > This is actually not true ... DirectAction does not need to be > packageless and you do not need to fully qualify its name. By > default, it MAY look for it in the same package as Application, but I > don't recall. I would give pretty good odds that it just uses > _NSUtilities.classWithName (or whatever it's called) and looks it up > without regard for package (like the way WOComponents work). > > ms > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/mezz.dk%40gmail.com > > This email sent to [EMAIL PROTECTED] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
