Re: Tomcat 5.5.12 / Jasper2 - showstoppers ?

2005-10-05 Thread Remy Maucherat 

Henri Gomez wrote:

Hi to all,

I don't know if they should be considered showstopper but while
playing with 5.5.12 for some of our new applications, I see these
problems :

When using Jasper2 in JSP precompilation step, it load needed taglibs
jars defined in web.xml, but didn't release all of them after build
(here is how it's invoked)


Does this mean JARs are locked ?


Another serious problem in Jasper2 precompilation is when web.xml
contains external entites living in the webapp. We fixed Jasper2 in
5.5.9 to fixe this behaviour at runtime, but it appears it's also
needed in precompilation step.


I actually forgot what the fix was.

Rémy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5.12 / Jasper2 - showstoppers ?

2005-10-05 Thread Henri Gomez 
  When using Jasper2 in JSP precompilation step, it load needed taglibs
  jars defined in web.xml, but didn't release all of them after build
  (here is how it's invoked)

 Does this mean JARs are locked ?

yes, and since ant is running on the eclipse JVM, no other way to
release the jar that to stop eclipse ;(

  Another serious problem in Jasper2 precompilation is when web.xml
  contains external entites living in the webapp. We fixed Jasper2 in
  5.5.9 to fixe this behaviour at runtime, but it appears it's also
  needed in precompilation step.

 I actually forgot what the fix was.

If I recall exactly in JspConfig :

private void processWebDotXml(ServletContext ctxt) throws JasperException {

InputStream is = null;

try {
URL uri = ctxt.getResource(WEB_XML);
if (uri == null) {
// no web.xml
return;
}

is = uri.openStream();
InputSource ip = new InputSource(is);
ip.setSystemId(uri.toExternalForm());

ParserUtils pu = new ParserUtils();
TreeNode webApp = pu.parseXMLDocument(WEB_XML, ip);

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 5.5.12 / Jasper2 - showstoppers ?

2005-10-04 Thread Henri Gomez 
Hi to all,

I don't know if they should be considered showstopper but while
playing with 5.5.12 for some of our new applications, I see these
problems :

When using Jasper2 in JSP precompilation step, it load needed taglibs
jars defined in web.xml, but didn't release all of them after build
(here is how it's invoked)

jasper2 validateXml=false 
uriroot=${build.dir}/jspc/${wname}
webXmlFragment=${build.dir}/dst/${wname}/WEB-INF/jsp.xml
outputDir=${build.dir}/${wname}-src javaEncoding=ISO-8859-1
trimSpaces=true /


As such, when you're using ANT from eclipse and you specify ANT should
use the same JRE as the workspace, you're puzzled and should restart
eclipse ;-(


Another serious problem in Jasper2 precompilation is when web.xml
contains external entites living in the webapp. We fixed Jasper2 in
5.5.9 to fixe this behaviour at runtime, but it appears it's also
needed in precompilation step.

Here is a sample web.xml where you could see use of entities located
in base.xml and jsp.xml (also located in WEB-INF).


?xml version=1.0 encoding=ISO-8859-1?

!DOCTYPE web-app
PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd; [


!ENTITY base  SYSTEM base.xml
!ENTITY jsp SYSTEM  jsp.xml

]

web-app

...

base;
jsp;

...

  taglib
taglib-urihttp://jakarta.apache.org/taglibs/random-1.0/taglib-uri
taglib-location/WEB-INF/lib/taglibs-random.jar/taglib-location
  /taglib

  /web-app


Did these bugs are showstoppers or should they be postponed to 5.5.13 ?

Regards

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]