Richard Vowles wrote:
> Chris - you didn't stick in the <vendor> tags! <grin>
>
> The key thing to point out here is that the JSP 1.0 nor 1.1 spec address
> accessing EJBs directly from JSP. You can do it, but you have to put in all the
> code that you would normally need to get the home and bean interface, which is
> messy and best (IMHO) put inside a normal Java Bean. Alternatively you could use
> taglibs, but since no-one seems to support these yet (IMHO, they haven't been
> clearly defined enough) and there supposedly _will_ be a standard, I think that
> you should again, keep it in a normal Java Bean.
>
It would be worth your time to read the Servlet API 2.2 specification (which JSP 1.1
requires). One of the key new features is a deployment descriptor, which can (among
other things) include symbolic references to EJBs that are looked up for you by the
servlet container when you deploy the app. Since JSP pages are servlets underneath,
they benefit from these services as well.
>
> But there is no easy 1-2-3 "model 3" mechanism yet for EJB. Whether there ever
> will be one is questionable...
>
Whether it's "easy" or not is probably debatable, but I think you will see lots of
innovative stuff in the application development tools market, that will take
advantage of this new technology to create reasonably portable applications.
Craig McClanahan
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
