Well that one is simple. The client server integration already work inhouse
(we did it with jboss1.0).
Now we do the "in VM" integration in jboss2.0 just because the stack of
calls will not need to go through RMI and we can optimize teh hell out of
it. However now we run into serious classloader problems and it needs to be
fixed. Nothing terminal, just work that needs to be done in integration,
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Pfeiffer
> Sent: Wednesday, June 21, 2000 4:45 PM
> To: jBoss
> Subject: [jBoss-User] Integration with Tomcat
>
>
> I would like to run Tomcat along with jBoss. Right now they are fighting
> over port 8080. I like using port 8080 for servlet support testing (only
> because I am used to testing with it). Is there any good reason
> that jBoss
> would use this port? What is it? Can it be changed?
>
> Also, I haven't really come across a need to integrate the two products
> outside of calling an EJB from a servlet where the servlet is treated as a
> normal EJB client. Am I missing something? Is there a real need for
> integration other than the normal client - EJB server relationship?
>
> TIA,
>
> Bill Pfeiffer
> Arbitration Forums, Inc
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
