BlogJava-David.Turing's blog-随笔分类-SOA/WebServicehttp://www.blogjava.net/security/category/9930.htmlzh-cnThu, 12 Jul 2012 23:07:23 GMTThu, 12 Jul 2012 23:07:23 GMT60从java.lang.UnsupportedOperationException看WebLogic WS*协议栈的变迁http://www.blogjava.net/security/archive/2008/07/11/weblogic_webservice.htmldavid.turingdavid.turingFri, 11 Jul 2008 00:29:00 GMThttp://www.blogjava.net/security/archive/2008/07/11/weblogic_webservice.htmlhttp://www.blogjava.net/security/comments/214158.htmlhttp://www.blogjava.net/security/archive/2008/07/11/weblogic_webservice.html#Feedback4http://www.blogjava.net/security/comments/commentRss/214158.htmlhttp://www.blogjava.net/security/services/trackbacks/214158.html阅读全文

david.turing 2008-07-11 08:29 发表评论
]]>用JSR181驱动SpringSide Web Serviceshttp://www.blogjava.net/security/archive/2006/10/31/Spring_JSR181_XFire_WebService.htmldavid.turingdavid.turingTue, 31 Oct 2006 01:47:00 GMThttp://www.blogjava.net/security/archive/2006/10/31/Spring_JSR181_XFire_WebService.htmlhttp://www.blogjava.net/security/comments/78215.htmlhttp://www.blogjava.net/security/archive/2006/10/31/Spring_JSR181_XFire_WebService.html#Feedback0http://www.blogjava.net/security/comments/commentRss/78215.htmlhttp://www.blogjava.net/security/services/trackbacks/78215.html阅读全文

david.turing 2006-10-31 09:47 发表评论
]]>Federate Portal，面向SOA的Portalhttp://www.blogjava.net/security/archive/2006/10/16/soa_federate_portal.htmldavid.turingdavid.turingMon, 16 Oct 2006 14:25:00 GMThttp://www.blogjava.net/security/archive/2006/10/16/soa_federate_portal.htmlhttp://www.blogjava.net/security/comments/75495.htmlhttp://www.blogjava.net/security/archive/2006/10/16/soa_federate_portal.html#Feedback4http://www.blogjava.net/security/comments/commentRss/75495.htmlhttp://www.blogjava.net/security/services/trackbacks/75495.html阅读全文

david.turing 2006-10-16 22:25 发表评论
]]>9月23日成都WS-Security演讲内容稿http://www.blogjava.net/security/archive/2006/09/22/WS_Security.htmldavid.turingdavid.turingThu, 21 Sep 2006 17:03:00 GMThttp://www.blogjava.net/security/archive/2006/09/22/WS_Security.htmlhttp://www.blogjava.net/security/comments/71223.htmlhttp://www.blogjava.net/security/archive/2006/09/22/WS_Security.html#Feedback4http://www.blogjava.net/security/comments/commentRss/71223.htmlhttp://www.blogjava.net/security/services/trackbacks/71223.html阅读全文

david.turing 2006-09-22 01:03 发表评论
]]>CeltiXfireProposal让Axis2在Apache的地位被动摇？http://www.blogjava.net/security/archive/2006/08/28/xfire_soa_websevice.htmldavid.turingdavid.turingMon, 28 Aug 2006 05:51:00 GMThttp://www.blogjava.net/security/archive/2006/08/28/xfire_soa_websevice.htmlhttp://www.blogjava.net/security/comments/66164.htmlhttp://www.blogjava.net/security/archive/2006/08/28/xfire_soa_websevice.html#Feedback5http://www.blogjava.net/security/comments/commentRss/66164.htmlhttp://www.blogjava.net/security/services/trackbacks/66164.html阅读全文

david.turing 2006-08-28 13:51 发表评论
]]>思考Spring拦截技术与Web Service异常处理的结合http://www.blogjava.net/security/archive/2006/08/26/65878.htmldavid.turingdavid.turingFri, 25 Aug 2006 16:24:00 GMThttp://www.blogjava.net/security/archive/2006/08/26/65878.htmlhttp://www.blogjava.net/security/comments/65878.htmlhttp://www.blogjava.net/security/archive/2006/08/26/65878.html#Feedback2http://www.blogjava.net/security/comments/commentRss/65878.htmlhttp://www.blogjava.net/security/services/trackbacks/65878.html例外的是，当你的项目比较庞大的时候，你的业务方法可能很多并且你并不了解他们的内部实现。
作为一个优秀的Web Service架构师，你需要解决Web服务跟这些业务异常的结合问题。

