70 likes | 178 Views
Approach for UBL implementation & technical issues. Nobuyuki Sambuichi Shin Takagi R&D Center Hitachi Systems and Services, Ltd. 1. Approach. Hitachi Systems & Services. 2004/03 Implementing almost all business activity (except for “ add detail ” ). 2003/10
E N D
Approach for UBL implementation & technical issues Nobuyuki Sambuichi Shin Takagi R&D Center Hitachi Systems and Services, Ltd.
1 Approach Hitachi Systems & Services 2004/03 Implementing almost all business activity (except for “add detail”) 2003/10 Implementing only “place order” message 2004/05 UBL 1.0 CD 2003/11 UBL 1.0 beta 2003/01 UBL0p70 OASIS UBL-TC
2 Objectives • Objectives; • develop a set of sample activity exchanging XML business documents, • evaluate UBL as Business Document and • develop business logic framework responding to UBL flexibility or extensibility.
3 System Model Buyer Buyer System HTML/HTTP SOAP/WSDL, not ebMS. UBL/SOAP HTML/HTTP Seller System Seller
System Architecture(1) 4 Buyer System Seller System Web Service Logic Web Service Framework Business Logic DB (Oracle 9.0.1) Data Access Logic Business Component Framework Web Application Logic Data Access Framework Web Application Framework J2EE1.4 RI + JAXB Library
5 System Architecture(2)
6 Issues • Issues implementing UBL; • Application Extendability and Reusability • We like to have application framework which allows both extendability and reusability. • Difference in extension rule for UBL and JAXB • In JAXB, XML Schema “extension” is treated as “extend” of Java. • If UBL extension was implemented as XML Schema “extension”, we could reuse and extend business logic which handles original UBL.