[flexcoders] Cairngorm 0.99, JRun and Log4J

2005-05-19 Thread Alistair McLeod





Hi 
all,

It turns out that 
the log4j JAR file that ships with the CairngormStore example in Cairngorm 
conflicts with the one that is pre-installed with the version of JRun that ships 
with Flex, and stops the application context from starting up successfully. So, 
to get it running, delete the following file before starting the integrated JRun 
server:

\jrun4\servers\default\cairngormstore\WEB-INF\lib\log4j-1.2.8.jar

JRun will then use 
its own Log4J JAR file.




Cheers,

Ali

--
Alistair 
McLeodDevelopmentDirector
iteration::two[EMAIL PROTECTED]

Office: +44 (0)131 338 
6108

This e-mail and any associated attachments 
transmitted with it may contain confidential information and must not be copied, 
or disclosed, or used by anyone other than the intended recipient(s). If you are 
not the intended recipient(s) please destroy this e-mail, and any copies of it, 
immediately.Please also note that while software systems have been 
used to try to ensure that this e-mail has been swept for viruses, 
iteration::two do not accept responsibility for any damage or loss caused in 
respect of any viruses transmitted by the e-mail. Please ensure your own checks 
are carried out before any attachments are 
opened.









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.










R: [flexcoders] Cairngorm 0.99, JRun and Log4J

2005-05-19 Thread Paolo Bernardini










Thanks Alistair



Finally Im able to
see the cairngormstore example.



However Im noting
something strange, if I use the netConnectionDebugger that ship with flex,
which I usually use to see the exachange of data between the server and the
client, I dont see the data.



This is what I see:



MethodName:
productServiceImpl.getProducts

