|
Ah, hopefully it will be a little better
in 2.0. Unfortunately compiler errors are really hard to get right because it’s
often impossible to determine the intent of the user when the error is
encountered. From: It got solved yesterday, when checking some recently changed
files. As restarting Flex/JBoss/computer didn't worked, I did some
debugging, and it happened to be an undeclared variable (named aux) that
Flex was interpreting as a class, and therefore looking for it in the
user_classes directory. Just added the preceding "var" to it and
done. Although it was something really stupid, I guess a more
describing error message could have helped a lot. =) Thanks! ---Pablo Gustavo Apanasionek De: That seems very odd, what happens when you
restart JBoss? From: Hi everyone! Has any of you ever bumped into this while building/browsing
a MXML file? I'm using JBoss 4.0.2 and Flex 1.5. It was running perfectly a few
hours ago, and nothing changed in my configuration (at least, that I could
notice). 2 Errors found. Error reading MXML
document: check that the file exists and permissions are set correctly.
Don't know how to parse element "http://www.macromedia.com/2003/mxml:WebService".
It is not a known type or a property of mx.core.Application. In the first case, the file aux.mxml doesn't even exist. Is
this file generated by the compiler? What permissions should the flex-dir have? Thanks in advance! ---Pablo Apanasionek
|
