1.在无网络环境时，要把config-tiles.xml里的dtd文件位置改在本地的文件路径，否则出来IO Error
<!DOCTYPE tiles-definitions PUBLIC
"-//Apache Software Foundation//DTD Tiles Configuration//EN"
"D:/eclipse/workspace/HMS/WEB-INF/lib/tiles-config.dtd">
18:45:04,046 ERROR [TilesPlugin] Can't create Tiles definition factory for modul
e ''.
18:45:04,046 ERROR [[action]] Allocate exception for servlet action
org.apache.struts.tiles.DefinitionsFactoryException: IO Error while parsing file
'/WEB-INF/config-tiles.xml'. \WEB-INF\lib\tiles-config.dtd
2. 如何从inputstream得到file:
classLoader.getResource() -->inputstream.toURI() --> new File(uri)
URI uri = this.getClass().getClassLoader().getResource("WEB-INF/data/hotelx/rooms").toURI();
File directory = new File(uri);
3. within jsp <%%>
we can not use Vector<***>
it seems jasper can't parse jdk 1.5 syntax??
4. in elicpse plugin development, after you create the action and plugin class in
eclipse wizard, never try to change their names, otherwise, in runtime application,
the classloader will never find the action class.
5. 用<%=request.getContextPath()%>可以取得当前war的名字，
有一个问题。
用"href="<%=request.getContextPath()%>/jsp" 出来的结果是正确的"http://bruce-liu:8080/mdf-gen/jsp",
但是如何用"href="/<%=request.getContextPath()%>/jsp"，出来的结果就是""http://mdf-gen/jsp",
所以不能在前面加上"/".
6 exception using junitreport (java.lang.ClassNotFoundException: redirect)
To fix the problem you have the choice to:
- Upgrade your Xalan version to the latest one (or anything 2.4.1+) via the
endorsment mechanism
- Upgrade your JDK to 1.4.2-01+
- Use the ${ant.home}/etc/junit-frames-xalan1.xsl
Any option should fix the problem, this is due to an unfortunate
incompatibility between Xalan versions and the need to support XSLTC in JDK 1.5
http://issues.apache.org/bugzilla/show_bug.cgi?id=30524
7
矢量标识语言(VML),精度图像标识语言(PGML)都是作为W3C的矢量图像初始标准在1998年提出的.
VML和PGML在很多地方非常的类似,但VML比较适合一些普通矢量图像,而PGML可以做出更加丰富多彩,
适合专业设计和公众出版的图像.
为了进一步促进图像标准的发展,W3C成立了SVG工作组.SVG工作组将VML和PGML的优势结合在了一起,
重新推出了新的标准矢量格式,这就是SVG.
哪些是SVG能做到而GIF,JPEG做不到的?
SVG较位图图像有很多独特的优势:
1.任意放缩: 用户可以自由的放缩图像而不会破坏图像的清晰度.
2.文本独立: SVG图像中的文字独立于图像,可以编辑和查询.同时,也不会再有字体的限制,用户系统即使没有安装某一字体,
同样可以看到这些字体.
3.较小文件尺寸: 一般而言,SVG图像要比其他网络图像格式如GIF,JPEG更小,下载更迅速.
4.超强显示效果: SVG图像的清晰度适合任何屏幕分辨率或打印分辨率(dpi),无论是300dpi,600dpi甚至更高,
都不会产生位图图像的马赛克现象.
5.超强色彩控制: SVG图像具有一个1600万色彩的调色板,支持ICC标准,RGB,线性填充和遮罩.
6.超强交互性: 由于SVG是基于XML的,因而能制作出空前强大的动态交互.SVG图像能对用户动作做出不同响应,
例如高亮,声效,特效,动画等.
8
BPEL(Business Process Execution Language)用于异构环境的,基于Web的复杂环境业务流系统。
http://en.wikipedia.org/wiki/BPEL
http://searchwebservices.techtarget.com/sDefinition/0,,sid26_gci845110,00.html
9
when you use some opensource tools, such as httpunit, dom4j, apache-jakarta-commons,
axis, aspectj, ant, castor, struts, opencms, xdoclet. the quickest way to solve your problems
is go to their corresponding mail list archive, and do a search. it is more effective than google.
you always find no valuable from google search for these issues.
10
request.getRequestURI() 返回值类似：/xuejava/requestdemo.jsp
request.getRequestURL() 返回值类似：http://localhost:8080/xuejava/requestdemo.jsp
response.sendRedirect(request.getRequestURL()+"menubar.do?method=getWelcomePage");
System.out.println("request.getRequestURL() "+request.getRequestURL());
---->
request.getRequestURL() http://bruce-liu:8080/hotel/
11.
改变cvs的cvsroot参数中的服务器地址
找CVS对应的Root文件：D:\IJC\ijs\expense_report\CVS\Root, 直接改文件内容即可。
12. netstat -ab 可以显示所有的端口占用情况，并显示哪个应用占用哪个端口，
在启动Jboss时如果发现端口已经被占用，可以
用这个命令来查用哪个应用占用了该端口，然后在任务管理器杀之即可。
13.
Does it meet the bar?
When the team moved up to Microsoft from Connectix one thing that was quickly evident was that there were a number of 'cultural' differences between the two companies. This was highlighted by the fact that when we started the entire program management and development teams were from Connectix while the majority of the test team was from Microsoft. We have spent a lot of time trying to resolve the differences and want to end up with the 'best from both worlds' - however we still have a number of areas that need work :-)
One 'Microsoftism' that I have enjoyed having as a program manager is the concept of a 'bug bar'. This is a list of requirements that a bug must meet in order to be fixed in a milestone or release. Examples for a service pack would include things like 'Customer reported problems', 'Application crashes' or 'Data loss bugs'. Then as bugs come in during the development cycle they are assessed against the 'bar' and a decision is made to fix the bug or to postpone it to a future release.
This is invaluable for a number of reasons. Firstly, it helps to ensure a consistent quality approach for a release as it stops us from ignoring major bugs, and from wasting time on trivial issues. Secondly, it helps to be able to give a precise answer as to why a certain bug did not get fixed in a given release. Finally, it is great to be able to review the fixed and postponed bugs before shipping a product and be confident that the right changes have been made to the product.
However the thing that sticks in my mind about the 'bug bar' is this:
At Microsoft there are regular bug triage meetings where bugs are reviewed and assigned to an appropriate person. From time to time a contentious bug will be reported - where people are divided as to whether this bug should be fixed, and if it should be fixed how it should be fixed, and what the potential impact of the fix is. Invariably a minute or two into the discussion someone will ask 'Does it meet the bar?' Answering this question will resolve all debate. If it meets the bar it should be fixed. If it does not meet the bar we will get it next time.
Cheers,
Ben
|
