java才子

学习,成长,成就

  BlogJava :: 首页 :: 新随笔 :: 联系 :: 聚合  :: 管理 ::
  2 随笔 :: 0 文章 :: 0 评论 :: 0 Trackbacks

2008年7月26日 #

Sun technologist calls SOAP stack a failur
--By paul krill,JavaWorld.com
SAN FRANCISCO (07/24/2008) - The SOAP stack for Web services was branded a failure this week by Tim Bray, a Sun Microsystems technologist and co-inventor of XML, who hailed the REST (Representational State Transfer) mechanism as a SOAP alternative.

"The SOAP stack is generally regarded as an embarrassing failure these days," said Bray, who is Sun director of Web technologies, in an interview Wednesday afternoon at the O'Reilly Open Source Convention (OSCON) in Portland, Ore. "REST does what [the SOAP stack] was trying to do in a much more viable, elegant, cheap, affordable way except that we've got no tooling around it yet."

REST can be used for integration, enabling, for example, PHP Web front ends to talk to a Java manufacturing system, said Bray.

Tools to help developers work with REST are coming from companies such as Sun, Microsoft, and Oracle, said Bray. These tools would make it easier to create REST services and test them, he said.

SOAP and the attendant set of WS-* (ws star) specifications for security, messaging, and other capabilities certainly have had their detractors. Some, including Ruby on Rails founder David Heinemeier Hansson, have called these specifications " ws death star" -- a takeoff on the enemy home base in the "Star Wars" movies.

Analysts at ZapThink, who have specialized in technologies such as Web services and SOA, sharply disagreed with Bray.

"Tim Bray is a REST proponent and he'll say what he needs to, to bash SOAP and promote REST. SOAP is alive and well. There's no widespread movement away from SOAP. If you can find evidence of that [apart from Tim Bray], let me know," said Ronald Schmelzer, ZapThink senior analyst.

"It's ironic as well that he's incorrect about the lack of REST tooling. JackBe, Corizon, and others support REST," said Jason Bloomberg, a managing partner at ZapThink.

Bray also cited a need for more and better testing frameworks for REST-oriented protocols and frameworks.

During a keynote presentation at OSCON on Friday, Bray will talk about the "language inflection point," in which various languages such as Perl, Python, and Ruby have been gathering momentum at the expense of the established Java and .Net platforms.

"Up until two years ago, if you were a serious programmer you wrote code in either Java or .Net," Bray said. "[Now], there are all these options that people are looking at and it's really an inflection point."

The Java platform is accommodating scripting languages such as Ruby and Python on the JVM, Bray noted. Sun has been enabling these to work on the Java Virtual Machine. "The Java language is not what the cool kids are choosing to use these days," said Bray.

Still, Java will stay around, he said. "The Java language isn't going away. It's the world's most popular programming language," Bray said.

"I think that like it or not, we're stuck with a multilanguage future," he stressed.

posted @ 2008-07-26 11:25 efatao 阅读(47) | 评论 (0)编辑 收藏

2008年7月23日 #

Java语言程序员人生:J2ee的学习流程简介

在这里我谈谈我在学习j2ee流程,并谈到在此过程中领会的经验和教训。以便后来者少走弯路。
Java发展到现在,按应用来分主要分为三大块:J2SE,J2ME和J2EE。这三块相互补充,应用范围不同。
   J2SE就是Java2的标准版,主要用于桌面应用软件的编程;
   J2ME主要应用于嵌入式系统开发,如手机和PDA的编程;
   J2EE是Java2的企业版,主要用于分布式的网络程序的开发,如电子商务网站和ERP系统。

先学习j2se
要学习j2ee就要先学习j2se,刚开始学习j2se先建议不要使用IDE,然后渐渐的过渡到使用IDE开发,毕竟用它方便嘛。学习j2se推荐两本书,《java2核心技术一二卷》,《java编程思想》,《java模式》。其中《java编程思想》要研读,精读。这一段时间是基本功学习,时间会很长,也可能很短,这要看学习者自身水平而定。

不要被IDE纠缠

