Today, some folks call this an "embedded" java app, where you'd run something (like james) in the same JVM as something else. Searching on that might reveal something about "embedding" phoenix (running james) inside tomcat.
Can you describe in more detail why you see this as necessary in your case? Can you quantify why making a TCP call would be considered "slow"? Or is it memory that's an issue? Offhand, it doesn't seem a good idea to spawn a whole other container upon visiting a particular tomcat app. I don't see an apparent advantage to this. -broc > -----Original Message----- > From: Angel Angelov [mailto:[EMAIL PROTECTED] > Sent: Monday, February 14, 2005 4:08 PM > To: James Users List > Subject: James and JavaServlet (Tomcat) > > > Hi all, > I need to share some objects between James and my servlet (at > the moment > running on Tomcat). > Some suggestions how to do it? > I want to avoid (when possible) slow communications as a > TCP/IP or file > sharing on the hard disk. > > I was thinking to start James from my servlet, in this way > they will run > in the same jvm and can share objects in the memory. > Is there a way to do this? If yes - how? > > Thanks, > Angel > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
