This content has been marked as final. Show 3 replies
Creat your component in a Flex Library Project and put the .swc under the folder "user_classes" so that you can load it into your MXML applications anywhere as long as they are in the same J2EE server.
Thanks for the suggestion. That would work for a "finished" library, but the project is very dynamic and there are constant changes to the component classes and the application(s) that use them...
I consider this to either be a pretty substantial design flaw if you can't properly reference classes/components in other packages from within the same project. This is definitely a major issue, since there doesn't appear to be a workaround besides what you've suggested.
Appreciate the info!
Well, in the project properties it allows to add more applications to the project - therefore assuming that multiple applications should be allowed to run within the same project. It should be noted however that only the default application shows in the window even though the application file is marked as a project application in the Navigator window.... I believe that is a bug in Flex Builder....
But, like Rick, I am having the same classpath problems within Flex Builder. Unless I add the project folder as a source folder in the project, Flex Builder CANNOT find the files. This seems a bit silly considering the files are right there, with the correct path in the project.
Is there a solution to this? Am I missing some step in setting up my project that would allow it to find files in the project? Or is this a bug? Is there a bug database that I can look this up at?