RE: [flexcoders] crimson.jar flex runtime

2005-05-05 Thread laura . donia



Hi Peter,

I checked the web.xml and the AMFGatewayServlet is loaded by a BootstrapServlet.

Regarding sending XML over RemoteObject: No, we are not directly sending XML over the RemoteObject. We are using the RemoteObject to just call java methods on the app server. My concern was that I didn't know what was happening under the hood when the RemoteObject service calls are invoked  if crimson.jar could impact that.

thanks,

Laura

-- Original message -- 

In Flex 1.0 I think the AMF Gateway and the Flex MXML compiler were both behind a bootstrap classloader (you can tell from the servlet mapping in /WEB-INF/web.xml to see if the AMFGatewayServlet is actually loaded by a BootstrapServlet). 

In Flex 1.5 the AMF Gateway was removed from the bootstrap classloader due to other classloader reasons.

Are you sending XML at all over RemoteObject?





From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]Sent: Wednesday, May 04, 2005 4:46 PMTo: flexcoders@yahoogroups.comSubject: RE: [flexcoders] crimson.jar  flex runtime

Hi Peter,

This app is built on Flex 1.0 (not sure if that makes a difference for this topic).

I have not seen any issues in the testing that i have done so far (which included remote object calls). I am just wondering if it's possible to run into the same issues that I saw w/ mxml compilation. Basically the flex app runs in the same web app as a commerce server. The commerce server now requires the crimson.jar lib. I'm just looking to verify whether or not that will cause problems w/ the flex app during runtime.

thanks,

Laura

-- Original message -- 

The Flex 1.5 AMF gateway reads its own configuration file using SAX during servlet initialization and DOM for deserializing/serializing ActionScript XML objects sent via AMF. Are you seeing issues with just the gateway deployed or are you just wondering whether it's theoretically possible to run into the same issues as with mxml compilation?


From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]Sent: Wednesday, May 04, 2005 3:29 PMTo: flexcoders@yahoogroups.comSubject: RE: [flexcoders] crimson.jar  flex runtime

Hi,

This helps a lot, thank you.

I do have an additional question. Our swf does make data service calls back to the server using AMF. Is there any possibility that the AMF gateway relies on an XML parser which could be in conflict w/ crimson.jar? 

thanks, Laura

-- Original message -- 

Hi,

Flex runtime means Macromedia Flash Player, which is totally client side. As you said, you have precompiled swfs on server, I am sure there won't be any conflict by keeping crimson.jar. Once swf is delivered to client, it is run on client side(in Macromedia Flash Player). Only data service calls are made between client and server.

Flex compiler and Flex runtime(Macromedia Flash Player) are two different isolated entitity. 

Hope that helps

-abdul



From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 7:16 PMTo: flexcoders@yahoogroups.com; flexcoders@yahoogroups.comCc: Jonathan BezuidenhoutSubject: Re: [flexcoders] crimson.jar  flex runtime

Hi,

Thanks for the reply -

It sounds like the conflict you experienced occurs during compile time, when compiling the mxml.

Our app is installed as a precompiled swf (no mxml pages are installed with the application), so I am wondering if any of the flex runtime code could also be in conflict w/ the crimson.jar, or if it is just isolated to the compiler.

-- Original message -- 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 jarfiles from the flex/jars into your regular WEB-INF/jars - you wouldthink duplicate but OK - unfortunately Flex does not like that. Assoon as you access mxml pages that need to be recompiled, it givesweird error messages like being unable to find global.css etc.JonathanOn 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

Re: [flexcoders] crimson.jar flex runtime

2005-05-05 Thread Joe Berkovitz
I will say (possibly irrelevantly) that I have seen xerces-based 
applications fail in the past when crimson.jar was placed in the 
CLASSPATH.  I don't think they play nice together.

