Re: Weird case of "The requested application was not found on this server"

Chuck,

On Feb 16, 2012, at 6:46 AM, Chuck Hill wrote:

>>> Yes, that sounds correct.  The /-whatever URLs are for development =
when you are only running a woadaptor and wotaskd but no JavaMonitor.  =
They are most likely ignored or stripped out resulting in an effective =
URL of http://localhost/cgi-bin/WebObjects/Foo.woa.  You can go to =
http://localhost:1085 to see what has been registered as available with =
wotaskd.
>>=20
>> Well I deploy and develop both on the same machine -- that is not =
allowed?
>=20
> Yes, it is allowed, but I fear things will get confused if you use the =
same app name for development and deployment on the same machine.  You =
can make the app name not match the .woa name in the file system in =
JavaMonitor.  That would probably work around this for you.

I see. Thanks a lot -- if I don't mess up the names (and if I make sure =
to use the -WOLifebeat* arguments when manually run applications, which =
I am afraid I've forgot the last time) it runs perfectly now.

>>>> And one quite unrelated question -- is there a way to get rid of =
the superfluous "Display groups are defined for component FOO.wo but =
class was not found" errors? They get reported for all my groovy =
components (and they are wrong, the classes are build all right and the =
app works with them without a glitch).
>>>=20
>>> Check the contents of the .woo file (it is text).
>>=20
>> The woos are all right, the editor shows the proper settings and the =
application works exactly as it should. If I rename the groovy =
components to java, the errors disappear. Looks like the WOO compiler, =
instead of checking in the .class files whether the classes are =
available tries to parse .java or something like that.
>=20
> It may, I am not sure how it works.

Nor am I, which is why I'd like just to switch the error report off -- =
but can't find how to. Or is it not possible at all?

BTW I've just bumped into another completely weird behaviour of the IDE: =
if I change a (groovy) source, _sometimes_ I just select "Build Project" =
from the context menu and the source is compiled and changes are =
injected to the running app. Just about perfect.

Nevertheless the next time not only this does not work, but not even =
re-launching the app works, and the only way to make the changes to be =
reflected in the running application is to Project / Clean...! Far as I =
can say, no difference in the IDE or console: simply yesterday did work, =
today does not :(

Drives me completely mad. Any idea what the culprit might be, or at =
least, how to find it? Are the some detailed build logs somewhere, which =
may perhaps lead to pointing out the problem?

Thanks and all the best,
---
Ondra =C4=8Cada
OCSoftware:     [email protected]               http://www.ocs.cz
private         [email protected]             http://www.ocs.cz/oc