Re: URL Pathing

[Troy Echols]

Andy,

Forgive me if I'm insulting your intelligence by mentioning this.  I discovered
while using Tomcat that I had to distingush URL paths used in jsp:include tags
(RequestDispatcher.include() calls) and jsp:forward tags
(RequestDispatcher.forward() calls) from URL paths used in generated HTML
pages.  The former were being interpreted relative to the servlet context,
whereas the latter were not.  Therefore a "/" in a generated HTML page ends up
being interpreted relative to server root.

Troy

[EMAIL PROTECTED] wrote:

> Thank you very much for the response.  I agree with you but for some reason
> it is interpreting the slash as the server document root.  It only seems to
> do this in one section of my application.  Here's the scenario.  There is a
> point in my application where the user selects the product they wish to
> order from a list that is presented to them.  This list is an ordinary JSP
> page inside the main browser window.  However, once they select this
> product by clicking on a link, it invokes a small pop-up window which
> requests that they enter a quantity.  Once they enter the quantity and
> click proceed, the child window closes and returns control to the parent
> window.  The parent window then submits it's form to a servlet which adds
> the new line to the order.  This servlet then redirects the user to a jsp
> page to display the new line.  Inside that servlet and the JSP page it
> presents, all links and redirects that contain the '/' attempt to send you
> to the server document root.  It seems that whatever is called in relation
> to the child window that was invoked attempts to reference the '/' as the
> server document root.  I hope this could provide some direction into this
> issue.
>
> Thanks again,
> Andy

Re: EJB vs Servlets

[Troy Echols]

Might there be some benefit to using EJBs over servlets alone if you want to
support various modes of connectivity to your business logic (e.g., standalone
clients using JMS/CORBA/RMI in addition to web clients).

Just my two cents worth.

Troy

> Hani Suleiman wrote:
> 
> I've considered using EJB's a number of times for various projects I'm
> involved in, but every time, I have to admit to myself that it's more for the
> fun and coolness factor, than any real 'need' to use EJB's.
> 
> In every case, I was able to implement a solution using servlets with various
> caches to do whatever is needed much faster than an EJB would do things (as
> far as I can tell, I haven't put this theory to the test yet though!). Here
> are some examples of EJB features and ways to get the same thing without
> EJB's..
> 
> 1) Connection pooling: This is available everywhere, and everyone can reap the
> benefits of it while being perfectly EJBless.
> 
> 2) Transaction support: Stored procedures can take care of this.
> 3) Caching of database objects: Pretty easy to implement
> 4) Failover/load-balancing: As Kevin mentioned, works very nicely for
> servlets.
> 
> Having said all that though, I'm still going to try and use EJB's in my
> current project, and port all the existing 'model' objects to become full
> fledged EJB's. I'm hoping the advantages will become apparent then!
> 
> Also, does anyone have any concrete examples of EJB's performance/scalability?
> Has anyone deployed them in a high volume production environment? Most people
> seem to be using them for prototyping and small scale projects, that I know
> of...
> 
> Hani Suleiman
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Duffey, Kevin
> > Sent: Monday, October 09, 2000 1:22 PM
> > To: Orion-Interest
> > Subject: EJB vs Servlets
> >
> >
> > Hey all,
> >
> > I know this is a little off-topic, but seeing as how Orion is
> > about the only
> > fully compliant EJB server, I figured this would be a better
> > place to ask.
> >
> > Lately I have talked to a number of people that have been
> > moving towards EJB
> > and pulled back because they have found it to be more tedious
> > to develop, as
> > well as the end result was slower than just using Servlets.
> >
> > I ask this because it appears to me that the servlet engine
> > (at least with
> > 2.2) being able to be failed over, load-balanced, etc, seems
> > to be quite as
> > capable for scalability and fault-tolerance as the ejb engine
> > used to be. I
> > do realize that the EJB container offers transaction management, but
> > connection pooling is available in the servlet engine at the
> > server level as
> > well. So, if you lose speed in development time and
> > performance, what is the
> > real benefits of moving to EJB? I should say this with
> > caution..I am sure
> > the EJB engine/container offers some things the servlet
> > container doesn't,
> > but I would think its possible to actually put those abilities in the
> > servlet container.
> >
> > Anyways..I'll be interested in hearing any feedback on this.
> >
> > Thanks.
> >