[EMAIL PROTECTED] wrote:
 Hi Peter,
  
 I checked the web.xml and the AMFGatewayServlet is loaded by a 
 BootstrapServlet.
  
 Regarding sending XML over RemoteObject: No, we are not directly sending 
 XML over the RemoteObject. We are using the RemoteObject to just call 
 java methods on the app server. My concern was that I didn't know what 
 was happening under the hood when the RemoteObject service calls are 
 invoked  if crimson.jar could impact that.
  
 thanks,
  
 Laura
  
 
 -- Original message --
 In Flex 1.0 I think the AMF Gateway and the Flex MXML compiler were
 both behind a bootstrap classloader (you can tell from the servlet
 mapping in /WEB-INF/web.xml to see if the AMFGatewayServlet is
 actually loaded by a BootstrapServlet).
  
 In Flex 1.5 the AMF Gateway was removed from the bootstrap
 classloader due to other classloader reasons.
  
 Are you sending XML at all over RemoteObject?
  
  
  
 
 
 *From:* flexcoders@yahoogroups.com
 [mailto:[EMAIL PROTECTED] *On Behalf Of
 [EMAIL PROTECTED]
 *Sent:* Wednesday, May 04, 2005 4:46 PM
 *To:* flexcoders@yahoogroups.com
 *Subject:* RE: [flexcoders] crimson.jar  flex runtime
 
  
 Hi Peter,
  
 This app is built on Flex 1.0 (not sure if that makes a difference
 for this topic).
  
 I have not seen any issues in the testing that i have done so far
 (which included remote object calls). I am just wondering if it's
 possible to run into the same issues that I saw w/ mxml compilation.
 Basically the flex app runs in the same web app as a commerce
 server. The commerce server now requires the crimson.jar lib. I'm
 just looking to verify whether or not that will cause problems w/
 the flex app during runtime.
  
 thanks,
  
 Laura
  
 
 -- Original message --
 The Flex 1.5 AMF gateway reads its own configuration file using
 SAX during servlet initialization and DOM for
 deserializing/serializing ActionScript XML objects sent via AMF.
 Are you seeing issues with just the gateway deployed or are you
 just wondering whether it's theoretically possible to run into
 the same issues as with mxml compilation?
 
 
 
 *From:* flexcoders@yahoogroups.com
 [mailto:[EMAIL PROTECTED] *On Behalf Of
 [EMAIL PROTECTED]
 *Sent:* Wednesday, May 04, 2005 3:29 PM
 *To:* flexcoders@yahoogroups.com
 *Subject:* RE: [flexcoders] crimson.jar  flex runtime
 
  
 Hi,
  
 This helps a lot, thank you.
  
 I do have an additional question. Our swf does make data service
 calls back to the server using AMF. Is there any possibility
 that the AMF gateway relies on an XML parser which could be in
 conflict w/ crimson.jar?
  
 thanks, Laura
  
 
 -- Original message --
 Hi,
  
 Flex runtime means Macromedia Flash Player, which is totally
 client side. As you said, you have precompiled  swfs on
 server, I am sure there won't be any conflict by keeping
 crimson.jar. Once swf is delivered to client, it is run on
 client side(in Macromedia Flash Player). Only data service
 calls are made between client and server.
  
 Flex compiler and Flex runtime(Macromedia Flash Player) are
 two different isolated entitity.
  
 Hope that helps
  
 -abdul
  
 
 
 
 *From:* flexcoders@yahoogroups.com
 [mailto:[EMAIL PROTECTED]
 *Sent:* Wednesday, May 04, 2005 7:16 PM
 *To:* flexcoders@yahoogroups.com; flexcoders@yahoogroups.com
 *Cc:* Jonathan Bezuidenhout
 *Subject:* Re: [flexcoders] crimson.jar  flex runtime
 
  
 Hi,
  
 Thanks for the reply -
  
 It sounds like the conflict you experienced occurs during
 compile time, when compiling the mxml.
  
 Our app is installed as a precompiled swf (no mxml pages are
 installed with the application), so I am wondering if any of
 the flex runtime code could also be in conflict w/ the
 crimson.jar, or if it is just isolated

[flexcoders] crimson.jar flex runtime

2005-05-04 Thread laura . donia



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.










Re: [flexcoders] crimson.jar flex runtime

2005-05-04 Thread Jonathan Bezuidenhout
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/
 




Re: [flexcoders] crimson.jar flex runtime

2005-05-04 Thread laura . donia



Hi,

Thanks for the reply -

It sounds like the conflict you experienced occurs during compile time, when compiling the mxml.

Our app is installed as a precompiled swf (no mxml pages are installed with the application), so I am wondering if any of the flex runtime code could also be in conflict w/ the crimson.jar, or if it is just isolated to the compiler.

-- Original message -- 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 jarfiles from the flex/jars into your regular WEB-INF/jars - you wouldthink duplicate but OK - unfortunately Flex does not like that. Assoon as you access mxml pages that need to be recompiled, it givesweird error messages like being unable to find global.css etc.JonathanOn 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 the Yahoo! Terms of Service.










RE: [flexcoders] crimson.jar flex runtime

2005-05-04 Thread Abdul Qabiz





Hi,

Flex runtime means Macromedia Flash Player, which is 
totally client side. As you said, you have precompiled swfs on server, I 
am sure there won't be any conflict by keeping crimson.jar. Once swf is 
delivered to client, it is run on client side(in Macromedia Flash Player). Only 
data service calls are made between client and server.

Flex compiler and Flex runtime(Macromedia Flash Player) are 
two different isolated entitity. 

Hope that helps

-abdul



From: flexcoders@yahoogroups.com 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 
7:16 PMTo: flexcoders@yahoogroups.com; 
flexcoders@yahoogroups.comCc: Jonathan 
BezuidenhoutSubject: Re: [flexcoders] crimson.jar  flex 
runtime

Hi,

Thanks for the reply -

It sounds like the conflict you experienced occurs during compile time, 
when compiling the mxml.

Our app is installed as a precompiled swf (no mxml pages are installed with 
the application), so I am wondering if any of the flex runtime code could also 
be in conflict w/ the crimson.jar, or if it is just isolated to the 
compiler.

-- 
  Original message -- 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 jarfiles from the flex/jars into your 
  regular WEB-INF/jars - you wouldthink duplicate but OK - unfortunately 
  Flex does not like that. Assoon as you access mxml pages that need 
  to be recompiled, it givesweird error messages like being unable to find 
  global.css etc.JonathanOn 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.<B! R> 
  /BLOCKQUOTE 







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.










RE: [flexcoders] crimson.jar flex runtime

2005-05-04 Thread laura . donia



Hi,

This helps a lot, thank you.

I do have an additional question. Our swf does make data service calls back to the server using AMF. Is there any possibility that the AMF gateway relies on an XML parser which could be in conflict w/ crimson.jar? 

thanks, Laura

-- Original message -- 

Hi,

Flex runtime means Macromedia Flash Player, which is totally client side. As you said, you have precompiled swfs on server, I am sure there won't be any conflict by keeping crimson.jar. Once swf is delivered to client, it is run on client side(in Macromedia Flash Player). Only data service calls are made between client and server.

Flex compiler and Flex runtime(Macromedia Flash Player) are two different isolated entitity. 

Hope that helps

-abdul



From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 7:16 PMTo: flexcoders@yahoogroups.com; flexcoders@yahoogroups.comCc: Jonathan BezuidenhoutSubject: Re: [flexcoders] crimson.jar  flex runtime

Hi,

Thanks for the reply -

It sounds like the conflict you experienced occurs during compile time, when compiling the mxml.

Our app is installed as a precompiled swf (no mxml pages are installed with the application), so I am wondering if any of the flex runtime code could also be in conflict w/ the crimson.jar, or if it is just isolated to the compiler.

-- Original message -- 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 jarfiles from the flex/jars into your regular WEB-INF/jars - you wouldthink duplicate but OK - unfortunately Flex does not like that. Assoon as you access mxml pages that need to be recompiled, it givesweird error messages like being unable to find global.css etc.JonathanOn 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.<B! R> /BLOCKQUOTE 







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.










RE: [flexcoders] crimson.jar flex runtime

2005-05-04 Thread Peter Farland





The Flex 1.5 AMF gateway reads its own configuration file 
using SAX during servlet initialization and DOM for deserializing/serializing 
ActionScript XML objects sent via AMF. Are you seeing 
issues with just the gateway deployed or are you just wondering whether it's 
theoretically possible to run into the same issues as with mxml 
compilation?


From: flexcoders@yahoogroups.com 
[mailto:[EMAIL PROTECTED] On Behalf Of 
[EMAIL PROTECTED]Sent: Wednesday, May 04, 2005 3:29 
PMTo: flexcoders@yahoogroups.comSubject: RE: [flexcoders] 
crimson.jar  flex runtime

Hi,

This helps a lot, thank you.

I do have an additional question. Our swf does make data service calls back 
to the server using AMF. Is there any possibility that the AMF gateway relies on 
an XML parser which could be in conflict w/ crimson.jar? 

thanks, Laura

-- 
  Original message -- 
  
  Hi,
  
  Flex runtime means Macromedia Flash Player, which is 
  totally client side. As you said, you have precompiled swfs on server, I 
  am sure there won't be any conflict by keeping crimson.jar. Once swf is 
  delivered to client, it is run on client side(in Macromedia Flash Player). 
  Only data service calls are made between client and 
server.
  
  Flex compiler and Flex runtime(Macromedia Flash Player) 
  are two different isolated entitity. 
  
  Hope that helps
  
  -abdul
  
  
  
  From: flexcoders@yahoogroups.com 
  [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 
  7:16 PMTo: flexcoders@yahoogroups.com; 
  flexcoders@yahoogroups.comCc: Jonathan 
  BezuidenhoutSubject: Re: [flexcoders] crimson.jar  flex 
  runtime
  
  Hi,
  
  Thanks for the reply -
  
  It sounds like the conflict you experienced occurs during compile time, 
  when compiling the mxml.
  
  Our app is installed as a precompiled swf (no mxml pages are installed 
  with the application), so I am wondering if any of the flex runtime code could 
  also be in conflict w/ the crimson.jar, or if it is just isolated to the 
  compiler.
  
  -- 
Original message -- 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 jarfiles from the flex/jars into your 
regular WEB-INF/jars - you wouldthink duplicate but OK - unfortunately 
Flex does not like that. Assoon as you access mxml pages that need 
to be recompiled, it givesweird error messages like being unable to find 
global.css etc.JonathanOn 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.<B! R !> 
/BLOCKQUOTE 








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.










RE: [flexcoders] crimson.jar flex runtime

2005-05-04 Thread laura . donia



Hi Peter,

This app is built on Flex 1.0 (not sure if that makes a difference for this topic).

I have not seen any issues in the testing that i have done so far (which included remote object calls). I am just wondering if it's possible to run into the same issues that I saw w/ mxml compilation. Basically the flex app runs in the same web app as a commerce server. The commerce server now requires the crimson.jar lib. I'm just looking to verify whether or not that will cause problems w/ the flex app during runtime.

thanks,

Laura

-- Original message -- 

The Flex 1.5 AMF gateway reads its own configuration file using SAX during servlet initialization and DOM for deserializing/serializing ActionScript XML objects sent via AMF. Are you seeing issues with just the gateway deployed or are you just wondering whether it's theoretically possible to run into the same issues as with mxml compilation?


From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]Sent: Wednesday, May 04, 2005 3:29 PMTo: flexcoders@yahoogroups.comSubject: RE: [flexcoders] crimson.jar  flex runtime

Hi,

This helps a lot, thank you.

I do have an additional question. Our swf does make data service calls back to the server using AMF. Is there any possibility that the AMF gateway relies on an XML parser which could be in conflict w/ crimson.jar? 

thanks, Laura

-- Original message -- 

Hi,

Flex runtime means Macromedia Flash Player, which is totally client side. As you said, you have precompiled swfs on server, I am sure there won't be any conflict by keeping crimson.jar. Once swf is delivered to client, it is run on client side(in Macromedia Flash Player). Only data service calls are made between client and server.

Flex compiler and Flex runtime(Macromedia Flash Player) are two different isolated entitity. 

Hope that helps

-abdul



From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 7:16 PMTo: flexcoders@yahoogroups.com; flexcoders@yahoogroups.comCc: Jonathan BezuidenhoutSubject: Re: [flexcoders] crimson.jar  flex runtime

Hi,

Thanks for the reply -

It sounds like the conflict you experienced occurs during compile time, when compiling the mxml.

Our app is installed as a precompiled swf (no mxml pages are installed with the application), so I am wondering if any of the flex runtime code could also be in conflict w/ the crimson.jar, or if it is just isolated to the compiler.

-- Original message -- 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 jarfiles from the flex/jars into your regular WEB-INF/jars - you wouldthink duplicate but OK - unfortunately Flex does not like that. Assoon as you access mxml pages that need to be recompiled, it givesweird error messages like being unable to find global.css etc.JonathanOn 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.<B! ! R> /BLOCKQUOTE 







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.










RE: [flexcoders] crimson.jar flex runtime

2005-05-04 Thread Peter Farland





In Flex 1.0 I think the AMF Gateway and the Flex MXML 
compiler were both behind a bootstrap classloader (you can tell from the servlet 
mapping in /WEB-INF/web.xml to see if the AMFGatewayServlet is actually loaded 
by a BootstrapServlet). 

In Flex 1.5 the AMF Gateway was removed from the 
bootstrap classloader due to other classloader reasons.

Are you sending XML at all over 
RemoteObject?





From: flexcoders@yahoogroups.com 
[mailto:[EMAIL PROTECTED] On Behalf Of 
[EMAIL PROTECTED]Sent: Wednesday, May 04, 2005 4:46 
PMTo: flexcoders@yahoogroups.comSubject: RE: [flexcoders] 
crimson.jar  flex runtime

Hi Peter,

This app is built on Flex 1.0 (not sure if that makes a difference for this 
topic).

I have not seen any issues in the testing that i have done so far (which 
included remote object calls). I am just wondering if it's possible to run into 
the same issues that I saw w/ mxml compilation. Basically the flex app runs in 
the same web app as a commerce server. The commerce server now requires the 
crimson.jar lib. I'm just looking to verify whether or not that will cause 
problems w/ the flex app during runtime.

thanks,

Laura

-- 
  Original message -- 
  
  The Flex 1.5 AMF gateway reads its own configuration file 
  using SAX during servlet initialization and DOM for deserializing/serializing 
  ActionScript XML objects sent via AMF. Are you seeing 
  issues with just the gateway deployed or are you just wondering whether it's 
  theoretically possible to run into the same issues as with mxml 
  compilation?
  
  
  From: flexcoders@yahoogroups.com 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  [EMAIL PROTECTED]Sent: Wednesday, May 04, 2005 3:29 
  PMTo: flexcoders@yahoogroups.comSubject: RE: 
  [flexcoders] crimson.jar  flex runtime
  
  Hi,
  
  This helps a lot, thank you.
  
  I do have an additional question. Our swf does make data service calls 
  back to the server using AMF. Is there any possibility that the AMF gateway 
  relies on an XML parser which could be in conflict w/ crimson.jar? 
  
  thanks, Laura
  
  -- 
Original message -- 

Hi,

Flex runtime means Macromedia Flash Player, which is 
totally client side. As you said, you have precompiled swfs on server, 
I am sure there won't be any conflict by keeping crimson.jar. Once swf is 
delivered to client, it is run on client side(in Macromedia Flash Player). 
Only data service calls are made between client and 
server.

Flex compiler and Flex runtime(Macromedia Flash Player) 
are two different isolated entitity. 

Hope that helps

-abdul



From: flexcoders@yahoogroups.com 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 
7:16 PMTo: flexcoders@yahoogroups.com; 
flexcoders@yahoogroups.comCc: Jonathan 
BezuidenhoutSubject: Re: [flexcoders] crimson.jar  flex 
runtime

Hi,

Thanks for the reply -

It sounds like the conflict you experienced occurs during compile time, 
when compiling the mxml.

Our app is installed as a precompiled swf (no mxml pages are installed 
with the application), so I am wondering if any of the flex runtime code 
could also be in conflict w/ the crimson.jar, or if it is just isolated to 
the compiler.

-- 
  Original message -- 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 jarfiles from the flex/jars into your 
  regular WEB-INF/jars - you wouldthink duplicate but OK - unfortunately 
  Flex does not like that. Assoon as you access mxml pages that 
  need to be recompiled, it givesweird error messages like being unable 
  to find global.css etc.JonathanOn 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