JSP Implementation

Hello! I am a newbie in JSP. How do I implement JSP? What do I need to install to run JSP? Please show me how. Tnx!

Do a search on something like "JSP tutorial" at google and you will probably get plenty of help ;)

Similar Messages

Jsp implementation of the worklist client for weblogic 6.0

Hi
Please find attached a demo version of how you can implement a JSP based
worklist client. This code is simply for demonstration/reference purposes
only but it illustrates how to implement a JSP client to the BPM product.
This application is not covered under support.
To install the product simply extract the attachment ( a war file ) and
place it in the applications directory of your weblogic deployment, for
example
d:\bea\wlserver6.0\config\mydomain\applications.
To run the worklist client enter the following url in your browser
http://localhost:7001/worklist
This code will also be placed on the BEA development centre.
Again, it must be re-iterated that although testing of the code has been
done this is not a production application and it's sole purpose it provide
examples of how to use the wlpi-worklist api. in a web environment.
Any questions, comments or updates to this code are welcome and should
be posted to the newsgroup.
Thanks and enjoy
Tony
[worklist.war]

Bart
Yes I do
Tony
"Bart Jenkins" <[email protected]> wrote in message
news:3b8bd563$[email protected]..
Tony,
Don't you mean that the target location of the .WAR file should be:
C:\bea\wlintegration2.0\processintegrator\config\mydomain\applications
(Assuming you have elected the default folders for the WLI BPMinstallation
location)
Bart Jenkins, CTO
Globeflow SA
"tony lodge" <[email protected]> wrote in message
news:[email protected]..
Hi
Please find attached a demo version of how you can implement a JSPbased
worklist client. This code is simply for demonstration/reference
purposes
only but it illustrates how to implement a JSP client to the BPMproduct.
This application is not covered under support.
To install the product simply extract the attachment ( a war file )and
place it in the applications directory of your weblogic deployment, for
example
d:\bea\wlserver6.0\config\mydomain\applications.
To run the worklist client enter the following url in your browser
http://localhost:7001/worklist
This code will also be placed on the BEA development centre.
Again, it must be re-iterated that although testing of the code hasbeen
done this is not a production application and it's sole purpose it
provide
examples of how to use the wlpi-worklist api. in a web environment.
Any questions, comments or updates to this code are welcome andshould
be posted to the newsgroup.
Thanks and enjoy
Tony

Combo box in jsp : implemented by struts tiles

Hi,
I have few problems with JSP...
we have devided the body part in the tiles into two parts
initially..................
body1: jsp with combo box
body2: a blank jsp
if the user selects an option from the combo box..in onchange function ..iam getting the value of the selected option..and iam doing form.action="action selected by user" ... so that it will go the struts-config then inturn will call the action then by forwarding success..will go to the struts-config file again ..then by have name="seccess".. it will call path="somedefinition"....this definition is defined in the tiles-definition file...
where again...extending some standard definition by overriding ..
body1:jsp with combo box
body2:jsp related to the selected option..in the combo box
second time.. in body1: again we r calling original jsp na..it will show default select only na??
so how to get the selected option and how i can give that option as selected when it is loading second time.
Hope you got my problem...
Please help me out...
Waiting for ur kind reply
Thanks & Regards
Kranti Kiran Kumar Parisa
Software Engineer [ e-Biz ]
[email protected]

It's not nice to highjack someone elses thread. I posted a reply http://forum.java.sun.com/thread.jsp?forum=45&thread=552915 (though I shouldn't have, shoulda done it here). if you have questions post them to this thread instead. Leave the other one to the OP's question.

JSP implementation class for a JSP Page

Hello,
It is very important for me to know ...
- Do you consider that a JSP developer should know that each JSP Page becomes at run-time a Java Servlet ? And int the way that the Java code you have wrote in the JSP Page is dispatched in the declaration of this servlet ?
He should know how the Java code generated by the server looks like ?
Thank you all for your answers.
Adriana

