fortaotao http://fortaotao.javaeye.com UTF-8 Copyright 2003-2008, JavaEye.com http://blogs.law.harvard.edu/tech/rss JavaEye - 做最棒的软件开发交流社区 从此不敢自称架构师 fortaotao 作者: fortaotao  链接：http://fortaotao.javaeye.com/blog/197761  发表时间: 2008年05月28日

声明：本文系JavaEye网站发布的原创博客文章，未经作者书面许可，严禁任何网站转载本文，否则必将追究法律责任！

合格的架构师必须达到以下要求。
The Senior Solution Architect (Systems) has a broad range of technical skills on systems solution. He/she involves leading the architecting and designing of systems solution consisting of Server, Blades, cluster, and management.

The Architect has overall responsibility for gathering customer's business requirements, translating those requirements into cost-effective solution, strategies, architectures, and guiding the implementation of those solutions to deliver high quality outcomes to meet or exceed customer expectations in a timely manner.


Responsibilities and Accountabilities:
-Develop trusted advisor status with customers and provide technical leadership in architecting technical solution for customers.

-Act as lead architect, or as a member of a team of Architects to lead and oversee solution implementation and project delivery, including creation of detailed designs of storage solution.

-May assume a quality assurance role on one or more engagements to ensure that solution design or architectures proposed and implemented are in accordance with current best practices and standards.

-Provide support to Project Manager to perform technical planning, requirements gathering, analysis, architecture, design, development, testing and deployment tasks

-During presales phase, assess the feasibility of providing systems solutions that meet customers requirements, given time and budgetary constraints, limited resources and understanding of abilities of the team.

-During presales and bidding phase, provide responsive and quality technical assistance to account teams as a subject matter expert, with opportunity qualification, solution scoping, cost estimation, technical risk assessment, and overall solution formulation.

-Prepare and deliver persuasive technical presentations to support bid efforts.

-Lead technical demonstrations and proof-of-concept efforts.

-Act as a local or regional expert in one or more technical focus areas, and provide mentoring to junior consultants or architects.

-Undertake research, capture, development and dissemination of best practices through technical community collaboration, white-paper authoring, solution development and intellectual property reuse.

-At least 15 years of IT experience with 8 years of solid experience in the capacity of Solution Architect and track record in system integrator or multi-national vendor environment.

-A self starter and team player with excellent analytical and troubleshooting skills.

-Display high levels of energy and drive, thrives under pressure, with strong business acumen, strong process orientation and excellent verbal and written communication skills

-Solid experience in entire project implementation life-cycle.
Good understanding of Data Center solution business drivers (e.g. eco, security, high availability, disaster recovery)

-Excellent technology background and skills in Data Center Solutions: relocation, consolidation, optimization, virtualization

-Project experience with Systems products (open system or mainframe), preferably from Sun, IBM, HP.

-Willing to travel within Greater China to support business and project delivery activities.
本文的讨论也很精彩，浏览讨论>>


JavaEye推荐



]]> Wed, 28 May 2008 10:31:17 +0800 http://fortaotao.javaeye.com/blog/197761 http://fortaotao.javaeye.com/blog/197761 Spring多视图并存比较好的解决方案 fortaotao 作者: fortaotao  链接：http://fortaotao.javaeye.com/blog/154675  发表时间: 2008年01月10日

声明：本文系JavaEye网站发布的原创博客文章，未经作者书面许可，严禁任何网站转载本文，否则必将追究法律责任！

网上搜了下资料，自己也实战了下。分享一下。
传统的web.xml写法不变，如下为相关配置信息： 
<servlet>  
  <servlet-name>myportal</servlet-name>  
  <servlet-class>
org.springframework.web.servlet.DispatcherServlet
  </servlet-class>  
  <load-on-startup>1</load-on-startup>  
</servlet>  
<servlet-mapping>  
  <servlet-name>myportal</servlet-name>  
  <url-pattern>*.html</url-pattern>  
</servlet-mapping>

之所以将url-pattern配置成*.html，一是隐藏技术实现，二是增加搜索引擎的搜索概率。看个人爱好。
关键是对应的myportal-servlet.xml文件中的配置. 
<bean id="viewResolver" class="com.myportal.web.core.MultipleViewResolver">
    <property name="resolvers">
        <map>
            <entry key="jsp">
                <bean class="org.springframework.web.servlet.view.InternalResourceViewResolver">
                    <property name="viewClass" value="org.springframework.web.servlet.view.JstlView" />
			        <property name="prefix">  
			            <value>/WEB-INF/jsp/</value>  
			        </property>  
                </bean>
            </entry>
            
            <entry key="vm">
                <bean class="org.springframework.web.servlet.view.velocity.VelocityViewResolver">
                    <property name="contentType" value="text/html;charset=UTF-8" />
                </bean>
            </entry>
        </map>
    </property>
</bean>

然后大家在自己的Controller类里面必须返回如下视图:new ModelAndView("test.jsp");或者new ModelAndView("test.vm");
最后是自己写的ViewResolver，如下： 
public class MultipleViewResolver implements ViewResolver
{
	private Map<String, ViewResolver> resolvers;
    public void setResolvers(Map<String, ViewResolver> resolvers) 
    {
        this.resolvers = resolvers;
    }

public View resolveViewName(String viewName, Locale locale)        throws Exception {
		 int n = viewName.lastIndexOf(".");

	        if(n==(-1)) return null;

	        // 获得扩展名:

	        String suffix = viewName.substring(n+1);

	        // 取出对应的ViewResolver:

	        ViewResolver resolver = resolvers.get(suffix);

	        if(resolver!=null)

	            return resolver.resolveViewName(viewName, locale);

	        // 没有找到对应的ViewResolver就抛异常:

	        return null;

	}

}

当然，大家可以对自己写的ViewResovler进行功能上的丰富，比如：设定默认的视图解析为jsp，那你的Controller的View就可以偷懒写成new ModelAndView("test")了。基本功能有了，完善慢慢来。
本文的讨论也很精彩，浏览讨论>>


JavaEye推荐



]]> Thu, 10 Jan 2008 11:51:55 +0800 http://fortaotao.javaeye.com/blog/154675 http://fortaotao.javaeye.com/blog/154675