白板文化

欢迎定做各种尺寸白板,报刊架直销网代理销售白板,报刊架,杂志架,展示架,书报架,汇集应豪报刊架,得兴报刊架,百利佳书报架,新三星白板,壕铭白板等众多品牌,是北京白板,北京报刊架专业供应商,报价可靠,北京市内免费送货上门....
公司网址：www.gaotong123.com

zhuang,

Thanks for your consideration, looking forward to your further contact.

Hi,

I have been working in a Telecom company for 3 years, focusing on .net and sql server 2000. I have done many n-tier applications, either window-based or web-based.

I am now located in Manchester, UK, but want to go back to China due to family reason. I am a hardworking people with excellent education background.

I will send you my CV very soon once I tidy it up.

Thanks

zhuang

job description
* Create and maintain As-Is and To-Be strategies and system landscapes
* Lead and collaborate with peer architects to recommend domain-level convergence strategy & target architecture that supports Bill of IT goals
* Provide thought leadership and innovation in the planning, design, and creation of domain architecture constructs (e.g. reference architectures), and deliverables (e.g. standardized work, common initiatives)
* Provide architectural costs, benefits, and risk management (including operations, security)
* Define and develop architecture solutions
* Communicate strategic vision and detailed architecture representations
* Work with the Enterprise Data Architect to develop a domain-level Data Management Program
* Develop, socialize, and publish architectural deliverables (As-Is & To-Be environment strategies, system landscapes, application connectivity methods and frameworks, decomposition diagrams)
* Support the release team by reviewing global Block-point releases and advising of negative impacts based on the architectural roadmap
* Document standards for common data objects, and data formats
* Participate in reviews of technical/product evaluations
* Provide coaching, mentoring, and guidance to project teams (e.g. review checklists, architecture starter kit collateral, integration requirements, tradeoff analysis)
* Author change requests for new standards, and deviations from standards
* Provide cost benefit and risk management as required.

Qualifications
your profile
* Recognized expert in Enterprise Architecture development and management
* Proven track record IT management or IT consulting with experience in financial services and/or insurance industries
* Proven experience in examining and re-engineering business and IT processes, formulating policy, and developing and implementing new strategies
* Advanced verbal and written communication skills
* Excellent facilitation, negotiation, and consensus building skills
* Communicate effectively with a wide variety of people including senior management
* Knowledge of project management principles, practices, techniques, and tools
* Experience working on a geographically dispersed team
* Strong interpersonal and relationship management skills
* Expert knowledge of data integration design principles in a complex computing environment
* Demonstrated ability to build consensus and promote standards, and design principles to project teams
* Expert technology research and analysis

job description
* Provide technical and thought leadership in assisting client to move toward Services Oriented Architecture
* Develop, socialize, and publish architectural deliverables (As-Is & To-Be environment strategies, system landscapes, application connectivity methods and frameworks, decomposition diagrams)
* Create & Maintain landscapes/diagrams/blueprints to reduce application, integration, and operational complexity
* Determine Enterprise Patterns based upon Adaptive Enterprise principles and component engineering practices
* Create application convergence plans and implementation plans to improve reusability
* Identify and define common components for re-use
* Support the release team by reviewing global Block-point releases and advising of negative impacts based on GMAC level architectural roadmap
* Produce application architecture decomposition diagrams which depicts the major architectural layers (presentation, business rules, Data, Middleware, etc.) that depict the major components (COTS package, custom software, application interfaces)
* Author requests to build proof-of-concepts and prototypes
* Author change requests for new standards, and deviations from standards
* Support oversight architect with the constraints and tradeoffs needed to create viable solutions
* Provide cost benefit and risk management as required

Qualifications
* 10+ years working experience in system/IT architect design and plan
* Expert design, development, and deployment of applications using a variety of technologies and platforms (mainframe, client/server)
* Recent industry relevant experience using J2EE/.NET, Web Services, Portals, Integration, and SOA capabilities
* Demonstrate ability to build consensus and promote standards
* Advanced verbal and written communication skills

Validator in Java world

http://jakarta.apache.org/commons/validator/

一个WebService基础框架的介绍
http://www.huihoo.com/xml/cortex/

好！！

JE上的文章，看起来大家对这个都很感兴趣嘛，最近

Design Patterns of the enterprise Rich Client design （http://forum.javaeye.com/viewtopic.php?t=17588）

to 双鱼坐：
UI使用LocalFacade包装和访问Domain的目的就是为了减少分布调用,提高效率。
我们可不希望保存一条数据时，跑到服务器判断条件A不满足，用户更改A后再保存又跑到服务器后发现B又不满足，最后跑个好几趟才终于保存下去。要知道这些判断如果不需要访问服务器资源，本来都可以在客户端判断的。（不过，有意思的是，因为老系统很多都这样搞的，客户似乎已经习惯了这种慢速，我有时倒觉得自己纯技术了）


另外，实际上我们在后一个项目中，UI也是分成两层，上面一层只是数据绑定和显示(View)，下面一层是数据的简单处理(UIController)。View的控件在事件响应中，基本上直接将消息转发给UIController处理，UIController要考虑是访问后台还是前台的逻辑，要考虑是否使用读写缓存（因为client和appServer分布，所以client运用了很多缓存和同步机制）等等。