Everybody's going to have their own opinion on this - here's my 2 cents.
Theoretically, there are at least two roles here.
#1. An expert in HTML, graphic layout, user interface etc.
#2. A programmer who understands the technical infrastructure - Java, beans, servlets, database connections etc.
In the perfect world, Role #1 would build JSPs and would not need to understand Java or the technical architecture. The JSPs would act as templates and not contain any Java code (e.g. scriptlets). Role #2 would build custom tags and beans for use in the JSPs.
To answer your question, Role #1 should not understand how JSPs are translated to servlets, but Role #2 should.
In reality, the two roles are often filled by the same person, usually a programmer who may introduce Java elements into the JSP. Once this occurs, then the JSP has become a program rather than a template and knowledge of its translation to servlets is necessary for debugging.

JSP documents and namespaces

I have an issue involving JSP documents (i.e. JSP pages that are
          well-formed XML documents). I am using namespaces on children elements
          of the <jsp:root> element, because my JSP page generates XML with
          namespaces. The simple fragment below illustrates this:
          <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"
          version="1.2">
          <d:document xmlns:d="http://example.org/xml/document">
          <d:head>
          <d:title>Example</d:title>
          </d:head>
          <d:body>
          Some Text.
          </d:body>
          </d:document>
          </jsp:root>
          This example works with Tomcat 4 and Tomcat 5, but fails with WL
          8.1. I get an error like this:
          /example/my.jsp(20): no corresponding open tag for tag extension
          close: //[ ; Line: 20]
          probably occurred due to an error in /example/my.jsp line 20:
          </d:document>
          This seems to be a bug in the WebLogic JSP implementation. It should
          be possible to generate XML documents containing namespaces. The JSP
          1.2 spec is actually silent on this, but it says (JSP.5.2.2):
          "the root is where namespace attributes of taglibs will be inserted.
          All tag libraries used within the JSP document are represented in the
          root element through additional xmlns attributes."
          This to me implies that namespace declarations occurring elsewhere in
          the document are not interpreted as tag libs and therefore should be
          handled like regular tags.
          Any help is appreciated.
          -Erik


          "Erik Bruchez" <[email protected]> wrote in message
          news:[email protected]...
          > Thanks Nagesh,
          >
          > In passing, looking at the latest JSP 2.0 spec, I found out that there
          > may be an additional issue in the future, as the 2.0 spec allows for
          > tag libraries namespace declarations everywhere in the document. How
          > are you going to be able to generate XML documents with namespaces if
          > every namespace is necessarily bound to a tag library? The spec does
          > not seem to address this at all. I have emailed my feedback to the
          > JSR, but it would be interesting to have the opinion of WebLogic
          > developers on this.
          >
          > -Erik
          As far as i can remember, this doesn't restrict the namespaces in themselves
          i.e not attached to any taglibs. Given a namespace which is not resolved as
          a taglib, it will be considered a standard namespace no? .. Am i missing
          something. Also which section and which PFD version of the spec are you
          looking at? It would be great if you can give a little more detail about the
          issue so it can be fixed in the spec if possible..
          I would also be interested in knowing how you are using the Jsp documents
          (in xml format) in general. (since I'm trying to get an insight into the
          various ways in which jsp Docs are being used by customers)
          Nagesh
          >
          > Nagesh Susarla <[email protected]> wrote in message
          news:<[email protected]>...
          > > Hi Erik,
          > >
          > > Indeed this does look like a bug in the wls jsp container. Attributes
          > > with ':' in them are not being lexed correctly. I've opened CR111972 to
          > > track this issue, so please contact [email protected] for necessary
          patches.
          > >
          > > thanks
          > > Nagesh
          > >
          > > Erik Bruchez wrote:
          > > > I have an issue involving JSP documents (i.e. JSP pages that are
          > > > well-formed XML documents). I am using namespaces on children elements
          > > > of the <jsp:root> element, because my JSP page generates XML with
          > > > namespaces. The simple fragment below illustrates this:
          > > >
          > > > <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"
          > > > version="1.2">
          > > > <d:document xmlns:d="http://example.org/xml/document">
          > > > <d:head>
          > > > <d:title>Example</d:title>
          > > > </d:head>
          > > > <d:body>
          > > > Some Text.
          > > > </d:body>
          > > > </d:document>
          > > > </jsp:root>
          > > >
          > > > This example works with Tomcat 4 and Tomcat 5, but fails with WL
          > > > 8.1. I get an error like this:
          > > >
          > > > /example/my.jsp(20): no corresponding open tag for tag extension
          > > > close: //[ ; Line: 20]
          > > > probably occurred due to an error in /example/my.jsp line 20:
          > > > </d:document>
          > > >
          > > > This seems to be a bug in the WebLogic JSP implementation. It should
          > > > be possible to generate XML documents containing namespaces. The JSP
          > > > 1.2 spec is actually silent on this, but it says (JSP.5.2.2):
          > > >
          > > > "the root is where namespace attributes of taglibs will be inserted.
          > > > All tag libraries used within the JSP document are represented in the
          > > > root element through additional xmlns attributes."
          > > >
          > > > This to me implies that namespace declarations occurring elsewhere in
          > > > the document are not interpreted as tag libs and therefore should be
          > > > handled like regular tags.
          > > >
          > > > Any help is appreciated.
          > > >
          > > > -Erik

