On Jul 4, 2007, at 3:30 PM, Simon McLean wrote:
On 4 Jul 2007, at 23:15, Chuck Hill wrote:
However, i think there is a bug in there somewhere. If i switch
the validate options back on i see errors everywhere again. But
when I turn it off the errors stay. Reboot eclipse / clean
everything = no change. There is a workaround: if i open each
affected component (by double clicking the .wo - not the error,
which only opens the affected file rather than the whole .wo) the
errors vanish. It's as if the errors are only refreshed when the
component is opened.
I think that is correct. The validation is rather expensive so it
is only done on certain triggers. I think Mike mentioned maybe
adding a "validate all now" function. But with a new iPhone and a
real job I would not hold my breath. You could phone him and
ask... :-)
Chuck
Hi Chuck -
A "validate all now" function would be great, but I've got a couple
of projects that have stubborn errors that seem to only response to
a fresh check-out.
That might also be an Eclipse bug. Guido posted some Eclipse state
files that you can try deleting.
Any idea why I'm getting so many errors when i switch those options
on ?
No.
(is my html code really that bad ?!!
Mayb, :-)
Or to be more precise, is WOBuilder's html code really that bad ?!!).
Hell Yes!
The Validate WOD / Inline Bindings option causes by far the most
problems.
Do you have protected variables with no get/set methods? Those are
disallowed by design.
Chuck
--
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/products/practical_webobjects
_______________________________________________
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]
