D
dbeavon
Guest
Thanks for the tips Marian, I am very open to the possibility that it is a platform-specific issue on HP-UX since there have been quite a number of those. In fact I've almost stopped developing on HP-UX altogether since it seems to be such an odd duck. I wouldn't go near it at all except for the fact that we still use it in production. Your other tips about the possibility of PROPATH and namespace problems are also interesting. They might explain why the on-the-fly compilation was a little bit happier when I started to use fully-qualified namespaces for my class names. I thought the USING statements would be enough to resolve the location of my classes for the compiler (especially since Progress requires that class names and namespaces align with filenames and paths). It sounds like you might have had some of these types of experiences yourself. Have you ever come across code that Progress OE didn't accept when using "on-the-fly" compilation but was happy to compile into r-code? This may be a first for me. The weirdest part (IMHO) was the (1) platform-specific behavior, and the (2) difference in behavior between state-reset appserver and running the same code in the editor (whereby neither scenario uses r-code). But then, like you said, I may be overlooking some subtle environment variable or another subtle environment-related factor. I was hoping someone would pipe in and say they know about a specific KB/bug related to either the message "incompatible data types" or the message that seems to preceed it ("Could not locate method...with matching signature in class"). But I suppose that the problem my involve *both* the use of OO *and* HP-UX, in which case I may be on my own. 
I will package up the project and send it off to support when I have some spare time. Hopefully Progress still has an HP-UX server sitting around somewhere. Fortunately we always run compiled classes in production. I guess for now I will also have to compile in development too.
Continue reading...
I will package up the project and send it off to support when I have some spare time. Hopefully Progress still has an HP-UX server sitting around somewhere. Fortunately we always run compiled classes in production. I guess for now I will also have to compile in development too.Continue reading...