Multiple Row selection in JSP using checkbox - Oracle BPM 10gR3

Dear BPM Experts,
Has anyone invoked JSP from Oracle BPM 10gR3 screen flow that has the following UI requirement.
1. When UI is loaded user is presented with multiple rows of pre-populated data(each column of the row represents attributes of a BPM object) with checkbox against each of the rows for user to select one, many and all rows.
2. User has option to select one, many and all rows and submit the form.
3. Upon submission, the all data related to selected rows only should made available to a BPM process(either using Global Creation or Global Interactive activity)
I was able to have the JSP created with FTL tags but unable to transmit the data back to BPM process. Same has been accomplished using BPM Presentation. Can any one please help me with the JSP implementation? It is little urgent, so your early intervention is much solicited and coveted.
I will send you guys the code I have in case you need to review.
Regards,
Subho

Hi friends
I need to do the same feature, select elements, but in a tree object. I've followed the same approach - using a selectBooleanCheckBox in each node of the Tree. But, when I submit the page, the boolean property of my TreeNode object isnt changed.
An Idea?
thanks a lot!

JSP and Netscape frame target bug. HELP!!!!!!!!

Hello All,
I have a frameset that has 4 frames. In one of the frames I submit a form which processes some jsp code. The jsp code then is suppossed to load a new page in another frame (I have the target="MyFrame" in the form).
In IE it works fine and loads into the proper frame, but in Netscape 4.79 + it doesn't and opens in a completely new window. If I just have the page as html it works fine in all browsers, so I have isolated it to the jsp implementation.
Anyone come across this problem? Better yet, Anyone know how to fix the problem?
I need help ASAP as my deadline has passed and I haven't found a solution.
Thanks in advance,
Hyper
Actual jsp page below
<html>
<head>
<base target="QA">
<Script>
function pushme(){
document.form1.submit();
</script>
</head>
<body>
<form name="form1" action="nd/Euser.jsp" method="get" target="MyFrame">
<input type=hidden name=server value="00.000.000.00 - I actually have a correct server address in the functioning code">
<input type=hidden name=port value="8080">
<input type=hidden name=username value="enduser01">
<input type=hidden name=userid value="1">
<input type=hidden name=role value="EU">
<input type=hidden name=eventid value="1">
</form>
<script>
pushme();
</script>
</body>
</html>

This can not possibly be a JSP issue since it works in IE. In your case, JSP is just producing html and how this html will be handled depends on the browser .Post your frameset tag along with the html that you calimed to be working. Better yet, some html/Netscape users forum might be more helpful for you.

Any way to access params passed in URL implementing JSR 168 on Oracle Appl

I'm trying to access the params passed through URL like : http://hostname:7777/portal/page/portal/Wes%20store%20Sample/OnlyOnePortal
webStoreId=100&Id=10000
I have create a portlet with jsp implementing JSR 168 on Oracle Application Server 10g
But unable to access them in either actionProcess() as well as render() using actionRequest and renderRequest as well.
I wonder will this possible with JSR 168 to access params passed in URL in any way
Can any body help me do this

access params passed in URL implementing JSR 168 on Oracle Application Ser

Large number of JSP performance

Hi,
a colleague of me made tests with a large number of JSP and identified a
performance problem.
I believe I found a solution to his problem. I tested it with WLS 5.1 SP2
and SP3 and MS jview SDK 4.
The issue was related to the duration of the initial call of the nth JSP,
our situation as we are doing site hosting.
The solution is able to perform around 14 initial invocations/s no matter if
the invocation is the first one or the
3000th one and the throughput can go up to 108 JSPs/s when the JSP are
already loaded, the JSPs being the
snoopservlet example copied 3000 times.
The ratio have more interest than the values as the test machine (client and
WLS 5.1) was a 266Mhz laptop.
I repeat the post of Marc on 2/11/2000 as it is an old one:
Hi all,
I'm wondering if any of you has experienced performance issue whendeploying
a lot of JSPs.
I'm running Weblogic 4.51SP4 with performance pack on NT4 and Jdk1.2.2.
I deployed over 3000 JSPs (identical but with a distinct name) on myserver.
I took care to precompile them off-line.
To run my tests I used a servlet selecting randomly one of them and
redirecting the request.
getServletContext().getRequestDispatcher(randomUrl).forward(request,response);
The response-time slow-down dramaticaly as the number of distinct JSPs
invoked is growing.
(up to 100 times the initial response time).
I made some additional tests.
When you set the properties:
weblogic.httpd.servlet.reloadCheckSecs=-1
weblogic.httpd.initArgs.*.jsp=..., pageCheckSeconds=-1, ...
Then the response-time for a new JSP seems linked to a "capacity increase
process" and depends on the number of previously activated JSPs. If you
invoke a previously loaded page the server answers really fast with no
delay.
If you set previous properties to any other value (0 for example) the
response-time remains bad even when you invoke a previously loaded page.SOLUTION DESCRIPTION
Intent
The package described below is design to allow
* Fast invocation even with a large number of pages (which can be the case
with Web Hosting)
* Dynamic update of compiled JSP
Implementation
The current implementation has been tested with JDK 1.1 only and works with
MS SDK 4.0.
It has been tested with WLS 5.1 with service packs 2 and 3.
It should work with most application servers, as its requirements are
limited. It requires
a JSP to be able to invoke a class loader.
Principle
For a fast invocation, it does not support dynamic compilation as described
in the JSP
model.
There is no automatic recognition of modifications. Instead a JSP is made
available to
invalidate pages which must be updated.
We assume pages managed through this package to be declared in
weblogic.properties as
weblogic.httpd.register.*.ocg=ocgLoaderPkg.ocgServlet
This definition means that, when a servlet or JSP with a .ocg extension is
requested, it is
forwarded to the package.
It implies 2 things:
* Regular JSP handling and package based handling can coexist in the same
Application Server
instance.
* It is possible to extend the implementation to support many extensions
with as many
package instances.
The package (ocgLoaderPkg) contains 2 classes:
* ocgServlet, a servlet instantiating JSP objects using a class loader.
* ocgLoader, the class loader itself.
A single class loader object is created.
Both the JSP instances and classes are cached in hashtables.
The invalidation JSP is named jspUpdate.jsp.
To invalidate an JSP, it has simply to remove object and cache entries from
the caches.
ocgServlet
* Lazily creates the class loader.
* Retrieves the target JSP instance from the cache, if possible.
* Otherwise it uses the class loader to retrieve the target JSP class,
create a target JSP
instance and stores it in the cache.
* Forwards the request to the target JSP instance.
ocgLoader
* If the requested class has not the extension ocgServlet is configured to
process, it
behaves as a regular class loader and forwards the request to the parent
or system class
loader.
* Otherwise, it retrieves the class from the cache, if possible.
* Otherwise, it loads the class.
Do you thing it is a good solution?
I believe that solution is faster than standard WLS one, because it is a
very small piece of code but too because:
- my class loader is deterministic, if the file has the right extension I
don't call the classloader hierarchy first
- I don't try supporting jars. It has been one of the hardest design
decision. We definitely need a way to
update a specific page but at the same time someone post us NT could have
problems handling
3000 files in the same directory (it seems he was wrong).
- I don't try to check if a class has been updated. I have to ask for
refresh using a JSP now but it could be an EJB.
- I don't try to check if a source has been updated.
- As I know the number of JSP I can set pretty accurately the initial
capacity of the hashtables I use as caches. I
avoid rehash.

Use a profiler to find the bottlenecks in the system. You need to determine where the performance problems (if you even have any) are happening. We can't do that for you.

Large number of JSP performance [repost for grandemange]

Hi,
a colleague of me made tests with a large number of JSP and identified a
performance problem.
I believe I found a solution to his problem. I tested it with WLS 5.1 SP2
and SP3 and MS jview SDK 4.
The issue was related to the duration of the initial call of the nth JSP,
our situation as we are doing site hosting.
The solution is able to perform around 14 initial invocations/s no matter if
the invocation is the first one or the
3000th one and the throughput can go up to 108 JSPs/s when the JSP are
already loaded, the JSPs being the
snoopservlet example copied 3000 times.
The ratio have more interest than the values as the test machine (client and
WLS 5.1) was a 266Mhz laptop.
I repeat the post of Marc on 2/11/2000 as it is an old one:
Hi all,
I'm wondering if any of you has experienced performance issue whendeploying
a lot of JSPs.
I'm running Weblogic 4.51SP4 with performance pack on NT4 and Jdk1.2.2.
I deployed over 3000 JSPs (identical but with a distinct name) on myserver.
I took care to precompile them off-line.
To run my tests I used a servlet selecting randomly one of them and
redirecting the request.
getServletContext().getRequestDispatcher(randomUrl).forward(request,response);
The response-time slow-down dramaticaly as the number of distinct JSPs
invoked is growing.
(up to 100 times the initial response time).
I made some additional tests.
When you set the properties:
weblogic.httpd.servlet.reloadCheckSecs=-1
weblogic.httpd.initArgs.*.jsp=..., pageCheckSeconds=-1, ...
Then the response-time for a new JSP seems linked to a "capacity increase
process" and depends on the number of previously activated JSPs. If you
invoke a previously loaded page the server answers really fast with no
delay.
If you set previous properties to any other value (0 for example) the
response-time remains bad even when you invoke a previously loaded page.SOLUTION DESCRIPTION
Intent
The package described below is design to allow
* Fast invocation even with a large number of pages (which can be the case
with Web Hosting)
* Dynamic update of compiled JSP
Implementation
The current implementation has been tested with JDK 1.1 only and works with
MS SDK 4.0.
It has been tested with WLS 5.1 with service packs 2 and 3.
It should work with most application servers, as its requirements are
limited. It requires
a JSP to be able to invoke a class loader.
Principle
For a fast invocation, it does not support dynamic compilation as described
in the JSP
model.
There is no automatic recognition of modifications. Instead a JSP is made
available to
invalidate pages which must be updated.
We assume pages managed through this package to be declared in
weblogic.properties as
weblogic.httpd.register.*.ocg=ocgLoaderPkg.ocgServlet
This definition means that, when a servlet or JSP with a .ocg extension is
requested, it is
forwarded to the package.
It implies 2 things:
* Regular JSP handling and package based handling can coexist in the same
Application Server
instance.
* It is possible to extend the implementation to support many extensions
with as many
package instances.
The package (ocgLoaderPkg) contains 2 classes:
* ocgServlet, a servlet instantiating JSP objects using a class loader.
* ocgLoader, the class loader itself.
A single class loader object is created.
Both the JSP instances and classes are cached in hashtables.
The invalidation JSP is named jspUpdate.jsp.
To invalidate an JSP, it has simply to remove object and cache entries from
the caches.
ocgServlet
* Lazily creates the class loader.
* Retrieves the target JSP instance from the cache, if possible.
* Otherwise it uses the class loader to retrieve the target JSP class,
create a target JSP
instance and stores it in the cache.
* Forwards the request to the target JSP instance.
ocgLoader
* If the requested class has not the extension ocgServlet is configured to
process, it
behaves as a regular class loader and forwards the request to the parent
or system class
loader.
* Otherwise, it retrieves the class from the cache, if possible.
* Otherwise, it loads the class.
Do you thing it is a good solution?
I believe that solution is faster than standard WLS one, because it is a
very small piece of code but too because:
- my class loader is deterministic, if the file has the right extension I
don't call the classloader hierarchy first
- I don't try supporting jars. It has been one of the hardest design
decision. We definitely need a way to
update a specific page but at the same time someone post us NT could have
problems handling
3000 files in the same directory (it seems he was wrong).
- I don't try to check if a class has been updated. I have to ask for
refresh using a JSP now but it could be an EJB.
- I don't try to check if a source has been updated.
- As I know the number of JSP I can set pretty accurately the initial
capacity of the hashtables I use as caches. I
avoid rehash.
Cheers - Wei

I dont know the upper limit, but I think 80 is too much. I have never used more than 15-20. For Nav attributes, a seperate tables are created which causes the Performance issue as result in new join at query run time. Just ask your business guy, if these can be reduced.One way could be to model these attributes as seperate characteristics. It will certainly help.
Thanks...
Shambhu

Differences between WL or Netscape for Servlets and JSP's

What are the advantages / disadvantages of running Servlets under WL,
          vs. say, running them in Netscape's servlet engine? Assuming EJB
          container is run separately, either one of these could make calls to the
          WL EJB server, so perhaps it would be simpler and faster to run servlets
          and JSP's under Netscape, and have them call via t3 into a weblogic
          server for EJB's?
          Thoughts
          david
          David Michaels <[email protected]>
          Director of Technology
          ShockMarket Corporation (650) 330-4665
          [david.vcf]


David,
          One of the major reasons to run your servlets on Weblogic is that we have an
          optimization that allows us to pass by reference objects when calling from
          servlets to EJB. This makes things much faster.
          A number of our customers, in addition, have seen performance problems when
          using other servlet engines. It just seems to cause problems due to their
          threading models etc.
          Finally, our servlet engine is by far the most mature and robust on the
          market today. Our JSP implementation is also the best in terms of
          performance.
          Thanks,
          Michael
          Michael Girdley
          WLS Product Manager
          David Michaels <[email protected]> wrote in message
          news:[email protected]..
          > What are the advantages / disadvantages of running Servlets under WL,
          > vs. say, running them in Netscape's servlet engine? Assuming EJB
          > container is run separately, either one of these could make calls to the
          > WL EJB server, so perhaps it would be simpler and faster to run servlets
          > and JSP's under Netscape, and have them call via t3 into a weblogic
          > server for EJB's?
          >
          > Thoughts
          >
          > david
          >
          > --
          > David Michaels <[email protected]>
          > Director of Technology
          > ShockMarket Corporation (650) 330-4665
          >
          >

JSP - HTTP Session memory leak !!!

Hi there,
Another problem with JSP implementation of the framework !!!
I just added a debugging option to the jsp that show me the session.getValueParameters()
with their value.
My question is why or when are the rowkeys flush out of the session environment and if it's not this the bug that causes a java.lang.OutOfMemory when navigating in big result sets in an Master-Detail View.
Any answer from JDev Team will me very much appreciated.
TIA,
Seb

Hello,
You can modify the RowSetBrowser.java file to release all the detail keys after each master record is navigated. You need to clear the keys at the top of the render method as follows:
Hashtable keys = getKeys();
// assume that all keys need to be removed, we only support navigation through
// one screenfull of row keys
keys.clear();

JSP extending application class?

Greetings,
          I'm in the midst of porting some servlets from an implementation that
          didn't use jsp at all to a MVC type model.
          For some quick and dirty output, I wanted to define a couple jsp files
          that extended a app BaseServlet class (frame and menu functions included
          on this servlet) so that
          I could do stuff like this
          </body>
          <% setSideMenu(<array of Menu structures from session>); %>
          ... other html
          where setSideMenu was one of the functions this jsp inherited from my
          BaseServlet class.
          Unfortunately, the JSP compiled, but whenever I try to use it, the
          client browser sits waiting for output that never comes.
          Now, before I go off and debug this with lots of printlns, is there
          some easy explaination for why WLS would do this (did I break the JSP
          implementation by extending a class that was not weblogic.xxx?)
          If I remove the "page extends..." directive, the jsp returns after
          compilation ok.
          Thanks In Advance,
          Brian Homrich
          Chicago Illinois


There is no such thing as a javafx class. It is a regular java class. The Aapplication class is the entry
point for JavaFX application. You have to extend the Application class to create Javafx application .

IllegalAccessError and JSP

Hi,
          We are having problems with the JSP compiler: it's happens that,
          when we have an inner class (a class embded into a jsp)
          implementing an interface of an external package
          (correctly included in the classpath), it returns an
          IllegalAccessError. It only happens when the class implements
          an external interface, and we have not found that problem
          with other JSP Compilers (p.ex. jakarta-tomcat).
          We haven't found any configuration option in the documentation
          to resolve that problem an we would like to know if it is a
          security convention, a bug or something configurable.
          We are using:
          - Weblogic Server Version: 4.5.1 - 9602001-01,
          - JDK version: Solaris JDK 1.2.1_04,
          - OS version: SunOS Release 5.7 Generic_106541-09
          - Full Thread dump:
          Thu Jun 29 14:20:28 GMT+01:00 2000:<E> <ServletContext-General> Servlet
          failed with Exception
          java.lang.IllegalAccessError:
          jsp_servlet/_madrid/_teatro/_buscateatro/_resultado_95_obra$1$SalasParaTeatr
          oWriter
          at
          jsp_servlet._madrid._teatro._buscateatro._resultado_95_obra._jspService(Comp
          iled Code)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :105)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :123)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:742)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:686)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          Manager.java:247)
          at
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
          at
          weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          at weblogic.kernel.ExecuteThread.run(Compiled Code)
          Please, contact us in [email protected]
          Thank you,
          Carlos.
          Carlos Narciso Moreno González.
          Estudio de Ingeniería Telemática CESAT.
          Almirante Francisco Moreno, 5, Planta Baja.
          Ciudad Universitaria. 28040 Madrid. Spain.
          Tel : +34-91-4590001
          Fax : +34-91-4597555
          E-mail : [email protected]