Parameters (object #2)

.[0] (object #3)

.._flag:
Envelope

..data (object
#4)

...No
properties

..headers (object
#5)

...[0]
(object #6)

[0]:
ServiceType

[1]:
(boolean) false

[2]:
stateless-class





Result (object #2)

.[0]: (undefined) 

.[1]: (undefined) 

.[10]: (undefined) 

.[11]: (undefined) 

.[12]: (undefined) 

.[13]: (undefined) 

.[14]: (undefined) 

.[15]: (undefined) 

.[2]: (undefined) 

.[3]: (undefined) 

.[4]: (undefined) 

.[5]: (undefined) 

.[6]: (undefined) 

.[7]: (undefined) 

.[8]: (undefined) 

.[9]: (undefined)



Is this because you are
using a valueOject and the debug is not able to understand it or what?











Da: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] Per conto
di Alistair McLeod
Inviato: giovedì 19 maggio 2005
11.05
A: flexcoders@yahoogroups.com
Oggetto: [flexcoders] Cairngorm
0.99, JRun and Log4J







Hi all,











It turns out that the log4j JAR file that ships with the
CairngormStore example in Cairngorm conflicts with the one that is
pre-installed with the version of JRun that ships with Flex, and stops the
application context from starting up successfully. So, to get it running,
delete the following file before starting the integrated JRun server:











\jrun4\servers\default\cairngormstore\WEB-INF\lib\log4j-1.2.8.jar











JRun will then use its own Log4J JAR file.











Cheers,



Ali



--

Alistair McLeod
DevelopmentDirector



iteration::two
[EMAIL PROTECTED]











Office: +44 (0)131 338 6108











This e-mail and any associated attachments
transmitted with it may contain confidential information and must not be
copied, or disclosed, or used by anyone other than the intended recipient(s).
If you are not the intended recipient(s) please destroy this e-mail, and any
copies of it, immediately.

Please also note that while software systems have been used to try to ensure
that this e-mail has been swept for viruses, iteration::two do not accept
responsibility for any damage or loss caused in respect of any viruses
transmitted by the e-mail. Please ensure your own checks are carried out before
any attachments are opened.























Passa a QUIZIL SuperMail !

Con 40 MBytes di spazio per casella (a richiesta anche 100), spedizione ad alta velocità di messaggi grandi fino a 20 Mbytes, 
WebMail di alta qualità, la configurazione gratuita di SPF e, naturalmente, Antivirus, Antispam, POP e IMAP, più il backup settimanale. 
SuperMail è integrabile con WebFax e WebAdmin.
Se preferisci l'indipendenza puoi portare un MailGateway entro la tua azienda, ed usarlo per attivare le funzioni cooperative di Outlook !

Attiva QUIZIL SuperMail con una email a [EMAIL PROTECTED]












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] Cairngorm 0.99, JRun and Log4J

2005-05-19 Thread Hans Omli




I'm running Tomcat. I see two log4j warnings when launching Tomcat through Eclipse:

log4j:WARN No appenders could be found for logger (org.apache.catalina.session.ManagerBase).
log4j:WARN Please initialize the log4j system properly.

Then I get the following error when I run Main.mxml:

Error: Unresolved compilation problems: The import org.apache.commons cannot be resolvedThe import org.apache.commons cannot be resolvedlog cannot be resolvedlog cannot be resolved
log cannot be resolvedlog cannot be resolvedlog cannot be resolvedlog cannot be resolvedLog cannot be resolved to a typeLogFactory cannot be resolved

Any ideas?
On 5/19/05, Alistair McLeod [EMAIL PROTECTED] wrote:

Hi all,

It turns out that the log4j JAR file that ships with the CairngormStore example in Cairngorm conflicts with the one that is pre-installed with the version of JRun that ships with Flex, and stops the application context from starting up successfully. So, to get it running, delete the following file before starting the integrated JRun server:


\jrun4\servers\default\cairngormstore\WEB-INF\lib\log4j-1.2.8.jar

JRun will then use its own Log4J JAR file.




Cheers,

Ali

--
Alistair McLeodDevelopmentDirector
iteration::two[EMAIL PROTECTED]

Office: +44 (0)131 338 6108

This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately.
Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.









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] Cairngorm 0.99, JRun and Log4J

2005-05-19 Thread Hans Omli



I resolved the log4j warnings. I had imported log4j.properties into the wrong webapp. :-(

However, I still get the unresolved compilation problems. Any ideas?
On 5/19/05, Hans Omli [EMAIL PROTECTED] wrote:

I'm running Tomcat. I see two log4j warnings when launching Tomcat through Eclipse:

log4j:WARN No appenders could be found for logger (org.apache.catalina.session.ManagerBase).
log4j:WARN Please initialize the log4j system properly.

Then I get the following error when I run Main.mxml:

Error: Unresolved compilation problems: The import org.apache.commons cannot be resolvedThe import org.apache.commons cannot be resolvedlog cannot be resolvedlog cannot be resolved
log cannot be resolvedlog cannot be resolvedlog cannot be resolvedlog cannot be resolvedLog cannot be resolved to a typeLogFactory cannot be resolved

Any ideas?

On 5/19/05, Alistair McLeod [EMAIL PROTECTED]
 wrote: 

Hi all,

It turns out that the log4j JAR file that ships with the CairngormStore example in Cairngorm conflicts with the one that is pre-installed with the version of JRun that ships with Flex, and stops the application context from starting up successfully. So, to get it running, delete the following file before starting the integrated JRun server: 


\jrun4\servers\default\cairngormstore\WEB-INF\lib\log4j-1.2.8.jar

JRun will then use its own Log4J JAR file.




Cheers,

Ali

--
Alistair McLeodDevelopmentDirector
iteration::two[EMAIL PROTECTED]

Office: +44 (0)131 338 6108

This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately. 
Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened. 









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] Cairngorm 0.99, JRun and Log4J

2005-05-19 Thread Hans Omli



Resolved the compilation problems. I needed to add the libraries to the Tomcat project I'm using in Eclipse, not just import the libraries into the lib folder.
On 5/19/05, Hans Omli [EMAIL PROTECTED] wrote:

I resolved the log4j warnings. I had imported log4j.properties into the wrong webapp. :-(

However, I still get the unresolved compilation problems. Any ideas?

On 5/19/05, Hans Omli [EMAIL PROTECTED] wrote:
 

I'm running Tomcat. I see two log4j warnings when launching Tomcat through Eclipse:

log4j:WARN No appenders could be found for logger (org.apache.catalina.session.ManagerBase).
log4j:WARN Please initialize the log4j system properly.

Then I get the following error when I run Main.mxml:

Error: Unresolved compilation problems: The import org.apache.commons cannot be resolvedThe import org.apache.commons cannot be resolvedlog cannot be resolvedlog cannot be resolved
log cannot be resolvedlog cannot be resolvedlog cannot be resolvedlog cannot be resolvedLog cannot be resolved to a typeLogFactory cannot be resolved

Any ideas?

On 5/19/05, Alistair McLeod [EMAIL PROTECTED] 
 wrote: 

Hi all,

It turns out that the log4j JAR file that ships with the CairngormStore example in Cairngorm conflicts with the one that is pre-installed with the version of JRun that ships with Flex, and stops the application context from starting up successfully. So, to get it running, delete the following file before starting the integrated JRun server: 


\jrun4\servers\default\cairngormstore\WEB-INF\lib\log4j-1.2.8.jar

JRun will then use its own Log4J JAR file.




Cheers,

Ali

--
Alistair McLeodDevelopmentDirector
iteration::two[EMAIL PROTECTED]

Office: +44 (0)131 338 6108

This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately. 
Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened. 









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.