Min Huang

I thought so. I ended up writing a task that read in id's and image file paths from a properties file, then executed a sql update on all of them. Here's the class:

import org.apache.commons.io.*; import org.apache.commons.logging.*; import org.apache.tools.ant.*; import org.apache.tools.ant.taskdefs.*; import javax.sql.rowset.serial.*; import java.io.*; import java.sql.*; import java.util.*; public class BlobLoaderTask extends JDBCTask { private static Log log = LogFactory.getLog(BlobLoaderTask.class); private String propsfile; private String basedir; private String sql; public void execute() throws BuildException { if (propsfile == null) throw new BuildException("propsfile is required"); if (sql == null) throw new BuildException("sql is required"); if (basedir == null) basedir = ""; Properties props = load(); Connection connection = getConnection(); PreparedStatement statement = null; try { connection.setAutoCommit(true); } catch (SQLException e) { throw new BuildException(e); } for (Object key : props.keySet()) { try { String id = (String) key; String path = props.getProperty(id); InputStream is = new FileInputStream(basedir + path); byte[] bytes = IOUtils.toByteArray(is); is.close(); Blob blob = new SerialBlob(bytes); statement = connection.prepareStatement(sql); statement.setBlob(1, blob); statement.setInt(2, Integer.parseInt(id)); int result = statement.executeUpdate(); log.info("Executed sql with [sql=" + sql + ", param1=" + id + ", param2=" + basedir + path + ", length=" + blob.length() + ", result=" + result + "]"); } catch (SQLException e) { throw new BuildException(e); } catch (IOException e) { throw new BuildException(e); } } } protected Properties load() { Properties props = new Properties(); try { props.load(new FileInputStream(propsfile)); return props; } catch (FileNotFoundException e) { throw new BuildException(e); } catch (IOException e) { throw new BuildException(e); } } public void setPropsfile(String propsfile) { this.propsfile = propsfile; } public void setSql(String sql) { this.sql = sql; } public void setBasedir(String basedir) { this.basedir = basedir; } }

Target def looks like this:

<taskdef name="bload" classname="BlobLoaderTask"> <classpath refid="compile.classpath"/> <classpath path="${build.test-classes.dir}"/> </taskdef> <bload propsfile="${basedir}/sql/images.properties" basedir="${basedir}/sql/binary/images" sql="update `uploaded_files` set content = ? where id = ?" url="${db.url}" classpathref="runtime.classpath" driver="${db.driver}" userid="${db.username}" password="${db.password}"/> </target>

Unfortunately, mysql's load_file only works on the host computer (ie the computer the mysql instance is running on), so this didnt work when I tried running ant load on another database:

package com.taylor.test; import java.io.PrintStream; import java.sql.SQLException; import org.apache.tools.ant.taskdefs.SQLExec; public class RelativeLoaderSQLTask extends SQLExec { private String basedir; @Override protected void execSQL(String sql, PrintStream stream) throws SQLException { sql = sql.replaceAll("load_file\\('", "load_file('" + basedir); super.execSQL(sql, stream); } public void setBasedir(String basedir) { this.basedir = basedir; } }

[ April 18, 2007: Message edited by: Min Huang ]
[ April 18, 2007: Message edited by: Min Huang ]

I am trying to load a bunch of images as seed data into MySQL as part of the build process. Currently, I have an image.sql file that contains binary data, which the mysql client tools will happily import into MySQL:

mysql my_database < image.sql

Unfortunately, the ant sql task fails to parse this file correctly because of the binary data and fails. I've tried combinations of keepformat, encoding, and escapeprocessing, but I still can't execute that sql file via ant.

I have a shell script that loads the data, but I'd really like to be able to use ant and not require mysql client tools or cygwin/unix to be able to load data into the database.

Here are my options:
a) Find out a way to make the ant sql task work with binary data
b) Find out a way to load binary data using mysql's load_file with ant. The load_file function requires an absolute path, so I would need some way to only specify relative paths in the sql file and have ant do the rest. I dont think this is even possible.
c) The least attractive option is to have a <exec> task execute the mysql binary with the correct args. But I dont think there's a way to do unix file redirection; it wouldn't work on Windows.

Any suggestions?

If you attach a debugger to your webapp while its running, break somewhere, and make a code change (works in Eclipse and IDEA), that change will be reflected instantly and you won't have to reload the context.

If you put

<script> history.forward(); </script>

at the top of your page, it will attempt to go forward a page in your history. If you go to another page, and then try to click back and go to this page, you will be bounced forward.

As an aside, if you do this, people will hate you. True story.

You probably want to use a servlet Filter to make the user go to the right page after authentication. Or use Acegi and let it do the hard work for you.

I figured it out. You have to put <% request.setCharacterEncoding("UTF-8"); %> at the top of the JSP. The character encoding has to be done before any params are read, or else it wont work.

Having a scriplet in your JSP is no good, so you can make a servlet filter to do just that. Make sure it's the first filter in the chain or it might not work. Order matters.

You can use CharacterEncodingFilter in Spring, or write your own:

<filter> <filter-name>CharacterEncodingFilter</filter-name> <filter-class>org.springframework.web.filter.CharacterEncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> </init-param> </filter> <filter-mapping> <filter-name>CharacterEncodingFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>