这样做的目的，主要因为WinForm的界面层维护起来非常麻烦，又很难重用。不过因为第一次尝试，在View和Controller的区分上处理得还不好，还需要继续摸索和改进。

to gozh2002 :

DTO,不同的人可能有不同的理解,在J2EE里面比较多的理解好像是各层之间传输的数据载体,比如从存储层到业务层,有的人把它们都叫DTO(我不太清楚他们是否把EntityBean也称为DTO,因为在EntityBean里面好像就如同你说的可以包含数据访问逻辑) ; 另一种是我这里的描述,当然也是PEAA那本书里面描述的, 在业务层和表现层之间传递的数据,因为Domain的对象关联的内容往往比较多,在分布式的结构里面,为了效率的原因,我们只返回界面所必要的数据,所以需要将Domain对象转化成DTO.这些DTO只是数据的容器,没有任何行为,供UI使用. 所有的逻辑都在Domain里面, 另外由RemoteFacade控制你所谓的事务和流程。

to age0:
抱歉，我可能整个介绍还不太清楚，补充了一份概要的部署图，可以看到实际上服务器里面也要部署后台所有的组件（图里面省略了很多），因为RemoteFacade只在服务端被执行，需要注意，客户端的Domain和服务端的Domain其实就是一个东西。

实际上我在公司里面还看到另外一种架构，所有的组件都部署到客户端在客户端执行，所有的业务逻辑甚至O/R Map工作都在客户端直接处理，服务端只有一有个DB Access的封装，从概念上说有点象数据库访问的代理，因为不允许从客户端直接访问数据库 可能同你说得很接近。说实话我最早有点BS这种结构，可能是受太多“正统”的三层架构的影响，现在看起来好像也没什么不可接受的，因为我们的系统的集成度还不高，也不是那么SOA，还没有其它系统访问我们后台业务逻辑的需求（有这种需求的时候，应该差不多这些系统都要重新构造了）。所以，如果不考虑集成的话，这种被BS的架构倒确实很实用的值得推荐的架构

呵呵，如果ui所用的facade仅仅是对domain object的包装，那你的分布式肯定是怪怪的了。感觉ui是可以做得与business完全分离的，这样你的分布式才有了意义。最近我也一直在研究这个话题，无论是web的还是winform的。

“我承认UI必不可少得包含一些逻辑，比如非空输入检查，这种检查往往UI和Domain都需要做的，但有些业务特别是计算还是只由Domain去处理好些”

反对这样的说法。ui完全没有必要承受任何业务逻辑这样的职责。如果要承受也不是直接承受----如同domain的同样的方式，而是间接承受。说到底，你需要在ui与你的分布式domain间建立一个有别于目前bindable的ui的方式。不能满足于某种形式上的分离或者解耦。

举个例子，非空检查，目前你是通过domain要求该域为非空，然后domain将这个要求传达到ui。换句话说，ui为什么会要求为非空，可以直接追溯到domain，而不是通过某种单向的、完全隔离的、简单的、细粒度的、完全业务无关的控制器。你要一个datagrid显示一个长度为3000行的数据集，需要一个滚动条或者分页器。如果你有一种简单的方式告诉这个datagrid一共要显示3000行而不是由这个datagrid去得到了一个列表来检查这个行数的话，你就真正做到了ui与domain的分离。除此之外的分离都是自欺欺人。

将所有组件部署在同一个计算空间没什么好奇怪的，效率、性能、架构简洁性都可以得到保证，只是BS将大部分组件部署在服务器上，而CS将大部分组件部署在客户端，这是由CS和BS各自特性所决定的。如果CS非要象BS一样将所谓的“后台”组件部署在服务端那才叫自寻烦恼。前台、后台应该是根据逻辑应用来区分，而非根据物理部署位置。

Good one!!!
I think your DTO layer definition is some thing like TypedDataSet, which includes the mapping of two or more tables with relationship, but of course here in DTO, this is object mapping.

So i assume if you have any business rules such as:
update two or more records in different tables,
update one record with premise that another record in another table has already exited.

They are encapsulated in DTO? or do you have another business rules
layer to manage the transaction spanning across more than one DTO
or domain objects?

解决问题就是好方法，当然要易于维护。

sign，我遇到的问题和你一模一样，处理的方式也几乎接近：后台组件必须全部部署到客户端。总感觉不是很爽，怪怪地

也只有这样了，MS的控件生来好象就是用datatable来绑定的(也可以通过自己动态处理对象属性和列名绑定来解决domain对象的绑定), 除了web 中的listview控件。

to yexiaojun
datagrid显示的数据我们分了两类，1）业务对象集合，2）条件查询结果
针对业务对象集合，比如 1个定单有10个定单项，定单和定单项肯定是作为EntityDTO对象传递到界面的，通过给DataGrid赋值的形式进行数据绑定，这个工作量不会有你想象中那么大
针对条件查询结果，我们有特殊通道，DataTable从存储层一路走到UI层，采用习惯的直接绑定形式，因为和这篇文章无关，所以没提。

请问你是用什么对象在UI层绑定datagrid的？
据我所知datagrid并不支持domain对象的绑定