What do you mean by "mix"? You don't want them in the same JVM? Or you
don't want the code mixing together?
In the latter case, choose a model/view/controller development approach.
View your servlets as controllers, and your templates as views. Your
existing application is the model.
Various environments exist that will suppor this. You can probably coax
JSP to do something like this. The WebMacro framework is built to work
this way:
http://www.webmacro.org/
The general idea would be for you to write a bunch of adaptor classes that
present your application to external programs, as the "model". Then write
servlet-side controllers and views to open up access.
You could go the RMI route this way too. That would be the design you
would wind up having to use in RMI--your adapter classes would simply
span a network connection.
However to avoid code mixing you don't need that extra overhead--just
separate the model from the view/controller code and keep it in a
separate source archive.
Justin
Quoting Robert Quinn ([EMAIL PROTECTED]):
> I want to front-end an existing java application with servlets. I don't
> want the mix them. Is RMI the best approach? I've been using a shared
> database, but I need more functionality.
>
> TIA
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
