• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Eclipse Woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Eclipse Woes


  • Subject: Re: Eclipse Woes
  • From: Lachlan Deck <email@hidden>
  • Date: Wed, 21 Nov 2007 14:11:38 +1100

On 21/11/2007, at 8:29 AM, Fred Shurtleff wrote:

SEE BELOW - and thanks for your help!

No problems...

Lachlan Deck wrote:
I assume testObject is public?
Are any child components also trying to reference testObject?

It was NOT public. So changing this + other bindings in the .wod file to Public fixed the problem.

Aha! seemed almost too obvious to mention. Just as well my fingers kept typing ;-)


Another example, I have a link with an action class & directActionName binding (DirectAction & Page1Action), and Eclipse reports:
Error: java.lang.NoSuchMethodException: com.webobjects.appserver.WODirectAction.page1Action()
But this action is in fact in the DirectAction class.

Yeah this is a problem with the normal Direct action request handler's class resolving being a bit dumb. It doesn't resolve DirectAction to your.apps.DirectAction class... and so defaults to com.webobjects.appserver.WODirectAction which is your superclass.


The solution for this involves assisting WO in finding /your/ direct action classes by adjusting the request path when needed... similar to how I offered a fix for finding the session class you mentioned below which Keiran had reposted...

So, the way I've gone around this one is to subclass com.webobjects.appserver._private.WODirectActionRequestHandler (or er.extensions.ERXDirectActionRequestHandler... either will do) so now AnyActionClass.withSomeAction resolves to your.app.AnyActionClass etc. Not sure how others are solving this, but this works reliably and is in production apps if that helps.

I get the drift & will check it out. It just seems odd to have to use this measure. Rather I would expect that Eclipse's search path should be the project first and then those items outside the project on the classpath.

This is not an eclipse problem but a WO runtime problem. (i.e., _NSUtilities)


with regards,
--

Lachlan Deck

_______________________________________________
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


References: 
 >Eclipse Woes (From: Fred Shurtleff <email@hidden>)
 >Re: Eclipse Woes (From: Lachlan Deck <email@hidden>)
 >Re: Eclipse Woes (From: Fred Shurtleff <email@hidden>)

  • Prev by Date: Using the built-in Velocity EOGenerator?
  • Next by Date: Velocity vs. JavaEOGenerator - I'm learning to hate both of them...
  • Previous by thread: Re: Eclipse Woes
  • Next by thread: Re: Eclipse Woes
  • Index(es):
    • Date
    • Thread