cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/coyote/tomcat5 CoyoteConnector.java
billbarker2003/08/17 23:43:29 Modified:catalina/src/share/org/apache/coyote/tomcat5 CoyoteConnector.java Log: Fixing getters for JMX. It looks like a big commit, but it really shouldn't be very much in terms of functionality. All default values are (almost) removed from the Connector. This may break other components that were depending on them. However that is why I'm committing now (so I can get more eyes to find the broken components). I've kludged getScheme for now, so that Tomcat is more or less functional. However, it looks like there is still a fair amount of cleanup to do in getting the default values set for the protocols. Revision ChangesPath 1.23 +141 -353 jakarta-tomcat-catalina/catalina/src/share/org/apache/coyote/tomcat5/CoyoteConnector.java Index: CoyoteConnector.java === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/coyote/tomcat5/CoyoteConnector.java,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- CoyoteConnector.java 11 Aug 2003 21:44:16 - 1.22 +++ CoyoteConnector.java 18 Aug 2003 06:43:29 - 1.23 @@ -128,48 +128,15 @@ /** - * The accept count for this Connector. - */ -private int acceptCount = 10; - - -/** - * The IP address on which to bind, if any. If codenull/code, all - * addresses on the server will be bound. - */ -private String address = null; - - -/** - * The input buffer size we should create on input streams. - */ -private int bufferSize = 2048; - - -/** * The Container used for processing requests received by this Connector. */ protected Container container = null; - -/** - * Compression value. - */ -private String compression = off; - - /** * The debugging detail level for this component. */ private int debug = 0; - -/** - * The enable DNS lookups flag for this Connector. - */ -private boolean enableLookups = false; - - /** * The server socket factory for this component. */ @@ -196,114 +163,11 @@ /** - * The minimum number of processors to start at initialization time. - */ -protected int minProcessors = 5; - - -/** - * The maximum number of processors allowed, or 0 for unlimited. - */ -private int maxProcessors = 20; - - -/** - * Linger value on the incoming connection. - * Note : a value inferior to 0 means no linger. - */ -private int connectionLinger = Constants.DEFAULT_CONNECTION_LINGER; - - -/** - * Timeout value on the incoming connection. - * Note : a value of 0 means no timeout. - */ -private int connectionTimeout = Constants.DEFAULT_CONNECTION_TIMEOUT; - - -/** - * Timeout value on the incoming connection during request processing. - * Note : a value of 0 means no timeout. - */ -private int connectionUploadTimeout = -Constants.DEFAULT_CONNECTION_UPLOAD_TIMEOUT; - - -/** - * Timeout value on the server socket. - * Note : a value of 0 means no timeout. - */ -private int serverSocketTimeout = Constants.DEFAULT_SERVER_SOCKET_TIMEOUT; - - -/** - * The port number on which we listen for requests. - */ -private int port = 8080; - - -/** - * The server name to which we should pretend requests to this Connector - * were directed. This is useful when operating Tomcat behind a proxy - * server, so that redirects get constructed accurately. If not specified, - * the server name included in the codeHost/code header is used. - */ -private String proxyName = null; - - -/** - * The server port to which we should pretent requests to this Connector - * were directed. This is useful when operating Tomcat behind a proxy - * server, so that redirects get constructed accurately. If not specified, - * the port number specified by the codeport/code property is used. - */ -private int proxyPort = 0; - - -/** - * The redirect port for non-SSL to SSL redirects. - */ -private int redirectPort = 443; - - -/** - * The request scheme that will be set on all requests received - * through this connector. - */ -private String scheme = http; - - -/** - * The secure connection flag that will be set on all requests received - * through this connector. - */ -private boolean secure = false; - -/** For jk, do tomcat authentication if true, trust server if false - */ -
DO NOT REPLY [Bug 22501] New: - Taglib evalution problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22501. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22501 Taglib evalution problem Summary: Taglib evalution problem Product: Tomcat 4 Version: 4.1.24 Platform: PC OS/Version: Windows NT/2K Status: UNCONFIRMED Severity: Major Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] I'm working on a medium-scale enterprise app in BES 5.2.1. My presentation tier consists of JSP pages served by Tomcat, and I am using the JSTL fmt tags to provide i18n support for my application. I wish to pass a parameter into the fmt tag as the key, the parameter coming from posted form data. e.g. fmt:message key=%= request.getParameter(action) % / I experienced problems using this method however. It seems that the request.getParameter part wasn't evaluated inside the tag for some reason, resulting in ???title??? as the output on the page if the action parameter had the value of title. I did some research on the newsgroups and discoverd that the body of the format tag can also be used as the key. e.g. fmt:message%= request.getParamger(action) %/fmt:message However this still didn't work, and produced the same output as above. Just as a shot in the dark, I tried running both examples on standalone Tomcat (i.e. not inside BES) which ships with JBuilder 9 (version 4.0.x). Everything worked fine!! However, the example fails again under standalone 4.1.24 which ships with JBuilder. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22502] New: - Jasper can't parse a XML format JSP file encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22502.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22502
Jasper can't parse a XML format JSP file encoding
Summary: Jasper can't parse a XML format JSP file encoding
Product: Tomcat 4
Version: 4.1.27
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Tomcat5 is able to parse a XML format JSP file encoding, but Tomcat4 isn't.
I thought org.xml.sax.InputSource didn't instantiate with java.io.InputStream.
So, I read Jasper source and made two patches as follows.
jakarta-tomcat-4.1.27-src/jasper/src/share/org/apache/jasper/compiler/JspDocumentParser.java
jakarta-tomcat-4.1.27-src/jasper/src/share/org/apache/jasper/compiler/ParserController.java
--- original/JspDocumentParser.java Mon Aug 18 14:26:17 2003
+++ ../jakarta-tomcat-4.1.27-src/jasper/src/share/org/apache/jasper/compiler/Jsp
DocumentParser.java Mon Aug 18 16:25:27 2003
@@ -128,6 +128,16 @@
this.path = path;
this.inputSource = new InputSource(reader);
}
+public JspDocumentParser(ParserController pc,
+String path,
+InputStream inputstream) {
+ this.parserController = pc;
+ this.ctxt = pc.getJspCompilationContext();
+ this.taglibs = pc.getCompiler().getPageInfo().getTagLibraries();
+ this.err = pc.getCompiler().getErrorDispatcher();
+ this.path = path;
+ this.inputSource = new InputSource(inputstream);
+}
/*
* Parses a JSP document by responding to SAX events.
@@ -139,6 +149,46 @@
InputStreamReader reader,
Node parent) throws JasperException {
JspDocumentParser handler = new JspDocumentParser(pc, path, reader);
+ handler.current = parent;
+ Node.Nodes pageNodes = null;
+
+ try {
+ // Use the default (non-validating) parser
+ SAXParserFactory factory = SAXParserFactory.newInstance();
+
+ // Configure the parser
+ SAXParser saxParser = factory.newSAXParser();
+ XMLReader xmlReader = saxParser.getXMLReader();
+ xmlReader.setProperty(LEXICAL_HANDLER_PROPERTY, handler);
+ xmlReader.setErrorHandler(handler);
+
+ // Parse the input
+ saxParser.parse(handler.inputSource, handler);
+
+ if (parent == null) {
+ // Add the jsp:root element to the parse result
+ pageNodes = new Node.Nodes((Node.JspRoot) handler.current);
+ } else {
+ pageNodes = parent.getBody();
+ }
+ } catch (IOException ioe) {
+ handler.err.jspError(jsp.error.data.file.read, path, ioe);
+ } catch (Exception e) {
+ handler.err.jspError(e);
+ }
+
+ return pageNodes;
+}
+/*
+ * Parses a JSP document by responding to SAX events.
+ *
+ * @throws JasperException XXX
+ */
+public static Node.Nodes parse(ParserController pc,
+ String path,
+ InputStream inputstream,
+ Node parent) throws JasperException {
+ JspDocumentParser handler = new JspDocumentParser(pc, path, inputstream)
;
handler.current = parent;
Node.Nodes pageNodes = null;
--- original/ParserController.java Mon Aug 18 14:26:24 2003
+++ ../jakarta-tomcat-4.1.27-src/jasper/src/share/org/apache/jasper/compiler/Par
serController.java Mon Aug 18 16:29:06 2003
@@ -167,6 +167,7 @@
String absFileName = resolveFileName(inFileName);
String encoding = topFileEncoding;
InputStreamReader reader = null;
+ InputStream is = null;
try {
// Figure out what type of JSP document we are dealing with
reader = getReader(absFileName, encoding);
@@ -188,11 +189,12 @@
// dispatch to the proper parser
-reader = getReader(absFileName, encoding);
if (isXml) {
-parsedPage = JspDocumentParser.parse(this, absFileName,
-reader, parent);
+ is = getInputStream(absFileName);
+parsedPage = JspDocumentParser.parse(this, absFileName, is,
+parent);
} else {
+ reader = getReader(absFileName, encoding);
JspReader r = new
DO NOT REPLY [Bug 22503] New: - Tomcat4.0.6 can't parse a XML format JSP file encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22503.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22503
Tomcat4.0.6 can't parse a XML format JSP file encoding
Summary: Tomcat4.0.6 can't parse a XML format JSP file encoding
Product: Tomcat 4
Version: 4.0.6 Final
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Tomcat5 is able to parse a XML format JSP file encoding, but Tomcat4 isn't.
I thought org.xml.sax.InputSource didn't instantiate with java.io.InputStream.
So, I read Jasper source and made two patches as follows.
jakarta-tomcat-4.0.6-src/jasper/src/share/org/apache/jasper/compiler/ParserController.java
jakarta-tomcat-4.0.6-src/jasper/src/share/org/apache/jasper/compiler/ParserXJspSax.java
--- original/ParserController.java Sun Aug 17 17:15:53 2003
+++ ParserController.java Sun Aug 17 17:17:37 2003
@@ -209,7 +209,7 @@
reader = getReader(absFileName, encoding);
jspHandler.setDefault(isXml);
if (isXml) {
-(new ParserXJspSax(absFileName, reader, jspHandler)).parse();
+(new ParserXJspSax(absFileName, getStream(absFileName), jspHand
ler)).parse();
} else {
(new Parser(ctxt, absFileName, encoding, reader, jspHandler)).p
arse();
}
@@ -443,6 +443,16 @@
}
}
+private InputStream getStream(String file)
+ throws FileNotFoundException
+{
+InputStream in;
+ in = ctxt.getResourceAsStream(file);
+ if (in == null) {
+ throw new FileNotFoundException(file);
+ }
+ return in;
+}
/* NOT COMPILED
private String getFileContent(String fileName) {
InputStream inStream;
#
--- original/ParserXJspSax.java Sun Aug 17 17:16:01 2003
+++ ParserXJspSax.java Sun Aug 17 17:17:14 2003
@@ -136,6 +136,15 @@
this.jspHandler = jspHandler;
}
+public ParserXJspSax(String filePath,
+InputStream stream,
+ParseEventListener jspHandler)
+{
+ this.filePath = filePath;
+ this.is = new InputSource(stream);
+ this.jspHandler = jspHandler;
+}
+
//*
// Parse
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
destroy not called if permanently unavailable exception is thrown
Hi, I'm using Tomcat 4.1.27. When I throw an UnavailableException in my Servlet marked as permanently the destroy method of the servlet doesn't seem to be called. In fact in looks like permanently unavailability is treated as a temporally unavailability with the available time set to Long.MAX_VALUE. This looks similar to bug 3209 (http://issues.apache.org/bugzilla/show_bug.cgi?id=3209). regards, Hendrik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20674] - Error in running Tag Files in Tomcat5.0.7 after removing JSPC mapping
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20674. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20674 Error in running Tag Files in Tomcat5.0.7 after removing JSPC mapping [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] URL|http://none.right.now |http://192.168.0.210:8080/js ||p- ||examples/jsp2/simpletag/hell ||o.jsp Severity|Normal |Critical Component|Jasper 2|Webapps:Examples Keywords||ErrorMessage OS/Version|Windows XP |Linux Priority|Other |High Product|Tomcat 4|Tomcat 5 Summary|Tomcat is not compliant with|Error in running Tag Files |the JSP 1.2 specification. |in Tomcat5.0.7 after ||removing JSPC mapping Version|4.1.24 |Nightly Build --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 11:18 --- There is problem in running the Jsp Tag files after removing the JSPC generated servlet-mappings and directly accessing the JSP file in Tomcat5.0.7 java.lang.IllegalArgumentException: -52 org.apache.jasper.compiler.SmapStratum$LineInfo.setOutputLineIncrement (SmapStratum.java:124) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22508] New: - Error in running Tag Files in Tomcat5.0.7 after removing JSPC generated mapping
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22508. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22508 Error in running Tag Files in Tomcat5.0.7 after removing JSPC generated mapping Summary: Error in running Tag Files in Tomcat5.0.7 after removing JSPC generated mapping Product: Tomcat 5 Version: 5.0.7 Platform: Other URL: http://localhost:8080/jsp- examples/jsp2/simpletag/hello.jsp OS/Version: Linux Status: NEW Severity: Critical Priority: Other Component: Webapps:Examples AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] There is problem in running the Jsp Tag files after removing the JSPC generated servlet-mappings and directly accessing the JSP file in Tomcat5.0.7 root cause java.lang.IllegalArgumentException: -52 org.apache.jasper.compiler.SmapStratum$LineInfo.setOutputLineIncrement (SmapStratum.java:124) org.apache.jasper.compiler.SmapStratum.optimizeLineSection (SmapStratum.java:221) org.apache.jasper.compiler.SmapUtil.evaluateNodes(SmapUtil.java:490) org.apache.jasper.compiler.SmapUtil.generateSmap(SmapUtil.java:123) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:301) org.apache.jasper.compiler.Compiler.compile(Compiler.java:453) org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) org.apache.jasper.JspCompilationContext.compile (JspCompilationContext.java:555) org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:300) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:293) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) javax.servlet.http.HttpServlet.service(HttpServlet.java:856) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
request
Hi , My name is majesh and i am a beginer in the feildof linux webserver administration.I am now in the study of connecting tomcat and redhat linux 8.0 apache.Will you please give me the steps required to accomplish this for me . waiting for your reply, A student
Re: request
Majesh, first of all, you should peruse the fine documentation on this subject that is readily available on the jakarta tomcat website. furthermore you should read it more thoroughly than the mailing-list instructions. quote Do not send mail to this list with usage questions or configuration problems -- that's what tomcat-user is for. best regards matthias -- Matthias Ernst Software Engineer CoreMedia - Smart Content Technology - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] New committer: Eric Carmichael
+1 (If more votes are still needed) -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20674] - Tomcat is not compliant with the JSP 1.2 specification.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20674. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20674 Tomcat is not compliant with the JSP 1.2 specification. [EMAIL PROTECTED] changed: What|Removed |Added URL|http://192.168.0.210:8080/js|http://none.right.now |p- | |examples/jsp2/simpletag/hell| |o.jsp | Severity|Critical|Normal Component|Webapps:Examples|Jasper 2 OS/Version|Linux |Windows XP Priority|High|Other Product|Tomcat 5|Tomcat 4 Summary|Error in running Tag Files |Tomcat is not compliant with |in Tomcat5.0.7 after|the JSP 1.2 specification. |removing JSPC mapping | Version|Nightly Build |4.1.24 --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 14:12 --- IllegalArgumentException in setOutputLineIncrement() is Bugzilla Bug 22277, and is fixed in CVS. Also I'm resetting the field values for this bug report to their previous values, as Bugzilla Bug 22277 is not related to this one. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22508] - Error in running Tag Files in Tomcat5.0.7 after removing JSPC generated mapping
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22508. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22508 Error in running Tag Files in Tomcat5.0.7 after removing JSPC generated mapping [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 14:13 --- *** This bug has been marked as a duplicate of 22277 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22277] - IllegalArgumentException in setOutputLineIncrement()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22277. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22277 IllegalArgumentException in setOutputLineIncrement() [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 14:13 --- *** Bug 22508 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22466] - StackOverflowError in ResponseBase.write (no recursion)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22466. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22466 StackOverflowError in ResponseBase.write (no recursion) --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 14:23 --- Confirmed that this problem does not occur on Window 2000 sp3, using the same version of Java, JBoss/Tomcat, and Struts. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PATCH] jakarta-servletapi-5: Schema updates
The following is a patch to the JSP 2.0 TLD and J2EE 1.4 schemas based
on recent specification changes.
jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd
jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd
- Made body-content element mandatory since default valid
is unusable for Simple Tag Handlers.
jsr154/src/share/dtd/j2ee_1_4.xsd
- Updated to latest J2EE 1.4 schema
- Moved java-typeType to common file.
---
Mark Roth, Java Software
JSP 2.0 Co-Specification Lead
Sun Microsystems, Inc.
Index: jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd
===
RCS file:
/home/cvspublic/jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd,v
retrieving revision 1.12
diff -u -r1.12 web-jsptaglibrary_2_0.xsd
--- jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd 16 May 2003 23:20:17 -
1.12
+++ jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd 18 Aug 2003 14:25:09 -
@@ -472,12 +472,15 @@
/xsd:annotation
/xsd:element
xsd:element name=body-content
- type=j2ee:body-contentType
- minOccurs=0
+ type=j2ee:body-contentType
xsd:annotation
xsd:documentation
- The default (if not defined) is JSP
+ Specifies the format for the body of this tag.
+ The default in JSP 1.2 was JSP but because this is an invalid
+ setting for simple tag handlers, there is no longer a default
+ in JSP 2.0. A reasonable default for simple tag handlers is
+ scriptless if the tag can have a body.
/xsd:documentation
/xsd:annotation
Index: jsr154/src/share/dtd/j2ee_1_4.xsd
===
RCS file: /home/cvspublic/jakarta-servletapi-5/jsr154/src/share/dtd/j2ee_1_4.xsd,v
retrieving revision 1.8
diff -u -r1.8 j2ee_1_4.xsd
--- jsr154/src/share/dtd/j2ee_1_4.xsd 16 May 2003 23:20:18 - 1.8
+++ jsr154/src/share/dtd/j2ee_1_4.xsd 18 Aug 2003 14:25:09 -
@@ -8,7 +8,7 @@
version=1.4
xsd:annotation
xsd:documentation
- %W% %E%
+ @(#)j2ee_1_4.xsds1.42 03/08/01
/xsd:documentation
/xsd:annotation
@@ -637,6 +637,25 @@
xsd:simpleContent
xsd:restriction base=j2ee:string
xsd:pattern value=($|_|\p{L})(\p{L}|\p{Nd}|_|$)*/
+ /xsd:restriction
+/xsd:simpleContent
+ /xsd:complexType
+
+!-- --
+
+ xsd:complexType name=java-typeType
+xsd:annotation
+ xsd:documentation
+
+ This is a generic type that designates a Java primitive
+ type or a fully qualified name of a Java interface/type,
+ or an array of such types.
+
+ /xsd:documentation
+/xsd:annotation
+xsd:simpleContent
+ xsd:restriction base=j2ee:string
+ xsd:pattern value=[^\p{Z}]*/
/xsd:restriction
/xsd:simpleContent
/xsd:complexType
Index: jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd
===
RCS file:
/home/cvspublic/jakarta-servletapi-5/jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd,v
retrieving revision 1.12
diff -u -r1.12 web-jsptaglibrary_2_0.xsd
--- jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd 16 May 2003 23:20:18 -
1.12
+++ jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd 18 Aug 2003 14:25:09 -
@@ -472,12 +472,15 @@
/xsd:annotation
/xsd:element
xsd:element name=body-content
- type=j2ee:body-contentType
- minOccurs=0
+ type=j2ee:body-contentType
xsd:annotation
xsd:documentation
- The default (if not defined) is JSP
+ Specifies the format for the body of this tag.
+ The default in JSP 1.2 was JSP but because this is an invalid
+ setting for simple tag handlers, there is no longer a default
+ in JSP 2.0. A reasonable default for simple tag handlers is
+ scriptless if the tag can have a body.
/xsd:documentation
/xsd:annotation
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
MBeanServer problem
Hello, I hope I post this in the right place. When restating a context in tomcat 4.1.24 the ServletContext lose the reference to the MBeanServer instance. The ServerLifeCycleListener set an attribute named 'org.apache.catalina.MBeanServer' in the ServletContext when tomcat starts up but once a context is reloaded... this attribute is gone and it is no more possible to access the MBeanServer. I took a look in the org.apache.catalina.mbeans.ServerLifeCycleListener code and there is a context reload event that suppose to create a new MBeanServer and set it as an attribute in the servelcontext, but actually it does not happening. I would appreciae any response and hope I do not waste your time Adi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[5.0.8] Tag soon
As most (all ?) of the issues uncovered in build 5.0.7 have been fixed or addressed in some way, I plan to tag and release 5.0.8 soon (likely wednesday). Please apply any fixes before then (but please no features addition or refactorings), such as the servlet API updates. Thanks :) (hopefully, we'll have a good quality build this time :) ) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 build.xml
jfarcand2003/08/18 09:34:42
Modified:.build.xml
Log:
Minor cleanup (modeler is now released or soon to be)
Revision ChangesPath
1.150 +0 -7 jakarta-tomcat-5/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
retrieving revision 1.149
retrieving revision 1.150
diff -u -r1.149 -r1.150
--- build.xml 10 Aug 2003 09:53:37 - 1.149
+++ build.xml 18 Aug 2003 16:34:42 - 1.150
@@ -117,13 +117,6 @@
srcfiles dir=${catalina.home}/webapps/admin includes=** /
/uptodate
-!--
-uptodate property=commons-modeler.build.notrequired
- targetfile=${commons-modeler.jar}
- srcfiles dir=${cvs.base}/jakarta-commons/modeler/src/java includes=** /
-/uptodate
---
-
uptodate property=commons-daemon.build.notrequired
targetfile=${commons-daemon.jar}
srcfiles dir=${cvs.base}/jakarta-commons-sandbox/daemon/src includes=**
/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-servletapi-5/jsr154/src/share/javax/servlet/http Cookie.java HttpServlet.java HttpServletRequest.java HttpServletResponse.java HttpSession.java HttpSessionListener.java
jfarcand2003/08/18 09:50:33 Modified:jsr154/src/share/javax/servlet Filter.java FilterConfig.java ServletConfig.java ServletContext.java ServletContextAttributeEvent.java ServletContextListener.java ServletOutputStream.java ServletRequest.java ServletResponse.java UnavailableException.java jsr154/src/share/javax/servlet/http Cookie.java HttpServlet.java HttpServletRequest.java HttpServletResponse.java HttpSession.java HttpSessionListener.java Log: Apply documentation patch submitted by Yutaka Yoshida at sun.com Revision ChangesPath 1.2 +2 -2 jakarta-servletapi-5/jsr154/src/share/javax/servlet/Filter.java Index: Filter.java === RCS file: /home/cvs/jakarta-servletapi-5/jsr154/src/share/javax/servlet/Filter.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Filter.java 13 Aug 2002 16:21:42 - 1.1 +++ Filter.java 18 Aug 2003 16:50:33 - 1.2 @@ -63,7 +63,7 @@ import java.io.IOException; /** - * A filter is an object than perform filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both. + * A filter is an object that performs filtering tasks on either the request to a resource (a servlet or static content), or on the response from a resource, or both. * brbr * Filters perform filtering in the codedoFilter/code method. Every Filter has access to ** a FilterConfig object from which it can obtain its initialization parameters, a @@ -114,7 +114,7 @@ * filter content or headers for output filtering br * 4. a) strongEither/strong invoke the next entity in the chain using the FilterChain object (codechain.doFilter()/code), br ** 4. b) strongor/strong not pass on the request/response pair to the next entity in the filter chain to block the request processingbr - ** 5. Directly set headers on the response after invokation of the next entity in ther filter chain. + ** 5. Directly set headers on the response after invocation of the next entity in ther filter chain. **/ public void doFilter ( ServletRequest request, ServletResponse response, FilterChain chain ) throws IOException, ServletException; 1.2 +4 -4 jakarta-servletapi-5/jsr154/src/share/javax/servlet/FilterConfig.java Index: FilterConfig.java === RCS file: /home/cvs/jakarta-servletapi-5/jsr154/src/share/javax/servlet/FilterConfig.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- FilterConfig.java 13 Aug 2002 16:21:42 - 1.1 +++ FilterConfig.java 18 Aug 2003 16:50:33 - 1.2 @@ -68,7 +68,7 @@ /** * * A filter configuration object used by a servlet container - * used to pass information to a filter during initialization. + * to pass information to a filter during initialization. * @see Filter * @since Servlet 2.3 * @@ -116,13 +116,13 @@ /** - * Returns the names of the servlet's initialization parameters + * Returns the names of the filter's initialization parameters * as an codeEnumeration/code of codeString/code objects, - * or an empty codeEnumeration/code if the servlet has + * or an empty codeEnumeration/code if the filter has * no initialization parameters. * * @return an codeEnumeration/code of codeString/code - * objects containing the names of the servlet's + * objects containing the names of the filter's * initialization parameters * * 1.2 +1 -1 jakarta-servletapi-5/jsr154/src/share/javax/servlet/ServletConfig.java Index: ServletConfig.java === RCS file: /home/cvs/jakarta-servletapi-5/jsr154/src/share/javax/servlet/ServletConfig.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ServletConfig.java13 Aug 2002 16:21:43 - 1.1 +++ ServletConfig.java18 Aug 2003 16:50:33 - 1.2 @@ -67,7 +67,7 @@ /** * * A servlet configuration object used by a servlet container - * used to pass information to a servlet during initialization. + * to pass information to a servlet during initialization. * */ 1.4 +6 -2
cvs commit: jakarta-servletapi-5/jsr154/src/share/dtd j2ee_1_4.xsd web-jsptaglibrary_2_0.xsd
kinman 2003/08/18 10:41:20
Modified:jsr152/src/share/dtd web-jsptaglibrary_2_0.xsd
jsr154/src/share/dtd j2ee_1_4.xsd web-jsptaglibrary_2_0.xsd
Log:
- Patch by Mark Roth
Patch to the JSP 2.0 TLD and J2EE 1.4 schemas based on recent
specification changes.
jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd
jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd
- Made body-content element mandatory since default valid
is unusable for Simple Tag Handlers.
jsr154/src/share/dtd/j2ee_1_4.xsd
- Updated to latest J2EE 1.4 schema
- Moved java-typeType to common file.
Revision ChangesPath
1.13 +6 -3
jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd
Index: web-jsptaglibrary_2_0.xsd
===
RCS file:
/home/cvs/jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- web-jsptaglibrary_2_0.xsd 16 May 2003 23:20:17 - 1.12
+++ web-jsptaglibrary_2_0.xsd 18 Aug 2003 17:41:20 - 1.13
@@ -472,12 +472,15 @@
/xsd:annotation
/xsd:element
xsd:element name=body-content
-type=j2ee:body-contentType
-minOccurs=0
+type=j2ee:body-contentType
xsd:annotation
xsd:documentation
- The default (if not defined) is JSP
+ Specifies the format for the body of this tag.
+ The default in JSP 1.2 was JSP but because this is an invalid
+ setting for simple tag handlers, there is no longer a default
+ in JSP 2.0. A reasonable default for simple tag handlers is
+ scriptless if the tag can have a body.
/xsd:documentation
/xsd:annotation
1.9 +20 -1 jakarta-servletapi-5/jsr154/src/share/dtd/j2ee_1_4.xsd
Index: j2ee_1_4.xsd
===
RCS file: /home/cvs/jakarta-servletapi-5/jsr154/src/share/dtd/j2ee_1_4.xsd,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- j2ee_1_4.xsd 16 May 2003 23:20:18 - 1.8
+++ j2ee_1_4.xsd 18 Aug 2003 17:41:20 - 1.9
@@ -8,7 +8,7 @@
version=1.4
xsd:annotation
xsd:documentation
- %W% %E%
+ @(#)j2ee_1_4.xsds 1.42 03/08/01
/xsd:documentation
/xsd:annotation
@@ -637,6 +637,25 @@
xsd:simpleContent
xsd:restriction base=j2ee:string
xsd:pattern value=($|_|\p{L})(\p{L}|\p{Nd}|_|$)*/
+ /xsd:restriction
+/xsd:simpleContent
+ /xsd:complexType
+
+!-- --
+
+ xsd:complexType name=java-typeType
+xsd:annotation
+ xsd:documentation
+
+ This is a generic type that designates a Java primitive
+ type or a fully qualified name of a Java interface/type,
+ or an array of such types.
+
+ /xsd:documentation
+/xsd:annotation
+xsd:simpleContent
+ xsd:restriction base=j2ee:string
+ xsd:pattern value=[^\p{Z}]*/
/xsd:restriction
/xsd:simpleContent
/xsd:complexType
1.13 +6 -3
jakarta-servletapi-5/jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd
Index: web-jsptaglibrary_2_0.xsd
===
RCS file:
/home/cvs/jakarta-servletapi-5/jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- web-jsptaglibrary_2_0.xsd 16 May 2003 23:20:18 - 1.12
+++ web-jsptaglibrary_2_0.xsd 18 Aug 2003 17:41:20 - 1.13
@@ -472,12 +472,15 @@
/xsd:annotation
/xsd:element
xsd:element name=body-content
-type=j2ee:body-contentType
-minOccurs=0
+type=j2ee:body-contentType
xsd:annotation
xsd:documentation
- The default (if not defined) is JSP
+ Specifies the format for the body of this tag.
+ The default in JSP 1.2 was JSP but because this is an invalid
+ setting for simple tag handlers, there is no longer a default
+ in JSP 2.0. A reasonable default for simple tag handlers is
+ scriptless if the tag can have a body.
/xsd:documentation
/xsd:annotation
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup ContextConfig.java
remm2003/08/18 10:44:20
Modified:catalina/src/share/org/apache/catalina/startup
ContextConfig.java
Log:
- Fix cut paste bug.
- Schema validation is now consistently broken between the deployer validator
task and the integrated Tomcat validation.
- I'll disable schema validation in 5.0.8 if this is not fixed.
Revision ChangesPath
1.29 +3 -3
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/ContextConfig.java
Index: ContextConfig.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/ContextConfig.java,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- ContextConfig.java19 Jul 2003 16:13:36 - 1.28
+++ ContextConfig.java18 Aug 2003 17:44:20 - 1.29
@@ -67,7 +67,7 @@
import java.io.FileNotFoundException;
import java.io.InputStream;
import java.io.IOException;
-import java.net.JarURLConnection;
+import java.net.URLConnection;
import java.net.URL;
import java.util.Enumeration;
import java.util.HashSet;
@@ -492,7 +492,7 @@
url = ContextConfig.class.getResource(Constants.WebSchemaResourcePath_24);
SchemaResolver webEntityResolver = new SchemaResolver(url.toString(),
webDigester);
-if( xmlValidation ) {
+if (validation) {
webDigester.setSchema(url.toString());
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Using SOAP with SSL in Tomcat 4.1.18
Hi, I'm trying to make soap calls over https. I am getting the following error when I try to ... Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Couldn't find trusted certificate This occurs at the point in the code where I invoke the soap call. I found an article at http://www.discursive.com/articles/2002/06/tomcat_ssl.html that I used to get my client working for doing a straight post over https. I had to use the deprecated classes to get the https stuff to work (I have no idea if this is really the correct thing to be doing). Anyway, after I got this to work, I tried using an https url to reference the service for my soap call/client and no matter what I've tried, I get the error message above. Can anyone help with a step-by-step of what to do to use SSL for http and soap using tomcat 4.1.18 and axis? (I can change versions if necessary). Pat Grever Software Development Engineer iIPS Connectivity - Management Applications Lab Phone: 208.396.2522 Fax: 208.396.4796 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using SOAP with SSL in Tomcat 4.1.18
Did you check the obvious solutions such as do you have a certificate? Martin - Original Message - From: GREVER,PAT (HP-Boise,ex1) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 18, 2003 11:09 AM Subject: Using SOAP with SSL in Tomcat 4.1.18 Hi, I'm trying to make soap calls over https. I am getting the following error when I try to ... Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Couldn't find trusted certificate This occurs at the point in the code where I invoke the soap call. I found an article at http://www.discursive.com/articles/2002/06/tomcat_ssl.html that I used to get my client working for doing a straight post over https. I had to use the deprecated classes to get the https stuff to work (I have no idea if this is really the correct thing to be doing). Anyway, after I got this to work, I tried using an https url to reference the service for my soap call/client and no matter what I've tried, I get the error message above. Can anyone help with a step-by-step of what to do to use SSL for http and soap using tomcat 4.1.18 and axis? (I can change versions if necessary). Pat Grever Software Development Engineer iIPS Connectivity - Management Applications Lab Phone: 208.396.2522 Fax: 208.396.4796 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using SOAP with SSL in Tomcat 4.1.18
Well I've followed the steps in several articles about creating server/client keystores, but whether or not I've done it correctly or done everything necessary to connect them up properly for the code to actually use them... I don't know. I've done everything listed in the articles I found. Pat -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 3:12 PM To: Tomcat Developers List Subject: Re: Using SOAP with SSL in Tomcat 4.1.18 Did you check the obvious solutions such as do you have a certificate? Martin - Original Message - From: GREVER,PAT (HP-Boise,ex1) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 18, 2003 11:09 AM Subject: Using SOAP with SSL in Tomcat 4.1.18 Hi, I'm trying to make soap calls over https. I am getting the following error when I try to ... Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Couldn't find trusted certificate This occurs at the point in the code where I invoke the soap call. I found an article at http://www.discursive.com/articles/2002/06/tomcat_ssl.html that I used to get my client working for doing a straight post over https. I had to use the deprecated classes to get the https stuff to work (I have no idea if this is really the correct thing to be doing). Anyway, after I got this to work, I tried using an https url to reference the service for my soap call/client and no matter what I've tried, I get the error message above. Can anyone help with a step-by-step of what to do to use SSL for http and soap using tomcat 4.1.18 and axis? (I can change versions if necessary). Pat Grever Software Development Engineer iIPS Connectivity - Management Applications Lab Phone: 208.396.2522 Fax: 208.396.4796 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using SOAP with SSL in Tomcat 4.1.18
I assume you are referring to http://jakarta.apache.org/tomcat/tomcat-4.0-doc/ssl-howto.html After running keytool utility you will have a certificate keystore.. Did you confirm all these steps on your Tomcat installation? Martin - Original Message - From: GREVER,PAT (HP-Boise,ex1) [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, August 18, 2003 11:14 AM Subject: RE: Using SOAP with SSL in Tomcat 4.1.18 Well I've followed the steps in several articles about creating server/client keystores, but whether or not I've done it correctly or done everything necessary to connect them up properly for the code to actually use them... I don't know. I've done everything listed in the articles I found. Pat -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 3:12 PM To: Tomcat Developers List Subject: Re: Using SOAP with SSL in Tomcat 4.1.18 Did you check the obvious solutions such as do you have a certificate? Martin - Original Message - From: GREVER,PAT (HP-Boise,ex1) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 18, 2003 11:09 AM Subject: Using SOAP with SSL in Tomcat 4.1.18 Hi, I'm trying to make soap calls over https. I am getting the following error when I try to ... Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Couldn't find trusted certificate This occurs at the point in the code where I invoke the soap call. I found an article at http://www.discursive.com/articles/2002/06/tomcat_ssl.html that I used to get my client working for doing a straight post over https. I had to use the deprecated classes to get the https stuff to work (I have no idea if this is really the correct thing to be doing). Anyway, after I got this to work, I tried using an https url to reference the service for my soap call/client and no matter what I've tried, I get the error message above. Can anyone help with a step-by-step of what to do to use SSL for http and soap using tomcat 4.1.18 and axis? (I can change versions if necessary). Pat Grever Software Development Engineer iIPS Connectivity - Management Applications Lab Phone: 208.396.2522 Fax: 208.396.4796 [EMAIL PROTECTED] -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PATCH] jakarta-servletapi-5: Additional TLD clarifications
Slight additional clarification to TLD. jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd - Clarified that body-content is not just a hint - Reformatted description for body-content with smaller margins for spec --- Mark Roth, Java Software JSP 2.0 Co-Specification Lead Sun Microsystems, Inc. Index: jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd === RCS file: /home/cvspublic/jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd,v retrieving revision 1.13 diff -u -r1.13 web-jsptaglibrary_2_0.xsd --- jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd 18 Aug 2003 17:41:20 - 1.13 +++ jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd 18 Aug 2003 18:47:14 - @@ -131,8 +131,11 @@ xsd:annotation xsd:documentation - Provides a hint as to the content of the body of this tag. - Primarily intended for use by page composition tools. +Specifies the type of body that is valid for a tag. + This value is used by the JSP container to validate + that a tag invocation has the correct body syntax and + by page composition tools to assist the page author + in providing a valid tag body. There are currently four values specified: @@ -477,10 +480,11 @@ xsd:documentation Specifies the format for the body of this tag. - The default in JSP 1.2 was JSP but because this is an invalid - setting for simple tag handlers, there is no longer a default - in JSP 2.0. A reasonable default for simple tag handlers is - scriptless if the tag can have a body. + The default in JSP 1.2 was JSP but because this + is an invalid setting for simple tag handlers, there + is no longer a default in JSP 2.0. A reasonable + default for simple tag handlers is scriptless if + the tag can have a body. /xsd:documentation /xsd:annotation Index: jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd === RCS file: /home/cvspublic/jakarta-servletapi-5/jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd,v retrieving revision 1.13 diff -u -r1.13 web-jsptaglibrary_2_0.xsd --- jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd 18 Aug 2003 17:41:20 - 1.13 +++ jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd 18 Aug 2003 18:47:14 - @@ -131,8 +131,11 @@ xsd:annotation xsd:documentation - Provides a hint as to the content of the body of this tag. - Primarily intended for use by page composition tools. +Specifies the type of body that is valid for a tag. + This value is used by the JSP container to validate + that a tag invocation has the correct body syntax and + by page composition tools to assist the page author + in providing a valid tag body. There are currently four values specified: @@ -477,10 +480,11 @@ xsd:documentation Specifies the format for the body of this tag. - The default in JSP 1.2 was JSP but because this is an invalid - setting for simple tag handlers, there is no longer a default - in JSP 2.0. A reasonable default for simple tag handlers is - scriptless if the tag can have a body. + The default in JSP 1.2 was JSP but because this + is an invalid setting for simple tag handlers, there + is no longer a default in JSP 2.0. A reasonable + default for simple tag handlers is scriptless if + the tag can have a body. /xsd:documentation /xsd:annotation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13430] - WWW-Authenticate Header Is Not Sent
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13430. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13430 WWW-Authenticate Header Is Not Sent --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 18:58 --- I finaly got the WWW-Authenticate header by changing org.apache.coyote.tomcat4.CoyoteResponse to keep that header, I'm attaching a patch with my change - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5814] - 401 error code could not be populated by error-page tag
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5814. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5814 401 error code could not be populated by error-page tag --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 18:59 --- Created an attachment (id=7879) Keeping the WWW-Authenticate header in reset(int, String) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13430] - WWW-Authenticate Header Is Not Sent
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13430. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13430 WWW-Authenticate Header Is Not Sent --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 19:09 --- Created an attachment (id=7880) Keeping the WWW-Authenticate header in reset(int, String) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using SOAP with SSL in Tomcat 4.1.18
Yes, the tomcat ssl-howto was one of the sources of information I used on setting up the keystore. I did not see any information about how to confirm these steps with tomcat. How would I go about doing this? Pat -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 3:20 PM To: Tomcat Developers List Subject: Re: Using SOAP with SSL in Tomcat 4.1.18 I assume you are referring to http://jakarta.apache.org/tomcat/tomcat-4.0-doc/ssl-howto.html After running keytool utility you will have a certificate keystore.. Did you confirm all these steps on your Tomcat installation? Martin - Original Message - From: GREVER,PAT (HP-Boise,ex1) [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, August 18, 2003 11:14 AM Subject: RE: Using SOAP with SSL in Tomcat 4.1.18 Well I've followed the steps in several articles about creating server/client keystores, but whether or not I've done it correctly or done everything necessary to connect them up properly for the code to actually use them... I don't know. I've done everything listed in the articles I found. Pat -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 3:12 PM To: Tomcat Developers List Subject: Re: Using SOAP with SSL in Tomcat 4.1.18 Did you check the obvious solutions such as do you have a certificate? Martin - Original Message - From: GREVER,PAT (HP-Boise,ex1) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 18, 2003 11:09 AM Subject: Using SOAP with SSL in Tomcat 4.1.18 Hi, I'm trying to make soap calls over https. I am getting the following error when I try to ... Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Couldn't find trusted certificate This occurs at the point in the code where I invoke the soap call. I found an article at http://www.discursive.com/articles/2002/06/tomcat_ssl.html that I used to get my client working for doing a straight post over https. I had to use the deprecated classes to get the https stuff to work (I have no idea if this is really the correct thing to be doing). Anyway, after I got this to work, I tried using an https url to reference the service for my soap call/client and no matter what I've tried, I get the error message above. Can anyone help with a step-by-step of what to do to use SSL for http and soap using tomcat 4.1.18 and axis? (I can change versions if necessary). Pat Grever Software Development Engineer iIPS Connectivity - Management Applications Lab Phone: 208.396.2522 Fax: 208.396.4796 [EMAIL PROTECTED] -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets DefaultServlet.java
jfarcand2003/08/18 12:41:56
Modified:catalina/src/share/org/apache/catalina/servlets
DefaultServlet.java
Log:
Fix NPE when getMessage returns null.
Revision ChangesPath
1.17 +6 -5
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/DefaultServlet.java
Index: DefaultServlet.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/DefaultServlet.java,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- DefaultServlet.java 29 Jul 2003 14:23:35 - 1.16
+++ DefaultServlet.java 18 Aug 2003 19:41:56 - 1.17
@@ -513,7 +513,8 @@
serveResource(request, response, true);
} catch( IOException ex ) {
// we probably have this check somewhere else too.
-if( ex.getMessage().indexOf(Broken pipe) = 0 ) {
+if( ex.getMessage() != null
+ ex.getMessage().indexOf(Broken pipe) = 0 ) {
// ignore it.
}
throw ex;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-servletapi-5/jsr154/src/share/dtd web-jsptaglibrary_2_0.xsd
kinman 2003/08/18 12:58:19 Modified:jsr152/src/share/dtd web-jsptaglibrary_2_0.xsd jsr154/src/share/dtd web-jsptaglibrary_2_0.xsd Log: - Patch by Mark Roth Slight additional clarification to TLD. jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd - Clarified that body-content is not just a hint - Reformatted description for body-content with smaller margins for spec Revision ChangesPath 1.14 +10 -6 jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd Index: web-jsptaglibrary_2_0.xsd === RCS file: /home/cvs/jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- web-jsptaglibrary_2_0.xsd 18 Aug 2003 17:41:20 - 1.13 +++ web-jsptaglibrary_2_0.xsd 18 Aug 2003 19:58:19 - 1.14 @@ -131,8 +131,11 @@ xsd:annotation xsd:documentation - Provides a hint as to the content of the body of this tag. - Primarily intended for use by page composition tools. +Specifies the type of body that is valid for a tag. + This value is used by the JSP container to validate + that a tag invocation has the correct body syntax and + by page composition tools to assist the page author + in providing a valid tag body. There are currently four values specified: @@ -477,10 +480,11 @@ xsd:documentation Specifies the format for the body of this tag. - The default in JSP 1.2 was JSP but because this is an invalid - setting for simple tag handlers, there is no longer a default - in JSP 2.0. A reasonable default for simple tag handlers is - scriptless if the tag can have a body. + The default in JSP 1.2 was JSP but because this + is an invalid setting for simple tag handlers, there + is no longer a default in JSP 2.0. A reasonable + default for simple tag handlers is scriptless if + the tag can have a body. /xsd:documentation /xsd:annotation 1.14 +10 -6 jakarta-servletapi-5/jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd Index: web-jsptaglibrary_2_0.xsd === RCS file: /home/cvs/jakarta-servletapi-5/jsr154/src/share/dtd/web-jsptaglibrary_2_0.xsd,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- web-jsptaglibrary_2_0.xsd 18 Aug 2003 17:41:20 - 1.13 +++ web-jsptaglibrary_2_0.xsd 18 Aug 2003 19:58:19 - 1.14 @@ -131,8 +131,11 @@ xsd:annotation xsd:documentation - Provides a hint as to the content of the body of this tag. - Primarily intended for use by page composition tools. +Specifies the type of body that is valid for a tag. + This value is used by the JSP container to validate + that a tag invocation has the correct body syntax and + by page composition tools to assist the page author + in providing a valid tag body. There are currently four values specified: @@ -477,10 +480,11 @@ xsd:documentation Specifies the format for the body of this tag. - The default in JSP 1.2 was JSP but because this is an invalid - setting for simple tag handlers, there is no longer a default - in JSP 2.0. A reasonable default for simple tag handlers is - scriptless if the tag can have a body. + The default in JSP 1.2 was JSP but because this + is an invalid setting for simple tag handlers, there + is no longer a default in JSP 2.0. A reasonable + default for simple tag handlers is scriptless if + the tag can have a body. /xsd:documentation /xsd:annotation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22478] - Ant manager deploy causing webapp to initialize twice
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22478. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22478 Ant manager deploy causing webapp to initialize twice --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 20:17 --- I have not studied the bug report. By the looks of it it seems that it is due to a problem with the log4j configurator watchdog thread using a dead classloader. The watchdog code in log4j 1.2.x does not have a notion of a lifecycle. In particular, LogManager.shutdown does not stop the watchdog thread. Atually, I don't think there is a way to stop a watchdog thread which is definetely a serious shortcoming of log4j watchdogs. Please let me know if the above does not clarify the issue. -- Ceki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0.8] Tag soon
Remy, I discovered there is a jasper bug that causes wrong Java line numbers to be mapped when codes for invoking tag handlers are generated in separate methods. This would completely screw up JSP debugging, and causes javac error messages to be lost if it happens in the generated method. I have a fix for this and plan to commit it. The fix is safe in that it does not affect the generated codes, and I promise to do thorough testing before committing. :-) Kin-man Date: Mon, 18 Aug 2003 18:24:53 +0200 From: Remy Maucherat [EMAIL PROTECTED] Subject: [5.0.8] Tag soon To: Tomcat Developers List [EMAIL PROTECTED] As most (all ?) of the issues uncovered in build 5.0.7 have been fixed or addressed in some way, I plan to tag and release 5.0.8 soon (likely wednesday). Please apply any fixes before then (but please no features addition or refactorings), such as the servlet API updates. Thanks :) (hopefully, we'll have a good quality build this time :) ) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22535] New: - JSP XML Syntax problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22535.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22535
JSP XML Syntax problem
Summary: JSP XML Syntax problem
Product: Tomcat 5
Version: 5.0.7
Platform: PC
URL: http://jsplin.sourceforge.net
OS/Version: Windows XP
Status: NEW
Severity: Blocker
Priority: Other
Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I need to use proper XML syntax, as proposed by the minimal JSP 1.2 XML syntax,
with EL I need to use JSP 2.0 in order to get it working.
I am using the following JSP code in a single JSP file:
?xml version=1.0 encoding=ISO-8859-1?
jsp:root xmlns:jsp=http://java.sun.com/JSP/Page;
xmlns:c=http://java.sun.com/jstl/core_rt;
version=1.2
jsp:directive.page language=java
contentType=text/html; charset=ISO-8859-1
pageEncoding=ISO-8859-1
session=true /
jsp:text![CDATA[?xml version=1.0 encoding=ISO-8859-1 ?]]/jsp:text
jsp:text![CDATA[
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;
]]/jsp:text
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en
head
titleTest2/title
/head
body
div
c:forEach var=counter begin=0 end=9 step=1
${counter}
/c:forEach
/div
/body
/html
/jsp:root
This should work correctly according to the specifications, however, the SAX
parser goes wrong with the xmlns:c statement in the jsp:root tag.
The errorcode it produces is:
type Exception report
message
description The server encountered an internal error () that prevented it from
fulfilling this request.
exception
org.apache.jasper.JasperException
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:365)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:259)
org.apache.jasper.compiler.JspDocumentParser.parse(JspDocumentParser.java:203)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:223)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:146)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:132)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:245)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:453)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:555)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:300)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:293)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
root cause
java.lang.NullPointerException
org.apache.jasper.compiler.PageInfo.popPrefixMapping(PageInfo.java:339)
org.apache.jasper.compiler.JspDocumentParser.endPrefixMapping(JspDocumentParser.java:574)
org.apache.xerces.parsers.AbstractSAXParser.endNamespaceMapping(Unknown Source)
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
org.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(Unknown Source)
org.apache.xerces.impl.XMLNamespaceBinder.endElement(Unknown Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
javax.xml.parsers.SAXParser.parse(Unknown Source)
org.apache.jasper.compiler.JspDocumentParser.parse(JspDocumentParser.java:195)
DO NOT REPLY [Bug 22535] - JSP XML Syntax problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22535. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22535 JSP XML Syntax problem [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 22:36 --- This is a duplicate and has been fixed. *** This bug has been marked as a duplicate of 22439 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22439] - NPE compiling JSP Document
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22439. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22439 NPE compiling JSP Document [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-08-18 22:36 --- *** Bug 22535 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Versioning in WebDAV and Slide
Hi ! You will save me a lot of time answering two questions: 1) Is Versioning part of the current Slide implementation ? 2) If not, is there library that can help me implementing that (with some instructions of course). To be clear: I need to copy, on a daily basis, files from workstations to the web folder (on the server). I need to Archive and Version them so to retrieve earlier version in a CVS like fashion. I read that WebDAV specifu that, so I am just wandering if Slide implemented that already and how I can use that because I was not able to find help, guidelines or any instructions whether how to use Versioning with Slide or how to implement that functionality. I need a client (with UI) that will have capabilities to do similar tasks like CVS but on WebDAV platform. Thanks a lot, Darko Stefanovic Senior Software Engineer Lexicon Genetics Bioinformatics Department 8800 Technology Forest Place The Woodlands, TX 77381-1160 Phone: (281) 863-3195 Fax: (281) 863-8004 E-mail: [EMAIL PROTECTED] *** The contents of this communication are intended only for the addressee and may contain confidential and/or privileged material. If you are not the intended recipient, please do not read, copy, use or disclose this communication and notify the sender. Opinions, conclusions and other information in this communication that do not relate to the official business of my company shall be understood as neither given nor endorsed by it. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Versioning in WebDAV and Slide
Hi ! You will save me a lot of time answering two questions: 1) Is Versioning part of the current Slide implementation ? 2) If not, is there library that can help me implementing that (with some instructions of course). To be clear: I need to copy, on a daily basis, files from workstations to the web folder (on the server). I need to Archive and Version them so to retrieve earlier version in a CVS like fashion. I read that WebDAV specifu that, so I am just wandering if Slide implemented that already and how I can use that because I was not able to find help, guidelines or any instructions whether how to use Versioning with Slide or how to implement that functionality. I need a client (with UI) that will have capabilities to do similar tasks like CVS but on WebDAV platform. Thanks a lot, Darko Stefanovic Senior Software Engineer Lexicon Genetics Bioinformatics Department 8800 Technology Forest Place The Woodlands, TX 77381-1160 Phone: (281) 863-3195 Fax: (281) 863-8004 E-mail: [EMAIL PROTECTED] *** The contents of this communication are intended only for the addressee and may contain confidential and/or privileged material. If you are not the intended recipient, please do not read, copy, use or disclose this communication and notify the sender. Opinions, conclusions and other information in this communication that do not relate to the official business of my company shall be understood as neither given nor endorsed by it. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/admin build.xml
amyroh 2003/08/18 16:53:49
Modified:webapps/admin build.xml
Log:
Fix typo - bugzilla 19469.
Revision ChangesPath
1.8 +1 -1 jakarta-tomcat-catalina/webapps/admin/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/admin/build.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- build.xml 11 Feb 2003 03:34:43 - 1.7
+++ build.xml 18 Aug 2003 23:53:49 - 1.8
@@ -72,7 +72,7 @@
classpath=${struts.jar} /
available property=beanutils.present
classname=org.apache.commons.beanutils.PropertyUtils
- classpath=${common-beanutils.jar} /
+ classpath=${commons-beanutils.jar} /
available property=regexp.present
classname=org.apache.regexp.RE
classpath=${regexp.jar} /
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/admin build.xml
amyroh 2003/08/18 16:54:26
Modified:webapps/admin build.xml
Log:
Backport patch. Fix typo - bugzilla 19469.
Revision ChangesPath
1.6 +1 -1 jakarta-tomcat-4.0/webapps/admin/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/admin/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 11 Feb 2003 02:27:15 - 1.5
+++ build.xml 18 Aug 2003 23:54:26 - 1.6
@@ -67,7 +67,7 @@
classpath=${struts.jar} /
available property=beanutils.present
classname=org.apache.commons.beanutils.PropertyUtils
- classpath=${common-beanutils.jar} /
+ classpath=${commons-beanutils.jar} /
!-- JAR files availability flags --
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19469] - Typo in admin webapp's build.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19469. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19469 Typo in admin webapp's build.xml [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/conf web.xml
yoavs 2003/08/18 17:17:03 Modified:catalina/src/conf web.xml Log: Removed logVerbosityLevel doc and init-param from JSP Servlet, as they're no longer used. Closing bug 22494. BTW, should we change the DTD of web.xml to 2.4? Revision ChangesPath 1.24 +1 -11 jakarta-tomcat-catalina/catalina/src/conf/web.xml Index: web.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/web.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- web.xml 6 Aug 2003 20:17:59 - 1.23 +++ web.xml 19 Aug 2003 00:17:03 - 1.24 @@ -114,7 +114,7 @@ !-- if a JSP page needs to be recompiled. [300]-- !-- -- !-- compilerWhich compiler Ant should use to compile JSP -- - !-- pages. See the Ant documenation for more -- + !-- pages. See the Ant documentation for more -- !-- information. [javac] -- !-- -- !-- classdebuginfo Should the class file be compiled with -- @@ -144,12 +144,6 @@ !-- keepgenerated Should we keep the generated Java source code -- !-- for each page instead of deleting it? [true] -- !-- -- - !-- logVerbosityLevel The level of detailed messages to be produced -- - !-- by this servlet. Increasing levels cause the -- - !-- generation of more messages. Valid values are -- - !-- FATAL, ERROR, WARNING, INFORMATION, and DEBUG. -- - !-- [WARNING] -- - !-- -- !-- mappedfile Should we generate static content with one -- !-- print statement per input line, to ease-- !-- debugging? [false]-- @@ -182,10 +176,6 @@ servlet servlet-namejsp/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class -init-param -param-namelogVerbosityLevel/param-name -param-valueWARNING/param-value -/init-param init-param param-namefork/param-name param-valuefalse/param-value - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs jasper-howto.xml
yoavs 2003/08/18 17:20:02 Modified:webapps/docs jasper-howto.xml Log: Removed logVerbosityLevel. Revision ChangesPath 1.9 +0 -5 jakarta-tomcat-catalina/webapps/docs/jasper-howto.xml Index: jasper-howto.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/jasper-howto.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- jasper-howto.xml 12 Mar 2003 09:49:10 - 1.8 +++ jasper-howto.xml 19 Aug 2003 00:20:02 - 1.9 @@ -112,11 +112,6 @@ pages in external data files, to reduce the size of the generated servlets? codetrue/code or codefalse/code, default codefalse/code./li -listronglogVerbosityLevel/strong - The level of detailed messages to be -produced by this servlet. Increasing levels cause the generation of more -messages. Valid values are codeFATAL, ERROR, WARNING, INFORMATION,/code -and codeDEBUG/code. Default codeWARNING/code./li - listrongmappedfile/strong - Should we generate static content with one print statement per input line, to ease debugging? codetrue/code or codefalse/code, default codefalse/code./li - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22494] - logVerbosityLevel not used anymore
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22494. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22494 logVerbosityLevel not used anymore [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-08-19 00:23 --- logVerbosityLevel indeed seems unused -- patch done. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java Node.java
kinman 2003/08/18 17:36:35
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Node.java
Log:
- Adjust Java lines mappings for codes that are generated in buffers.
The diff is more than was actually changed, due to a change of a class
name.
Revision ChangesPath
1.197 +80 -32
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java
Index: Generator.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
retrieving revision 1.196
retrieving revision 1.197
diff -u -r1.196 -r1.197
--- Generator.java17 Aug 2003 21:54:36 - 1.196
+++ Generator.java19 Aug 2003 00:36:35 - 1.197
@@ -91,7 +91,7 @@
private static final Class[] OBJECT_CLASS = { Object.class};
private ServletWriter out;
-private MethodsBuffer methodsBuffer;
+private ArrayList methodsBuffered;
private FragmentHelperClass fragmentHelperClass;
private ErrorDispatcher err;
private BeanRepository beanInfo;
@@ -695,7 +695,7 @@
private boolean isFragment;
private boolean isTagFile;
private ServletWriter out;
- private MethodsBuffer methodsBuffer;
+ private ArrayList methodsBuffered;
private FragmentHelperClass fragmentHelperClass;
private int methodNesting;
private TagInfo tagInfo;
@@ -706,13 +706,13 @@
*/
public GenerateVisitor(boolean isTagFile,
ServletWriter out,
-MethodsBuffer methodsBuffer,
+ArrayList methodsBuffered,
FragmentHelperClass fragmentHelperClass,
ClassLoader loader,
TagInfo tagInfo) {
this.isTagFile = isTagFile;
this.out = out;
- this.methodsBuffer = methodsBuffer;
+ this.methodsBuffered = methodsBuffered;
this.fragmentHelperClass = fragmentHelperClass;
this.loader = loader;
this.tagInfo = tagInfo;
@@ -1485,7 +1485,6 @@
// If the tag contains no scripting element, generate its codes
// to a method.
ServletWriter outSave = null;
- MethodsBuffer methodsBufferSave = null;
Node.ChildInfo ci = n.getChildInfo();
if (ci.isScriptless() !ci.hasScriptingVars()) {
// The tag handler and its body code can reside in a separate
@@ -1515,9 +1514,10 @@
// Set up new buffer for the method
outSave = out;
- out = methodsBuffer.getOut();
- methodsBufferSave = methodsBuffer;
- methodsBuffer = new MethodsBuffer();
+ GenBuffer genBuffer = new GenBuffer(
+ n.implementsSimpleTag()? null:n.getBody());
+ methodsBuffered.add(genBuffer);
+ out = genBuffer.getOut();
methodNesting++;
// Generate code for method declaration
@@ -1590,12 +1590,7 @@
methodNesting--;
- // Append any methods that got generated in the body to the
- // current buffer
- out.print(methodsBuffer.toString());
-
- // restore previous buffer
- methodsBuffer = methodsBufferSave;
+ // restore previous writer
out = outSave;
}
}
@@ -2722,7 +2717,7 @@
fragmentHelperClass.openFragment(n, tagHandlerVar,
methodNesting);
ServletWriter outSave = out;
- out = fragment.getMethodsBuffer().getOut();
+ out = fragment.getGenBuffer().getOut();
String tmpParent = parent;
parent = tagHandlerVar;
boolean tmpIsFragment = isFragment;
@@ -2851,12 +2846,17 @@
* Common part of postamble, shared by both servlets and tag files.
*/
private void genCommonPostamble() {
- // Append any methods that were generated
- out.printMultiLn(methodsBuffer.toString());
+ // Append any methods that were generated in the buffer.
+ for (int i = 0; i methodsBuffered.size(); i++) {
+ GenBuffer methodBuffer = (GenBuffer) methodsBuffered.get(i);
+ methodBuffer.adjustJavaLines(out.getJavaLine()-1);
+ out.printMultiLn(methodBuffer.toString());
+ }
// Append the helper class
if( fragmentHelperClass.isUsed() ) {
fragmentHelperClass.generatePostamble();
+fragmentHelperClass.adjustJavaLines(out.getJavaLine()-1);
out.printMultiLn(fragmentHelperClass.toString());
}
@@
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans mbeans-descriptors.xml
amyroh 2003/08/18 17:43:09 Modified:catalina/src/share/org/apache/catalina/mbeans mbeans-descriptors.xml Log: Add missing className property for mbean description. It seems like it was accidently removed by previous commit. Should fix bugzilla 22328. Revision ChangesPath 1.77 +8 -6 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/mbeans-descriptors.xml Index: mbeans-descriptors.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/mbeans-descriptors.xml,v retrieving revision 1.76 retrieving revision 1.77 diff -u -r1.76 -r1.77 --- mbeans-descriptors.xml8 Jul 2003 23:12:51 - 1.76 +++ mbeans-descriptors.xml19 Aug 2003 00:43:09 - 1.77 @@ -10,11 +10,12 @@ -- mbeans-descriptors - mbean name=AccessLogValve - description=Valve that generates a web server access log - domain=Catalina - group=Valve - type=org.apache.catalina.valves.AccessLogValve + mbean name=AccessLogValve + className=org.apache.catalina.mbeans.ClassNameMBean + description=Valve that generates a web server access log + domain=Catalina +group=Valve + type=org.apache.catalina.valves.AccessLogValve attribute name=className description=Fully qualified class name of the managed object @@ -499,6 +500,7 @@ /mbean mbean name=ExtendedAccessLogValve + className=org.apache.catalina.mbeans.ClassNameMBean description=Valve that generates a web server access log domain=Catalina group=Valve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session PersistentManagerBase.java StandardManager.java StandardSession.java StoreBase.java
luehe 2003/08/18 17:49:58
Modified:catalina/src/share/org/apache/catalina/session
PersistentManagerBase.java StandardManager.java
StandardSession.java StoreBase.java
Log:
Fixed Bugtraq 4839736 (HttpSession.setMaxInactiveInterval() doesn't
behave as expected)
Patch provided by [EMAIL PROTECTED]
The following test case used to fail intermittently, due to a race
condition between the 2nd session access and the background thread
that invalidates expired sessions:
HttpSession session1 = req.getSession();
session1.setMaxInactiveInterval(5);
try {
Thread.sleep(10 * 1000);
} catch (InterruptedException e) { e.printStackTrace(); }
HttpSession session2 = req.getSession(false);
if (session2 == null) {
// SUCCESS
} else {
// FAIL!!
}
Revision ChangesPath
1.9 +11 -36
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java
Index: PersistentManagerBase.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- PersistentManagerBase.java8 Jul 2003 06:28:02 - 1.8
+++ PersistentManagerBase.java19 Aug 2003 00:49:58 - 1.9
@@ -835,8 +835,7 @@
if (session == null)
return (null);
-if (!session.isValid()
-|| isSessionStale(session, System.currentTimeMillis())) {
+if (!session.isValid()) {
log.error(session swapped in is invalid or expired);
session.expire();
removeSession(id);
@@ -867,10 +866,9 @@
*/
protected void swapOut(Session session) throws IOException {
-if (store == null ||
-!session.isValid() ||
-isSessionStale(session, System.currentTimeMillis()))
+if (store == null || !session.isValid()) {
return;
+}
((StandardSession)session).passivate();
writeSession(session);
@@ -887,10 +885,9 @@
*/
protected void writeSession(Session session) throws IOException {
-if (store == null ||
-!session.isValid() ||
-isSessionStale(session, System.currentTimeMillis()))
+if (store == null || !session.isValid()) {
return;
+}
try {
if (System.getSecurityManager() != null){
@@ -1073,27 +1070,6 @@
/**
- * Indicate whether the session has been idle for longer
- * than its expiration date as of the supplied time.
- *
- * FIXME: Probably belongs in the Session class.
- */
-protected boolean isSessionStale(Session session, long timeNow) {
-
-int maxInactiveInterval = session.getMaxInactiveInterval();
-if (maxInactiveInterval = 0) {
-int timeIdle = // Truncate, do not round up
-(int) ((timeNow - session.getLastAccessedTime()) / 1000L);
-if (timeIdle = maxInactiveInterval)
-return true;
-}
-
-return false;
-
-}
-
-
-/**
* Invalidate all sessions that have expired.
*/
protected void processExpires() {
@@ -1106,10 +1082,9 @@
for (int i = 0; i sessions.length; i++) {
StandardSession session = (StandardSession) sessions[i];
-if (!session.isValid())
-continue;
-if (isSessionStale(session, timeNow))
+if (!session.isValid()) {
session.expire();
+ }
}
}
1.11 +5 -12
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/StandardManager.java
Index: StandardManager.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/StandardManager.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- StandardManager.java 8 Jul 2003 06:28:02 - 1.10
+++ StandardManager.java 19 Aug 2003 00:49:58 - 1.11
@@ -813,14 +813,7 @@
for (int i = 0; i sessions.length; i++) {
StandardSession session = (StandardSession) sessions[i];
-if (!session.isValid())
-continue;
-int maxInactiveInterval = session.getMaxInactiveInterval();
-if (maxInactiveInterval 0)
-continue;
-int timeIdle = // Truncate, do not round up
-(int) ((timeNow - session.getLastAccessedTime()) / 1000L);
DO NOT REPLY [Bug 22328] - javax.management.ReflectionException: Cannot find method getClassName with this signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22328. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22328 javax.management.ReflectionException: Cannot find method getClassName with this signature [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21078] - modeler.present and beanutils.present surely fail in webapps/admin/build.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21078. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21078 modeler.present and beanutils.present surely fail in webapps/admin/build.xml [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21643] - Cannot create Valve with Mozilla 1.4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21643. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21643 Cannot create Valve with Mozilla 1.4 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-08-19 01:47 --- *** This bug has been marked as a duplicate of 18384 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18384] - creation of jdbc realms is not possible with mozilla 1.3
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18384. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18384 creation of jdbc realms is not possible with mozilla 1.3 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-08-19 01:47 --- *** Bug 21643 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16001] - Tag.release() not invoked
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16001. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16001 Tag.release() not invoked [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-08-19 02:16 --- According to the JSP 1.1 Errata published on 5/31/00 (http://java.sun.com/products/jsp/errata_1_1_a_042800.html see under Issue 14) the behavior exhibited by Jasper (regarding tag pooling) is not in accordance with the specification for JSP 1.1. The errata recognizes the shortcoming of the original spec, which did not provide any mechanism for clearing the tag handler’s state between uses, and it states that tag instances cannot be reused if they don't correspond to actions with the same attributes, unless release() is called between uses. So, the same instance of the handler can be used for x:foo att1=one att2=two/ x:foo att1=HELLO att2=BYE/ but for x:foo att1=one att2=two/ x:foo att1=HELLO/ you either have to use different instances, or you have to call release() before second use. I would assume the same applies for JSP 1.2, unless the specification explicitly states otherwise. The errata is there for everyone to see right along side of the original final specification http://java.sun.com/products/jsp/download.html#specs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0.8] Tag soon
(hopefully, we'll have a good quality build this time :) ) To that end, could someone add xml/xml.jsp from the jsp-examples webapp (or something like it) to tester? There isn't very much XML coverage in tester, and this particular jsp would have flagged bugs 22277 and 21366 before they made it into a release, so it seems like a good addition. I would help with this, but I don't think I'll have time before Remy starts tagging. If this is still pending post 5.0.8 (and no one's come up with a good reason why it shouldn't be done), I'll work on it. Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16001] - Tag.release() not invoked
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16001. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16001 Tag.release() not invoked [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-08-19 04:42 --- It's true that the 1.1 errata was included in the 1.2 Spec. However, it's not relevent to this report. Jasper will use seperate instances of the foo tag handler, which you've already agreed is valid. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: urgent
hi friends, this is the problem i am facing C:\tomcat\work\Standalone\localhost\callreg\passcall_jsp.java:58: package callreg does not exist callreg.URLBean db = null; An error occurred at line: 2 in the jsp file: /passcall.jsp Generated servlet error: C:\tomcat\work\Standalone\localhost\callreg\passcall_jsp.java:60: package callreg does not exist db = (callreg.URLBean) pageContext.getAttribute(db, PageContext.APPLICATION_SCOPE); An error occurred at line: 2 in the jsp file: /passcall.jsp Generated servlet error: C:\tomcat\work\Standalone\localhost\callreg\passcall_jsp.java:63: package callreg does not exist db = (callreg.URLBean) java.beans.Beans.instantiate(this.getClass().getClassLoader(), callreg.URLBean); and my dir structure is: c:/tomcat/webapps/callreg/web-inf/calsses/callreg/URLBean.class c:/tomcat/webapps/callreg/web-inf/lib/tds.jar and i am includeing jsp as jsp:useBean id=db scope=application class=callreg.URLBean / and connecting as Class.forName(db.getDriver()); Connection con=DriverManager.getConnection(db.getUrl(),db.getUser(),db.getPassword()); pls help me out its urgent thanx in advance Shaman ___ Meet your old school or college friends from 1 Million + database... Click here to reunite www.batchmates.com/rediff.asp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
