DO NOT REPLY [Bug 45153] New: Javabean not accessible to jsp until placed in a package.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45153
Summary: Javabean not accessible to jsp until placed in a
package.
Product: Tomcat 6
Version: unspecified
Platform: Macintosh
OS/Version: Mac OS X 10.4
Status: NEW
Severity: normal
Priority: P2
Component: Servlet & JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I am using version 6.0.16 of tomcat and the problem may be version dependent.
The problem I experienced is, if a bean is not contained within a package, the
bean is not accessible from a JSP.
Without a package specified in the bean class and with the bean class file in
the classes folder, the following exceptions occurred. The condition was not
resolved until a "package foo;" statement was added to the bean class and the
class file was placed in the "classes/foo" folder.
This is the error when the useBean standard action was used:
SEVERE: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /testJSTL3.jsp(12,0) The value for the
useBean class attribute TestBean1 is invalid.
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
...
This is the error when a scriptlet was used:
SEVERE: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: 7 in the jsp file: /testJSTL3.jsp
TestBean1 cannot be resolved to a type
4: <%
5: String [] movieList = {"Amelie", "Returrn of the King", "Mean Girls"};
6: request.setAttribute("movieList", movieList);
7: TestBean1 myBean = new TestBean1();
This is the error when the page directive and import attribute were used in the
jsp.
SEVERE: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: 6 in the generated java file
The import TestBean1 cannot be resolved
The following is a failing version of the code:
TestBean1.java:
public class TestBean1 {
private String prop1;
private int prop2;
public TestBean1() {
}
public String getProp1() {
return prop1;
}
public void setProp1(String newProp) {
prop1 = newProp;
}
public int getProp2() {
return prop2;
}
public void setProp2(int newProp) {
prop2 = newProp;
}
}
testBean.jsp
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %>
<%@ page import="TestBean1" %>
<%
String [] movieList = {"Amelie", "Returrn of the King", "Mean Girls"};
request.setAttribute("movieList", movieList);
TestBean1 myBean2 = new TestBean1();
myBean2.setProp1("This is a String a myBean property");
myBean2.setProp2(87654321);
request.setAttribute("myBean2", myBean2);
%>
<%-- forEach looks through scope maps for attribute specified in items
attribute --%>
Movie ${movieNum.count}: ${s}
Prop1: ${myBean.prop1}
Prop2: ${myBean.prop2}
Last Row
The following is a working version of the code:
TestBean1.java:
package foo;
public class TestBean1 {
private String prop1;
private int prop2;
public TestBean1() {
}
public String getProp1() {
return prop1;
}
public void setProp1(String newProp) {
prop1 = newProp;
}
public int getProp2() {
return prop2;
}
public void setProp2(int newProp) {
prop2 = newProp;
}
}
testBean.jsp:
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %>
<%@ page import="foo.TestBean1" %>
<%
String [] movieList = {"Amelie", "Returrn of the King", "Mean Girls"};
request.setAttribute("movieList", movieList);
TestBean1 myBean2 = new foo.TestBean1();
myBean2.setProp1("This is a String a myBean property");
myBean2.setProp2(87654321);
request.setAttribute("myBean2", myBean2);
%>
<%-- forEach looks through scope maps for attribute specified in items
attribute --%>
Movie ${movieNum.count}: ${s}
Prop1: ${myBean.prop1}
Prop2: ${myBean.prop2}
Last Row
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45154] New: Support sendfile with NIO and SSL
https://issues.apache.org/bugzilla/show_bug.cgi?id=45154 Summary: Support sendfile with NIO and SSL Product: Tomcat 6 Version: 6.0.16 Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Created an attachment (id=22092) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22092) Patch for Tomcat 6.0.16 We upgraded to Tomcat 6.0 to take advantage of NIO. We have a couple servlets which use SSL for secure download of very large files and needed it to scale. Disappointed that the sendfile functionality didn't work with NIO when using SSL, I dug in until I got something to work. I'm attaching a patch. The part that I'm least comfortable was the change to SecureNioChannel because I didn't know why the check was there to begin with. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45155] New: Authentication with windows XP Mini-redirector
https://issues.apache.org/bugzilla/show_bug.cgi?id=45155 Summary: Authentication with windows XP Mini-redirector Product: Tomcat 6 Version: unspecified Platform: All OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hello, There is a problem in Tomcat (all versions as far as i have tested, up to the 4.X versions) regarding the realm-based authentication on tomcat's side, with Windows XP clients. After several weeks trying to find how to solve this problem, here it is on the bug list.. Basically the problem is that the authentication provided by Tomcat is not working with the Windows XP clients using the windows xp 'Webclient' service as known as Webdav Mini-redirector. I won't explain in details how windows XP works with this Webclient service but here are the two things that are important: 1) In your 'Network Places' folder, try to add a folder with an HTTP url pointing to your favorite webdav servlet protected with BASIC authentication. Configure your tomcat server to provide this servlet on something like : http://host/davservlet It won't work at all because windows tries to authenticate with NTLM. The thing is that windows can't recognize the realm you are using and its type (BASIC). Windows thinks it's NTLM and provides your username like DOMAIN\username (which, obviously, is not your login at all...). 2) Configure your tomcat to provide SSL on port 443. Do the same as before : add your network folder httpS://host/davservlet : it works because another DLL file (the good one ! from microsoft office) is used to connect to it (because HTTPS is not supported by the real mini-redirector). 3) Configure your tomcat to provide HTTP (not HTTPS) acccess on port XXX other than 80. Do the same as before : it works again ! Because this is the same good DLL which is used. You'll say : change the port 80 to something else ! Or juste provide HTTPS which is even better ! I reply : yep, but what if i want to map my webdav access to a network drive ? Windows can handle that but not if your port is other than 80, and not if it's HTTPS !! So no solution so far ; This is a well known bug of Tomcat since many versions. Please don't put this bug report INVALID or DECLINED as it affects many people.. I alreay saw this bug being INVALIDATED by a developper around here juste because it worked properly for him. Please try these things about the ports and the HTTPS things and you'll see by yourself that there is a problem. And as you can't change the windows DLL, perhaps on Tomcat's side, something can be done ? Thank you ! Henri -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 45156] New: Symbol not found: _open$UNIX2003
https://issues.apache.org/bugzilla/show_bug.cgi?id=45156 Summary: Symbol not found: _open$UNIX2003 Product: Tomcat 6 Version: 6.0.10 Platform: Macintosh OS/Version: Mac OS X 10.4 Status: NEW Severity: normal Priority: P2 Component: Connectors AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When loading mod_jk.so (.../tomcat-connectors/jk/binaries/macosx/jk-1.2.25/ppc/mod_jk-1.2.25-httpd-2.2.6.so) starting Apache fails with dyld: lazy symbol binding failed: Symbol not found: _open$UNIX2003 Referenced from: /usr/local/OPIXweb/apache/modules/mod_jk.so Expected in: /usr/lib/libSystem.B.dylib in the error_log. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
