|
Question No: 3 (M a r k s: 2 )
How many types of comments are used in JSP?
Answer:- JSP may contain the following elements.
Directive element
Scripting element
Action element
|
|||
Question No: 4 ( M a r k s: 2 )
Disadvantage of Page-centered approach.
Answer:- The
page-centric approach has lot of draw backs such as the code becomes a
mixture of presentation, business and data access logic. The maintenance and
up-gradation
of the application becomes a nightmare
|
|||
Question No: 5 ( M a r k s: 3)
Advantages of using Custom Tags?
Answer:-
Provides cleaner separation of processing logic and
presentation, than JavaBeans.
Have access to all JSP implicit objects like out,
request etc.
Can be customized by specifying attributes.
|
|||
Question No: 6 ( M a r k s: 3 )
Why do we need Expression language?
Answer:The
Expression Language, not a programming or scripting language, provides a
way
to simplify expressions in JSP. It is a simple language that is geared
towards looking up
objects, their properties and performing simple operations
on them. It is inspired form both
the ECMAScript and the XPath expression
language.
|
|||
Question No: 7 ( M a r k s: 3 )
Differentiate between Sequential Execution and
multithreading.
Answer:
Every program has atleast one thread. Programs without
multithreading executes sequentially.
That is, after executing one
instruction the next instruction in sequence is executed. If a function
is
called then until the completion of the function the next instruction is not
executed. Similarly
if there is a loop then instructions after loop only gets
executed when the loop gets completed.
|
Question No: 8 ( M a r k s: 5 )
What is the difference between custom tags and JavaBeans?
Answer: In the context of
a JSP page, both accomplish similar goals but the differences are:
Custom Tags
|
Can manipulate
JSP content.
|
Custom tags can
simplify the complex operations much better than the bean can. But require a
bit more work to set up.
|
Used only in
JSPs in a relatively self-contained manner.
|
JavaBeans
|
Can't manipulate
JSP content.
|
Easier to set
up.
|
Can be used in
both Servlets and JSPs. You can define a bean in one Servlet and use them in
another Servlet or a JSP page.
|
Question No: 9 ( M a r k s: 5 )
Jsp page
directive?
Answer
: Give high level information about
servlet that will result from JSP page. It can be used
anywhere in the
document. It can control. – Which classes are imported – What class the servlet
extends – What MIME type is generated – How multithreading is handled – If the
participates
in session – Which page handles unexpected errors etc.
Question No: 10 ( M a r k s: 5 )
Why we need jsp
as we already have servlet ?
Answer:
While JSP may be great for serving up dynamic Web
content and separating content from presentation,
some may still wonder why
servlets should be cast aside for JSP. The utility of servlets is not in
question.
They are excellent for server-side processing, and, with their
significant installed base, are here to stay.
In fact, architecturally
speaking, you can view JSP as a high-level abstraction of servlets that is
implemented as an extension of the Servlet 2.1 API. Still, you shouldn't use
servlets indiscriminately;
they may not be appropriate for everyone. For
instance, while page designers can easily write a JSP
page using conventional
HTML or XML tools, servlets are more suited for back-end developers
because
they are often written using an IDE -- a process that generally requires a
higher level of
programming expertise.
|
Question No: 11 ( M a r k s: 5)
What are the characteristics of web services?
Answer: Web services are XML-based throughout.
Pretty much everything in the domain of Web services is defined in XML. For
example, the format of the data being exchanged between service user and
service provider is defined in XML or the description of web service is
defined in XML. Web services can be dynamically located and invoked. And
typically they will be accessed and invoked over both internet and intranet.
Interoperable Connect across heterogeneous
networks using ubiquitous web-based standards
Economical Recycle components, no installation
and tight integration of software
Automatic No
human intervention required even for highly complex transactions
Accessible Legacy assets & internal apps are
exposed and accessible on the web
Available Services on any device, anywhere,
anytime
Scalable No limits on scope of applications and
amount of heterogeneous applications
|
The page-centric approach has lot of draw backs such as the code becomes a
ReplyDeletemixture of presentation, business and data access logic. The maintenance and up-gradation
of the application becomes a nightmare. term paper writing service