tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Burman" <richard.bur...@ardentia.co.uk>
Subject RE: Pre-compiled JSPs?
Date Tue, 06 Sep 2005 13:58:45 GMT
Ah, I thought it was all too good to be true. Now that I have an
understanding of how to put it all together, I have given it a go but
hit another snag.

Remember the use of the 'errorOnUseBeanInvalidClassAttribute' flag?
Well, of course, that means that when the JSPs were turned into Java
classes, they ignored the fact that the bean wasn't declared in that JSP
and generated the classes regardless. What about when you try to compile
the Java into a .class file? Suddenly, the Java is missing a variable
declaration and cannot compile the class. Is there a way round this? If
not, what's the point in including the flag?!

Yours,
Confused of UK. ;o)

-----Original Message-----
From: Richard Burman [mailto:richard.burman@ardentia.co.uk] 
Sent: 06 September 2005 13:50
To: Tomcat Users List
Subject: RE: Pre-compiled JSPs?

Eureka! I get it now. :)

Indeed, I hadn't noticed the servlet-mapping section down the bottom. I
looked at the xml and foolishly assumed that it merely repeated all the
way to the bottom. Now that you've pointed out that, it all makes sense.

Thanks for all your help, I shall have a play and hopefully have new,
sparkly, compiled JSPs soon!

Richard.

-----Original Message-----
From: Darryl L. Miles [mailto:darryl@netbauds.net] 
Sent: 06 September 2005 12:33
To: Tomcat Users List
Subject: Re: Pre-compiled JSPs?


What you see looks like normal jasper name mangling of generated pages.

You use: http://myserver:8080/RichardsApp/DoSomething.jsp


I presume there is also a generated mapping entry, that you may have 
overlooked:

<servlet-mapping>
      <servlet-name>RichardsApp.DoSomething_jsp</servlet-name>
      <url-pattern>/DoSomething.jsp</url-pattern>
</servlet-mapping>

Richard Burman wrote:

>Hi Nicolas,
>
>Thanks for your reply, I really appreciate your help. I'm not sure I
>fully understand your solution. I see now that the webXmlFragment
>provides a convenient way to generate the XML needed for the Servlets
>but that have bizarre names.
>
>Let's say I have a jsp:
>/RichardsApp/DoSomething.jsp
>
>Running Jasper at it provides a java file:
>/RichardsApp/DoSomething_jsp.java
>
>Then the Servlet definition would be:
><servlet>
>  <servlet-name>RichardsApp.DoSomething_jsp</servlet-name>
>  <servlet-class>RichardsApp.DoSomething_jsp</servlet-class>
></servlet>
>
>The way to reference my JSP used to be:
>http://myserver:8080/RichardsApp/DoSomething.jsp
>
>What would the new reference be?
>http://myserver:8080/RichardsApp/DoSomething_jsp
>or
>http://myserver:8080/RichardsApp/DoSomething
>
>Have I missed something obvious?
>
>Thanks for your help!
>Richard.
>  
>

-- 
Darryl L. Miles



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message