On 7/22/04 7:00 AM, "John Zhao" <[EMAIL PROTECTED]> wrote:
> keepGenerated is a feature of JRun JSPServlet, which is a handler for all
> JSP requests. This setting need to be applied to all web application in
> JRun4 that is why it is in the default-web.xml (it is like the global
> web.xml for all apps). You can certainly move it to the web.xml for your
> application. For example, you only want to keep the .java file for certain
> app instead of all apps on the server. This is different from jrun-web.xml,
> which sounds like you don�t have. Anyhow, the default-web.xml is in the
> SERVER-INF directory. You definitely have it no matter how you deploy the
> app.
>
> Since it is a JRun specific servlet, if you move the app to other J2EE
> server, the servlet class won�t be included in your application. You
> probably don�t want to since each J2EE server has its own JSP handler. You
> need to take it out of the web.xml if you do add to your web.xml.
>
> Hope this helps.
>
> John
>
> -----Original Message-----
> From: Jeffrey Anderson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 22, 2004 9:37 AM
> To: JRun-Talk
> Subject: Re: Compiled Java Files from jsp's
>
> Our webapp is an expanded directory structure that is not in the default web
> application. As such we have just web.xml not a default-web.xml which is
> something Jrun only uses, correct?
>
> My next question is can this be added to a plain vanilla web.xml file and
> still conform to the J2EE spec so that if we deploy to a different container
> it won�t blow up at us?
>
> Thanks
>
> On 7/22/04 5:12 AM, "Kathy Vance" <[EMAIL PROTECTED]> wrote:
>
>> > 1. JRun 4.0
>> > In your app default-web.xml, check init-param for
>> > JSPServlet. If you need to have source files
>> > generated, use:
>> > <init-param>
>> > <param-name>keepGenerated</param-name>
>> > <param-value>true</param-value>
>> > </init-param>
>> > 2. JRun 3.0
>> > Jrun 3.0 will generate those source files by default.
>> >
>> > All source files are in the same directory as byecode
>> > files as Dave said.
>> > fyi.
>> > Kathy
>> >
>> >
>> > --- Dave Watts <[EMAIL PROTECTED]> wrote:
>>>>>> >>> > > Anyone here know where JRun would store the .java
>>>> >> > files from
>>>>>> >>> > > compiled jsp with a deployed webapp on a watched
>>>> >> > directory?
>>>>>> >>> > >
>>>>>> >>> > > We deploy a webapp in it�s expanded form to a
>>>> >> > folder like
>>>>>> >>> > > �/apps/app1� and then use the JRun admin interface
>>>> >> > to point
>>>>>> >>> > > to the directory and deploy the application.
>>>>>> >>> > >
>>>>>> >>> > > Turns out we have some run time errors in some JSP
>>>> >> > files that
>>>>>> >>> > > give the line number for the exception for the
>>>> >> > COMPILED JSP
>>>>>> >>> > > but not the actual JSP file on disk.
>>>> >> >
>>>> >> > I don't think it stores the source files at all - I
>>>> >> > think they're compiled
>>>> >> > directly to bytecode without being stored as source
>>>> >> > code. I'm no JRun
>>>> >> > expert, though. If they were stored anywhere, I
>>>> >> > suspect they'd be stored in
>>>> >> > the same place as the compiled class files.
>>>> >> >
>>>> >> > I think the compiled class files are in
>>>> >> > \jrun4\servers\yourserver\yourserver-war\WEB-INF\jsp
>>>> >> > (if you've deployed as
>>>> >> > an EAR, presumably it would be
>>>> >> >
>> > \jrun4\servers\yourserver\yourserver-ear\yourserver-war\WEB-INF\jsp
>>>> >> >
>>>> >> > Dave Watts, CTO, Fig Leaf Software
>>>> >> > http://www.figleaf.com/
>>>> >> > phone: 202-797-5496
>>>> >> > fax: 202-797-5444
>>>> >> >
>>>> >> >
>>>> >> >
>> >
>> >
>
> _____
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
