[Bug 55398] New: Unable to deploy war file on tomcat 6.0.13
https://issues.apache.org/bugzilla/show_bug.cgi?id=55398
Bug ID: 55398
Summary: Unable to deploy war file on tomcat 6.0.13
Product: Tomcat 6
Version: 6.0.13
Hardware: Other
OS: other
Status: NEW
Severity: critical
Priority: P2
Component: Manager application
Assignee: dev@tomcat.apache.org
Reporter: raviyella...@india.com
Unable to deploy war file tomcat 6.0.13 .please find the below exception for
your reference.attaching war file for your reference.
Aug 9, 2013 12:05:18 AM org.apache.catalina.startup.ContextConfig init
SEVERE: Exception fixing docBase: {0}
java.io.FileNotFoundException:
/opt/tc6-tinbo/webapps/TestAdhar/META-INF/MANIFEST.MF (No such file or
directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:179)
at java.io.FileOutputStream.(FileOutputStream.java:131)
at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:312)
at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:158)
at
org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:890)
at
org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:1008)
at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:279)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5297)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4070)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Aug 9, 2013 12:05:19 AM org.apache.catalina.startup.ContextConfig
validateSecurityRoles
INFO: WARNING: Security role name tomcat used in an without
being defined in a
Aug 9, 2013 12:05:24 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-9082
Aug 9, 2013 12:05:24 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 5854 ms
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 55398] Unable to deploy war file on tomcat 6.0.13
https://issues.apache.org/bugzilla/show_bug.cgi?id=55398 Christopher Schultz changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Christopher Schultz --- Please re-try with current Tomcat 6.0.37. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 55383] Improve markup and design of Tomcat's HTML pages
https://issues.apache.org/bugzilla/show_bug.cgi?id=55383 --- Comment #3 from Konstantin Preißer --- Hi Mark, (In reply to Mark Thomas from comment #2) > An overhaul of the docs and site is long overdue as you can tell from the > age of the duplicate. > > Please, go ahead. If you attach proposed patches, I'm happy to review and > apply them as I am sure other committers will be as well. > > One piece of advice I would give is to make small, incremental changes > rather than a "big-bang" approach. It is hard to provide guidance to what > the 'right' size is but the committers will let you know if you are wide of > the mark. > > As you go, please keep in mind the concerns raised in bug 16579. > > One comment on the new default homepage, it is (in my view) too cluttered. > It is a million miles better than what we had before but I think there is > still scope for improvement. Ok, thank you. After reviewing bug 16579, I would like to add to my previous point 3) reg. : You can create a table-like layout purely with CSS (that is, using tags like in markup and then use style "display: table;", "display: table-row" etc). This has the advantages over using that - the HTML markup doesn't misuse a for layout, which means a user-agent like a Search Engine can correctly regognize the structure of the document, and - the CSS "table" will not exceed the given width if it has elements that are wider (e.g. a with long lines of unwrappable text) than the "table" (this should consider the concerns in bug 16579). There are some other things that came to my attention while I was browsing through Tomcat's doc: 1) Sometimes there is following markup in HTML (a in a tag): Text... ... More Text... For example, r1511000 intruduced such a structure. Note that this is invalid HTML, as a element cannot have nested and elements. A HTML parser therefore closes the element as soon as it sees a , and therefore the following is incorrect (I think this has been mentioned already by Konstantin Kolinko). In XHTML, it is possible to have a DOM like ..., but it is still not valid XHTML. The currect markup in this case would be: Test... ... More Text... Please see the HTML5 spec [1] reg. "The p element" for more info at this issue. 2) The Tomcat Docs use the Comments system (https://comments.apache.org/) by appeding a JavaScript that will place a comments section there (e.g. at the bottom at http://tomcat.apache.org/tomcat-8.0-doc/index.html). Note that while the script seems to be intended to be usable in XHTML as it contains a CDATA-declaration in the
[Bug 55383] Improve markup and design of Tomcat's HTML pages
https://issues.apache.org/bugzilla/show_bug.cgi?id=55383 --- Comment #4 from Konstantin Preißer --- Created attachment 30719 --> https://issues.apache.org/bugzilla/attachment.cgi?id=30719&action=edit Example for new markup and style I attached an example HTML page with an idea of new HTML markup and tweaked style, that could be used as template for Tomcat Documentation and Tomcat Website. The layout is very similar to the current one (navigation at left-hand-side), but it should refresh the look so the site doesn't look dated. There is still room for a completely new layout in the future (like the proposal from pid), but I do not yet have an idea of how a new layout might look like (I'm more a programmer than designer), and my favor was to improve the HTML markup while kepping a similar layout. The page is HTML but is also viewable as XHTML. It is best viewed at IE10+, Firefox, Chrome etc. (note that Chrome seems to behave differently than IE10 and Firefox with the font line height). I'm developing mostly on Windows so I used a Windows font (Lucida Sans Unicode) as primary font for the site. Note that older browsers like IE 9 do not show the layout correctly, but information is still viewable (if people need to view the site with old IE at corporate PCs for example). For the code box, overflow:auto is used, so in the XML example with the long unwrappable line, browsers should display a scrollbar below the box (but I needed to use markup like
[Bug 55399] New: Request English but Response Spanish Language (Default Locale)
https://issues.apache.org/bugzilla/show_bug.cgi?id=55399
Bug ID: 55399
Summary: Request English but Response Spanish Language (Default
Locale)
Product: Tomcat 7
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: guillermo.gran...@gmail.com
== Server: Windows, Language: es_ES
== Client: Linux, Language: en_US
== Request:
POST /xx HTTP/1.1
Host: x.x.x.x:8080
Accept: */*
Accept-Language: en
Content-Length: 0
Content-Type: application/x-www-form-urlencoded
== Response:
HTTP/1.1 400 Petición incorrecta
Server: Apache-Coyote/1.1
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 1030
Date: Sat, 10 Aug 2013 17:25:17 GMT
Connection: close
...cut...
---
HTTP Response "Petición incorrecta" must be in English. Right?
I tried to do response.setLocale() workarround in the Servlet but neither
works:
---
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
// ...
response.setLocale(Locale.ENGLISH); // Locale.US neither
// ...
response.sendError(HttpServletResponse.SC_BAD_REQUEST, "BAD REQUEST");
}
---
HttpServletResponse.setLocale() don't honors?
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Tomcat Gump Builds
Dear Tomcat devs, we'll be reducing the set of projects built by Gump pretty soon. We'll still build the projects Tomcat depends on and re-enable nagging for the Tomcat builds itself. Mark inidicated it would be good to reduce the set of Tomcat related projects built by Gump by removing ancient versions. Right now we have jakarta-tomcat-40.xml jakarta-tomcat-5.xml jakarta-tomcat-catalina.xml(5.5 branch) jakarta-tomcat-connectors.xml (5.5 branch) jakarta-tomcat-jasper_tc4.xml jakarta-tomcat-jasper_tc5.xml tomcat-connectors-native.xml (trunk) tomcat-taglibs.xml tomcat-tc6.xml tomcat-tc7.xml tomcat-trunk.xml Do you want to keep anything beside tc7 and the trunk builds? Do you still want Gump to build the standard taglib? The only dependees of Tomcat require the 4.x version and we wouldn't build them in the future anyway. Please note that we intend to hand back our FreeBSD jail so the only platform Gump will be using will be Linux (Ubuntu 10.04 right now). Cheers Stefan - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: svn commit: r1511501 - in /tomcat/trunk: conf/logging.properties java/org/apache/juli/FileHandler.java webapps/docs/changelog.xml
On Aug 7, 2013, at 2:14 PM, ma...@apache.org wrote:
> Author: markt
> Date: Wed Aug 7 21:14:55 2013
> New Revision: 1511501
>
> URL: http://svn.apache.org/r1511501
> Log:
> Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=52092
> Switch to the AsyncLogWriter and OneLineFormatter by default
I think this broke running with -security
$ output/build/bin/catalina.sh run -security
Exception in thread "main" java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at java.lang.Class.newInstance0(Class.java:374)
at java.lang.Class.newInstance(Class.java:327)
at
org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:535)
at
org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:478)
at
org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:302)
at java.util.logging.LogManager$2.run(LogManager.java:288)
at java.util.logging.LogManager$2.run(LogManager.java:286)
at java.security.AccessController.doPrivileged(Native Method)
at
java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:286)
at java.util.logging.LogManager.getLogManager(LogManager.java:268)
at java.util.logging.Logger.(Logger.java:252)
at java.util.logging.LogManager$RootLogger.(LogManager.java:1311)
at java.util.logging.LogManager$RootLogger.(LogManager.java:1309)
at java.util.logging.LogManager$1.run(LogManager.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.(LogManager.java:176)
at java.util.logging.Logger.demandLogger(Logger.java:307)
at java.util.logging.Logger.getLogger(Logger.java:361)
at org.apache.juli.logging.DirectJDKLog.(DirectJDKLog.java:68)
at
org.apache.juli.logging.DirectJDKLog.getInstance(DirectJDKLog.java:188)
at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:99)
at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:114)
at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:165)
at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:52)
Caused by: java.security.AccessControlException: access denied
("java.util.PropertyPermission" "org.apache.juli.AsyncOverflowDropType" "read")
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:366)
at
java.security.AccessController.checkPermission(AccessController.java:560)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at
java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1302)
at java.lang.System.getProperty(System.java:742)
at org.apache.juli.AsyncFileHandler.(AsyncFileHandler.java:51)
... 28 more
Exception in thread "Thread-0" java.lang.NoClassDefFoundError: Could not
initialize class java.util.logging.LogManager
at java.util.logging.LogManager$Cleaner.run(LogManager.java:231)
signature.asc
Description: Message signed with OpenPGP using GPGMail
[Bug 55400] New: WsFilter not compatible with async sample applications
https://issues.apache.org/bugzilla/show_bug.cgi?id=55400 Bug ID: 55400 Summary: WsFilter not compatible with async sample applications Product: Tomcat 8 Version: trunk Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: WebSocket Assignee: dev@tomcat.apache.org Reporter: jboy...@apache.org $ output/build/bin/catalina.sh run http://localhost:8080/examples/async/async0 java.lang.IllegalStateException: Not supported. org.apache.catalina.connector.Request.startAsync(Request.java:1621) org.apache.catalina.connector.Request.startAsync(Request.java:1614) org.apache.catalina.connector.RequestFacade.startAsync(RequestFacade.java:1033) async.Async0.service(Async0.java:44) javax.servlet.http.HttpServlet.service(HttpServlet.java:728) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:91) org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) I'm not sure if this filter supports Async or whether it should not be applied for these Servlets. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1512826 - in /tomcat/trunk: java/org/apache/catalina/ java/org/apache/catalina/core/ java/org/apache/catalina/startup/ java/org/apache/catalina/storeconfig/ java/org/apache/jasper/resourc
Author: jboynes Date: Sat Aug 10 21:53:43 2013 New Revision: 1512826 URL: http://svn.apache.org/r1512826 Log: Refactor Catalina's TLD processing into Jasper's ServletContainerInitializer. Replaces the TldConfig lifecycle listener with code the SCI to scan for TLDs and register listeners dynamically. Removes the "processTld" property from StandardContext and deprecates other TLD related properties on Context Does not yet address refactoring Jasper's own TLD processing into the SCI. Added: tomcat/trunk/java/org/apache/jasper/servlet/TldScanner.java (with props) tomcat/trunk/test/org/apache/jasper/servlet/TestTldScanner.java (with props) Removed: tomcat/trunk/java/org/apache/catalina/startup/TldConfig.java tomcat/trunk/java/org/apache/catalina/startup/TldRuleSet.java Modified: tomcat/trunk/java/org/apache/catalina/Context.java tomcat/trunk/java/org/apache/catalina/core/StandardContext.java tomcat/trunk/java/org/apache/catalina/storeconfig/server-registry.xml tomcat/trunk/java/org/apache/jasper/resources/LocalStrings.properties tomcat/trunk/java/org/apache/jasper/servlet/JasperInitializer.java tomcat/trunk/test/org/apache/catalina/core/TestStandardContext.java Modified: tomcat/trunk/java/org/apache/catalina/Context.java URL: http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/Context.java?rev=1512826&r1=1512825&r2=1512826&view=diff == --- tomcat/trunk/java/org/apache/catalina/Context.java (original) +++ tomcat/trunk/java/org/apache/catalina/Context.java Sat Aug 10 21:53:43 2013 @@ -621,6 +621,7 @@ public interface Context extends Contain * parsing tlds files. * @param tldValidation true to enable xml instance validation */ +@Deprecated public void setTldValidation(boolean tldValidation); @@ -629,6 +630,7 @@ public interface Context extends Contain * @return true if validation is enabled. * */ +@Deprecated public boolean getTldValidation(); @@ -636,6 +638,7 @@ public interface Context extends Contain * Get the server.xmlattribute's xmlNamespaceAware. * @return true if namespace awareness is enabled. */ +@Deprecated public boolean getTldNamespaceAware(); @@ -644,6 +647,7 @@ public interface Context extends Contain * parsing xml instances. * @param tldNamespaceAware true to enable namespace awareness */ +@Deprecated public void setTldNamespaceAware(boolean tldNamespaceAware); /** Modified: tomcat/trunk/java/org/apache/catalina/core/StandardContext.java URL: http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/core/StandardContext.java?rev=1512826&r1=1512825&r2=1512826&view=diff == --- tomcat/trunk/java/org/apache/catalina/core/StandardContext.java (original) +++ tomcat/trunk/java/org/apache/catalina/core/StandardContext.java Sat Aug 10 21:53:43 2013 @@ -99,7 +99,6 @@ import org.apache.catalina.Wrapper; import org.apache.catalina.deploy.NamingResourcesImpl; import org.apache.catalina.loader.WebappLoader; import org.apache.catalina.session.StandardManager; -import org.apache.catalina.startup.TldConfig; import org.apache.catalina.util.CharsetMapper; import org.apache.catalina.util.ContextName; import org.apache.catalina.util.ExtensionValidator; @@ -707,11 +706,6 @@ public class StandardContext extends Con private boolean webXmlNamespaceAware = Globals.STRICT_SERVLET_COMPLIANCE; /** - * Attribute value used to turn on/off TLD processing - */ -private boolean processTlds = true; - -/** * Attribute value used to turn on/off XML validation */ private boolean tldValidation = Globals.STRICT_SERVLET_COMPLIANCE; @@ -6338,10 +6332,6 @@ public class StandardContext extends Con protected void initInternal() throws LifecycleException { super.initInternal(); -if (processTlds) { -this.addLifecycleListener(new TldConfig()); -} - // Register the naming resources if (namingResources != null) { namingResources.init(); @@ -6518,22 +6508,6 @@ public class StandardContext extends Con } /** - * Sets the process TLDs attribute. - * - * @param newProcessTlds The new value - */ -public void setProcessTlds(boolean newProcessTlds) { -processTlds = newProcessTlds; -} - -/** - * Returns the processTlds attribute value. - */ -public boolean getProcessTlds() { -return processTlds; -} - -/** * Get the server.xml attribute's xmlNamespaceAware. * @return true if namespace awarenes is enabled. */ Modified: tomcat/trunk/java/org/apache/catalina/storeconfig/server-registry.xml URL: http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/storeconfig/serve
buildbot exception in ASF Buildbot on tomcat-trunk
The Buildbot has detected a new failure on builder tomcat-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomcat-trunk/builds/4807 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-vm_ubuntu Build Reason: scheduler Build Source Stamp: [branch tomcat/trunk] 1512826 Blamelist: jboynes BUILD FAILED: exception compile upload_2 sincerely, -The Buildbot
Re: Jasper improvements - web resources and TLDs
On Jul 22, 2013, at 10:10 AM, Mark Thomas wrote: > On 21/07/2013 18:36, Jeremy Boynes wrote: > ... >> In the meantime, I'm going to look at refactoring the TLD support as >> described above. > > Nice. See my note about TLD processing in the TOMCAT-NEXT.txt file in > the root on trunk. I've taken the first step on this in http://svn.apache.org/r1512826 which moves the TLD processing from TldConfig into Jasper's ServletContainerInitializer. There are a couple of implications for this: 1) Jasper's SCI needs to be activated to use TLDs This should cause no impact when ContextConfig is used to configure a web application in the normal way is Jasper is on the class path. When using Context directly in embedded mode, JasperInitializer now need to be added to enable JSP functionality which will automatically TLD processing to add listeners. Previously, TLDs would be scanned automatically unless the processTld property on StandardContext was explicitly set false. IOW, TLDs will only be processed if JSP functionality is added, and don't need to be turned off if it is not. 2) As part of the change for processTlds I deprecated the operations on Context to set/get TLD processing properties (for validation and namespace) as they are can't be used by Jasper's SCI. If there are no objections to an API change at this stage I will go ahead and remove them completely. XML validation for TLDs can now be controlled via the "org.apache.jasper.validateDescriptors" initParam for the ServletContext; namespace processing is always on as we require >3.0 (due to the SCI etc.) which uses namespaces anyway 3) TldScanner parses TLDs as it goes creating a cache of parsed values keyed off TLD URI. It should probably create a second mapping from "TLD resource path" to the parse result in order to handle taglib directives that specify paths. I'll look at that when refactoring the Jasper side. That will also allow the second scan to be removed. Cheers Jeremy signature.asc Description: Message signed with OpenPGP using GPGMail
svn commit: r1512834 - in /tomcat/trunk/java/org/apache/catalina/startup: LocalStrings.properties LocalStrings_es.properties
Author: jboynes
Date: Sat Aug 10 22:41:53 2013
New Revision: 1512834
URL: http://svn.apache.org/r1512834
Log:
Remove old TldConfig related message
Modified:
tomcat/trunk/java/org/apache/catalina/startup/LocalStrings.properties
tomcat/trunk/java/org/apache/catalina/startup/LocalStrings_es.properties
Modified: tomcat/trunk/java/org/apache/catalina/startup/LocalStrings.properties
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/startup/LocalStrings.properties?rev=1512834&r1=1512833&r2=1512834&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/startup/LocalStrings.properties
(original)
+++ tomcat/trunk/java/org/apache/catalina/startup/LocalStrings.properties Sat
Aug 10 22:41:53 2013
@@ -110,18 +110,6 @@ hostConfig.start=HostConfig: Processing
hostConfig.stop=HostConfig: Processing STOP
hostConfig.undeploy=Undeploying context [{0}]
hostConfig.undeployVersion=Undeploying old version of context [{0}] which has
no active session
-tldConfig.addListeners=Adding {0} listeners from TLD files
-tldConfig.cce=Lifecycle event data object {0} is not a Context
-tldConfig.dirFail=Failed to process directory [{0}] for TLD files
-tldConfig.dirScan=Scanning for TLD files in directory [{0}]
-tldConfig.execute=Error processing TLD files for context with name [{0}]
-tldConfig.jarFail=Failed to process JAR [{0}] for TLD files
-tldConfig.webinfFail=Failed to process TLD found at [{0}]
-tldConfig.webinfScan=Scanning WEB-INF for TLD files in [{0}]
-tldConfig.webxmlAdd=Adding path [{0}] for URI [{1}]
-tldConfig.webxmlFail=Failed to process TLD with path [{1}] and URI [{0}]
-tldConfig.webxmlSkip=Path [{1}] skipped since URI [{0}] is a duplicate
-tldConfig.webxmlStart=Scanning elements in web.xml
userConfig.database=Exception loading user database
userConfig.deploy=Deploying web application for user {0}
userConfig.deploying=Deploying user web applications
Modified:
tomcat/trunk/java/org/apache/catalina/startup/LocalStrings_es.properties
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/startup/LocalStrings_es.properties?rev=1512834&r1=1512833&r2=1512834&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/startup/LocalStrings_es.properties
(original)
+++ tomcat/trunk/java/org/apache/catalina/startup/LocalStrings_es.properties
Sat Aug 10 22:41:53 2013
@@ -88,18 +88,6 @@ hostConfig.reload = Fall\u00F3 la recarg
hostConfig.start = "HostConfig"\: Procesando "START"
hostConfig.stop = "HostConfig"\: Procesando "STOP"
hostConfig.undeploy = Repliegue (undeploy) de la aplicaci\u00F3n web que tiene
como trayectoria de contexto {0}
-tldConfig.addListeners = A\u00F1adiendo {0} oyentes desde ficheros TLD
-tldConfig.cce = El objeto de datos de eventos de Ciclo de vida {0} no se
encuentra en el Contexto
-tldConfig.dirFail = No pude procesar el directorio [{0}] para ficheros TLD
-tldConfig.dirScan = Explorando en busca de ficheros TLD en directorio [{0}]
-tldConfig.execute = Error al procesar ficheros TLD para el contexto con nombre
[{0}]
-tldConfig.jarFail = No pude procesar el JAR [{0}] para ficheros TLD
-tldConfig.webinfFail = No pude procesar TLD hallado en [{0}]
-tldConfig.webinfScan = Esplorando WEB-INF en busca de ficheros TLD en [{0}]
-tldConfig.webxmlAdd = A\u00F1adiendo ruta [{0}] para URI [{1}]
-tldConfig.webxmlFail = No pude procesar TLD con ruta [{1}] y URI [{0}]
-tldConfig.webxmlSkip = La ruta [{1}] saltada desde URI [{0}] es un duplicado
-tldConfig.webxmlStart = Explorando elementos en web.xml
userConfig.database = Excepci\u00F3n durante la carga de base de datos de
usuario
userConfig.deploy = Despliegue de la aplicaci\u00F3n web para el usuario {0}
userConfig.deploying = Desplegando aplicaciones web para el usuario
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1512837 - in /tomcat/trunk: java/org/apache/jasper/resources/LocalStrings.properties webapps/docs/config/systemprops.xml
Author: jboynes
Date: Sat Aug 10 22:42:57 2013
New Revision: 1512837
URL: http://svn.apache.org/r1512837
Log:
Remove references to TldConfig.jarsToSkip system properties that were not
copied over using JarScanner refactoring
Modified:
tomcat/trunk/java/org/apache/jasper/resources/LocalStrings.properties
tomcat/trunk/webapps/docs/config/systemprops.xml
Modified: tomcat/trunk/java/org/apache/jasper/resources/LocalStrings.properties
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/jasper/resources/LocalStrings.properties?rev=1512837&r1=1512836&r2=1512837&view=diff
==
--- tomcat/trunk/java/org/apache/jasper/resources/LocalStrings.properties
(original)
+++ tomcat/trunk/java/org/apache/jasper/resources/LocalStrings.properties Sat
Aug 10 22:42:57 2013
@@ -391,7 +391,7 @@ jsp.message.jsp_unload_check=Checking JS
xmlParser.skipBomFail=Failed to skip BOM when parsing XML input stream
-jsp.tldCache.noTldInJar=No TLD files were found in [{0}]. Consider adding the
JAR to the tomcat.util.scan.DefaultJarScanner.jarsToSkip or
org.apache.catalina.startup.TldConfig.jarsToSkip property in
CATALINA_BASE/conf/catalina.properties file.
+jsp.tldCache.noTldInJar=No TLD files were found in [{0}]. Consider adding the
JAR to the tomcat.util.scan.DefaultJarScanner.jarsToSkip property in
CATALINA_BASE/conf/catalina.properties file.
jsp.tldCache.noTldSummary=At least one JAR was scanned for TLDs yet contained
no TLDs. Enable debug logging for this logger for a complete list of JARs that
were scanned but no TLDs were found in them. Skipping unneeded JARs during
scanning can improve startup time and JSP compilation time.
#ELInterpreter
Modified: tomcat/trunk/webapps/docs/config/systemprops.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/systemprops.xml?rev=1512837&r1=1512836&r2=1512837&view=diff
==
--- tomcat/trunk/webapps/docs/config/systemprops.xml (original)
+++ tomcat/trunk/webapps/docs/config/systemprops.xml Sat Aug 10 22:42:57 2013
@@ -565,13 +565,6 @@
$CATALINA_BASE/conf/catalina.properties file.
-
- The comma-separated list of additional filenames of JARs that Tomcat
- will not scan for TLDs.
- The coded default is that no JARs are skipped however the system
- property is set in a default Tomcat installation via the
- $CATALINA_BASE/conf/catalina.properties file.
-
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 55399] Request English but Response Spanish Language (Default Locale)
https://issues.apache.org/bugzilla/show_bug.cgi?id=55399
Christopher Schultz changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #1 from Christopher Schultz ---
What version of Tomcat?
Can you echo these items back to the client and post the output:
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
// ...
ServletWriter out = response.getWriter();
out.println("request locale=" + request.getLocale());
out.println("server locale=" + Locale.getDefault());
response.sendError(HttpServletResponse.SC_BAD_REQUEST, "BAD REQUEST");
}
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
