Remy, let be serious. If the definition is invalid for Jasper, you should be consistant and do the same at web.xml reading/parsing time.
Also when you have a webapp with more than 150 servlets, produced by 2 or 3 teams, and with the mapping requirement, you SHOULD use this kind of ENTITY inclusion to make life a little simpler for developpers. Do you hate developpers ? or Team working ? If the SYSTEM entity tag is invalid, what could we use instead ? PUBLIC ? Sorry but this one is a show stopper... On Wed, 16 Mar 2005 15:04:26 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· > RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT > <http://issues.apache.org/bugzilla/show_bug.cgi?id=34034>. > ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· > INSERTED IN THE BUG DATABASE. > > http://issues.apache.org/bugzilla/show_bug.cgi?id=34034 > > [EMAIL PROTECTED] changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REOPENED |RESOLVED > Resolution| |INVALID > > ------- Additional Comments From [EMAIL PROTECTED] 2005-03-16 15:04 ------- > Webapps are not necessarily filesystem based. As a result, that kind of little > tricks are not portable, and cannot be supported. As you know, I am very > efficient at marking reports invalid ;) > > -- > Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
