I am sure it can - we just had the same problem with batik.jar. In fact, to see weirdness being even weirder, copy the exact batik jar files from the flex/jars into your regular WEB-INF/jars - you would think duplicate but OK - unfortunately Flex does not like that. As soon as you access mxml pages that need to be recompiled, it gives weird error messages like being unable to find global.css etc.
Jonathan On 5/4/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > Our flex application shares it's web app with another application that > requires crimson.jar in the WEB-INF/lib directory. I found that this creates > a conflict for the parser required for the mxmlc compiler & the compiler > fails. If I exclude crimson.jar from the classpath during compile time, I am > able to compile the swf. > > My question is, does anyone know if having crimson.jar live in the flex web > app could create other conflicts with flex during runtime? I am able to run > the application with no problems that I can see, but am not sure what is > going on under the hood and if there are other gotchas that I should be > aware of. > > thanks in advance for your help, > > Laura > ________________________________ > Yahoo! Groups Links > > > To visit your group on the web, go to: > http://groups.yahoo.com/group/flexcoders/ > > To unsubscribe from this group, send an email to: > [EMAIL PROTECTED] > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