在学习java和j2ee过程中,你会遇到五花八门的IDE,不要被他们迷惑,学JAVA的时候,要学语言本身的东西,不要太在意IDE的附加功能,JAVA编程在不同IDE之间的转换是很容易的,过于的在意IDE的功能反而容易耽误对语言本身的理解。目前流行的IDE有jbuilder,eclipse和eclipse的加强版WSAD。用好其中一个就可以了,推荐从eclipse入手j2ee。因为Jbuilder更适合于写j2se程序。

选择和学习服务器使用配置

当你有了j2se和IDE的经验时,可以开始j2ee的学习了,web服务器:tomcat,勿庸置疑,tomcat为学习web服务首选。而应用服务器目前主要有三个:jboss、weblogic、websphere。有很多项目开始采用jboss,并且有大量的公司开始做websphere或weblogic向jboss应用服务器的移植(节省成本),这里要说的是,学习tomcat和jboss我认为是首选,也是最容易上手的。学习服务器使用配置最好去询问有经验的人(有条件的话),因为他们或许一句话就能解决问题,你自己上网摸索可能要一两天(我就干过这种傻事),我们应该把主要时间放在学习原理和理论上,一项特定技术的使用永远代替不了一个人的知识和学问。

学习web知识

如果你是在做电子商务网站等时,你可能要充当几个角色,这是你还要学习:
html,可能要用到dreamwave等IDE。
Javascript,学会简单的数据校验,数据联动显示等等

J2eeAPI学习

学习j2eeAPI和学习服务器应该是一个迭代的过程。

先学习jsp和servlet编程,这方面的书很多,我建立看oreilly公司的两本《jsp设计》和《java servlet编程》,oreilly出的书总是那本优秀,不得不佩服。

学习jdbc数据库编程,j2ee项目大多都是MIS系统,访问数据库是核心。这本应属于j2se学习中,这里拿出来强调一下。

学习jndi api,它和学习ejb可以结合起来。

学习ejb api,推荐书《精通ejb》

经过上面的这些的学习,大概可以对付一般的应用了。

有人说跟着sun公司的《j2ee tutorial》一路学下来,当然也可以。



学习ejb设计模式和看代码(最重要)

设计模式是练内功,其重要性可以这么说吧,如果你不会用设计模式的话,你将写出一堆使用了ejb的垃圾,有慢又是一堆bug,其结果不如不用ejb实现(ejb不等于j2ee)
无论学习什么语言,都应该看大量代码,你看的代码量不到一定数量,是学不好j2ee的
目前有很多开源的工程可以作为教材:

   jive论坛
   petstore sun公司
   dune sun公司

等等,研读一个,并把它用到自己的工程中来。

J2ee其他学习

当你渐渐对j2ee了解到一定深度时,你要开始关注当前领域中的一些技术变化,J2ee是一块百家争鸣的领域,大家都在这里提出自己的解决方案,例如structs,hiberate,ofbiz等等,学习这些东西要你的项目和目标而定,预先补充一下未尝不可,但不用涉及太深,毕竟学习原理和理论是最最重要的事。

目前常见j2eeAPI
   JavaServer Pages(JSP)技术1.2
   Java Servlet技术2.3
   JDBC API 2.0
   Java XML处理API(JAXP)1.1
   Enterprise JavaBeans技术2.0
   Java消息服务(JMS)1.0
   Java命名目录接口(JNDI)1.2
   Java事务API(JTA) 1.0
   JavaMail API 1.2
   JavaBeans激活架构(JAF)1.0
   J2EE连接器体系结构(JCA)1.0
   Java认证和授权服务(JAAS)1.0

学习上面的某些API要以你的项目而定,了解所有他们总之是有好处的

上面印证了大家说的一句话,java语言本身不难学,但是技术太多,所以学java很费劲。回想一下,基本上每个初学者,在刚学习java的时候可能都会问别人这么一句话,你怎么知道的哪个方法(api)在哪个包里的?呵呵,无他,唯手熟尔。
posted @ 2008-07-23 14:28 efatao 阅读(80) | 评论 (0)编辑 收藏

仅列出标题