You can replace the page directives with this in your web.xml:
<jsp-config> <jsp-property-group> <page-encoding>UTF-8</page-encoding> <url-pattern>/*</url-pattern> </jsp-property-group> </jsp-config>

Setting the charset to gb2312 doesn't work; I don't see the character I want. I've crafted a JSP that illustrates my problem:

<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> <%@ taglib uri="http://jakarta.apache.org/taglibs/string-1.1" prefix="str" %> <%@page pageEncoding="UTF-8"%> <%@page contentType="text/html;charset=UTF-8"%> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"> <title>Test page</title> <style> p#utf8 { border: 1px solid green; width: 300px; } div#result { border: 1px solid red; width: 300px; } </style> </head> <body> <c:if test="${!empty param.text}"> <div id="result"> <b>Form submission result:</b> <c:out value="${param.text}"/> </div> </c:if> <p id="utf8"> UTF-8 chinese text: 我 </p> <p> Form submission with a GET:<br/> <form action="testI18N.jsp" method="GET" enctype="multipart/form-data" accept-charset="UTF-8"> <input type="text" name="text" value="我"/> <input type="submit" value="go"/> </form> </p> <p> Form submission with a POST (multipart/form-data):<br/> <form action="testI18N.jsp" method="POST" enctype="multipart/form-data" accept-charset="UTF-8"> <input type="text" name="text" value="我"/> <input type="submit" value="go"/> </form> </p> <p> Form submission with a POST (application/x-www-form-urlencoded):<br/> <form action="testI18N.jsp" method="POST" enctype="application/x-www-form-urlencoded" accept-charset="UTF-8"> <input type="text" name="text" value="我"/> <input type="submit" value="go"/> </form> </p> <p> Form submission with a POST (text/plain):<br/> <form action="testI18N.jsp" method="POST" enctype="text/plain" accept-charset="UTF-8"> <input type="text" name="text" value="我"/> <input type="submit" value="go"/> </form> </p> </body> </html>

Specifically, I have:
1) <%@page pageEncoding="UTF-8"%> set.
2) <%@page contentType="text/html;charset=UTF-8"%> set after the first directive.
3) <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/> in the head.
4) enctype="multipart/form-data" attribute in the form.
5) accept-charset="UTF-8" attribute in the form.

The results I see are:
For a GET: �ˆ‘ is the result.
For a POST with enctype="application/x-www-form-urlencoded": �ˆ‘ is the result.
For any other POST encoding: No entry in request parameter map.

Btw, yes I am Chinese.

Yes, I realize that. I was just wondering if there is some easy way to do it. I did stumble upon ct-eclipse, but there is are no files available for downloading. I was hoping if somebody knew of an alternative.

I have a weird problem I can't quite figure out. I am also not even sure if I'm posting in the correct forum, so please move my post if necessary.

Basically I am trying to get an HTML post to work with a chinese character.

I have a form that is multipart/form-data encoded:

<form action="someurl" method="POST" enctype="multipart/form-data"> ... </form>

The form has a single input in which I am trying to send the chinese character 我. For some reason, I am not getting the right character back when I break and inspect my command object in Eclipse.

I've tried a few things:

a) I don't explicitly set a page directive. When I submit, I get this back as a string: 我

This strikes me as incorrect because it should be a unicode character along the lines of '\uxxxx'

b) I set the content type via a page directive:

<%@ page contentType="text/html; charset=UTF-8" %>

This gets me a little bit closer; when I break, I see three characters: ���

I understand that in the encoding, some characters can have variable length (1-4), so I'm not surprised if 我 requires such an encoding. However, I should expect one character instead of three.

Does anybody know how to resolve this issue?

Sorry, I didn't specify that this is JUnit3 specific. I strongly suspect that there is nothing I can do in this situation..

Is there a way to do this? I understand that having this need reveals a deeper problem in my unit tests themselves (ie they are not actually unit tests, but functional or they are just plain bad, bad I tell you!), but please humor me

Also, if you don't want to nefariously subvert the <c:url/> tag, you can use jakarta's string taglibs that has a <str:encodeUrl/> tag.

--
edit: messed up the url
[ March 29, 2007: Message edited by: Min Huang ]

If anybody was following this, (and Mr. Bibeault, you're not going to like this), you can do this:

1) Write your own CustomUrlTag, possibly extending UrlTag.

2) Copy the c.tld from standard.jar into /WEB-INF/tld and rename it to something like custom.tld.

3) Modify the url tag in c.tld and change the class name to your custom url tag.

4) Put the following in your web.xml:
<jsp-config> <taglib> <taglib-uri>http://java.sun.com/jsp/jstl/core</taglib-uri> <taglib-location>/WEB-INF/tld/custom.tld</taglib-location> </taglib> </jsp-config>

Yea. I agree with your thoughts on a), overriding standard behavior is a whole other can of worms altogether, and I think I'll just go with b). Thanks for your input.

Why do would an EL function would be better? I've considered these options:

a) Replace <c:url/>
b) Write <myc:url/>
c) Write an EL function and do <c:url value="${myc:encode(url)}"/>
d) Encode in a servlet and set the encoded url in the model

I prefer option a) because I already have a lot of JSP's to modify, but c) is still on the table if there is a compelling reason to choose it.

URL encoding; eg transform a relative url like /search/��� into /search/%FF%D0%D1, for example.

Also, a form submission isn't an option either.