Hi
I'm not sure if you are using the right syntax for <jsp:include..>
Here is the link to a quick start tutorial:
http://java.sun.com/products/jsp/docs.html
Keep me posted on your progress.
Good Luck!
Eshwar Rao
Developer Technical Support
Sun microsystems inc
http://www.sun.com/developers/support

Redirect to login JSP form in case user hits restricted area

hi
          create a template jsp so that all the other jsps are created from that
          template,in the template
          check if the user is logged in or not and redirect accordingly.
          u can do this by 2 ways ,check for the userid in the session object or in
          the bean whose scope is session
          Hope this Helps
          Parag B.Bhagwat
          John Greene <[email protected]> wrote in message
          news:[email protected]...
          >
          > Hi --
          >
          > This may be of some help to people:
          >
          > http://www.weblogic.com/docs45/examples/security/formauth/index.html
          >
          >
          >
          > Robert Patrick wrote:
          > >
          > > Here is some example code of how to create a JSP that extends a servlet
          class...
          > >
          > > Hope this helps,
          > > Robert
          > >
          > > Stephen Earl wrote:
          > >
          > > > Hi,
          > > >
          > > > With jhtml you can use the extends tag to "tell" the compiler what
          class
          > > > your resulting servlet extends. I've used this method to implement
          site
          > > > wide authentication and authorization. I don't know if this
          capability
          > > > exists in Weblogic's JSP implementation.
          > > >
          > > > This is a question for Weblogic... will you ever release the source
          code for
          > > > your JSP compiler??? Think Jakarta... think GNU... this would help a
          lot
          > > > of people.
          > > >
          > > > Steve...
          > > >
          >
          >
          > Take care,
          >
          > -jg
          >
          > John Greene BEA WebXpress
          > Developer Relations Engineer 550 California Street, 10th floor
          > 415.364.4559 San Francisco, CA 94104-1006
          > mailto:[email protected] http://weblogic.beasys.com

JSP Implementation

Similar Messages

Maybe you are looking for