现实是我们都不想关心这些业务类的实现，尽管这些异常从Java类抛出，并且Web服务必须处理这些
异常，起码，你需要让客户端知道：web服务端抛出异常。

以XFire为例， 假设有一个Web服务A和一个调用A的客户端B
A服务端 B客户端
当B->A发起一个Web服务请求，A抛出异常的时候，会直接new XFireFault并扔向XFire客户端。
解耦思路带领下，应该先将异常处理剥离出来。
于是，有
A服务-A异常处理handler  B客户端-B异常处理handler
这样，从架构的角度，A/B均无需考虑异常问题。

XFire客户端可以通过addFaultHandler来增加异常处理，XFire服务端则可以通过典型的AOP异常拦截来隔离
业务逻辑和Web服务之间的纽带。


david.turing 2006-08-26 00:24 发表评论
]]>跟XFire对比, AXIS2是垃圾吗? http://www.blogjava.net/security/archive/2006/08/23/AXIS.htmldavid.turingdavid.turingWed, 23 Aug 2006 04:40:00 GMThttp://www.blogjava.net/security/archive/2006/08/23/AXIS.htmlhttp://www.blogjava.net/security/comments/65249.htmlhttp://www.blogjava.net/security/archive/2006/08/23/AXIS.html#Feedback18http://www.blogjava.net/security/comments/commentRss/65249.htmlhttp://www.blogjava.net/security/services/trackbacks/65249.html阅读全文

david.turing 2006-08-23 12:40 发表评论
]]>解决异常：Parser has reached the entity expansion limit "64,000" set by the Applicationhttp://www.blogjava.net/security/archive/2006/08/10/62815.htmldavid.turingdavid.turingThu, 10 Aug 2006 08:22:00 GMThttp://www.blogjava.net/security/archive/2006/08/10/62815.htmlhttp://www.blogjava.net/security/comments/62815.htmlhttp://www.blogjava.net/security/archive/2006/08/10/62815.html#Feedback0http://www.blogjava.net/security/comments/commentRss/62815.htmlhttp://www.blogjava.net/security/services/trackbacks/62815.html异常：分析器已达到由应用程序设置的实体扩展限制"64,000"

用JDOM分析一个超大的xml文件，大概20M，估计有很多Elements：

  SAXBuilder saxbuilder = null;
  Document doc_all=null;

  saxbuilder = new SAXBuilder(); // 新建立构造器
  
  try {
   FileInputStream xmlfile=new FileInputStream("verybig.xml");
   doc_all=saxbuilder.build(xmlfile); // 读入文件
  } catch (FileNotFoundException e) {
   System.err.println("缺少文件！请检查");
   System.exit(-1);
  } catch (JDOMException e) {
   System.err.println("解析XML模板文件出错！请检查");
   e.printStackTrace();
  } catch (IOException e) {
   e.printStackTrace();
  }

抛出异常：
reached the entity expansion limit "64,000" set by the Application.
        at TErrorHandler.fatalError(XMLError.java:198)
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3342)
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3333)
        at org.apache.crimson.parser.Parser2.expandEntityInContent(Parser2.java:2667)
        at org.apache.crimson.parser.Parser2.maybeReferenceInContent(Parser2.java:2569)
        at org.apache.crimson.parser.Parser2.content(Parser2.java:1980)
        at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1654)
        at org.apache.crimson.parser.Parser2.content(Parser2.java:1926)
        at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1654)
        at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:634)
        at org.apache.crimson.parser.Parser2.parse(Parser2.java:333)
        at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
        at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
        at XMLError.DOMRead(XMLError.java:101)
        at XMLError.main(XMLError.java:30)

中文翻译是：分析器已达到由应用程序设置的实体扩展限制"64,000"

原来是JAXP的bug，换JDK1.5解决！



david.turing 2006-08-10 16:22 发表评论
]]>