FRIDAY, NOVEMBER 21, 2008




MY ACCOUNT LOGIN

LOGIN NAME:

PASSWORD:

REGISTER TODAY!
FORGOT YOUR PASSWORD?
SOA CONSULTING SERVICES
ASSISTING COMPANIES ACHIEVE THEIR SOA GOALS

WEB SERVICES

XWEBEMAILVALIDATION [tool]

XWEB1003 [real estate]

XWEBACHDIRECTORY [financial]

XWEBCHECKOUT [ecommerce]

XWEBTD [ecommerce]

XWEBNEWS [content mgmt.]


SUCCESS STORIES

SOA Portal - SOAHub.com

SOA information portal dedicated to the advancement of Service Oriented Architecture (SOA):


Enterprise Architecture - guides, white papers, case studies


SOA Consulting Services


Web Services Directory


SOA Services / Service Providers Directory


SOA Solutions / Solution Providers Directory


News / Press Releases


Online Forum (Message Boards)


Job Opportunities

browse portal




Web Services, SOA Solutions, SOA Services - XWebServices.com


HOME

WEB SERVICES

SOA SOLUTIONS

SOA SERVICES

ABOUT US





FEATURED WEB SERVICE



XWebEmailValidation
XML/SOAP based Web Service which provides real time Email address validation for client applications.






SEARCH









HOME  ::  NEWS  ::  ARCHIVE  ::  APR 2008

:: Web Services and SOA News ::

SOA's role in centralized data dictionary for messages in WSDLs

What is a centralized data dictionary for messages in WSDLs? Is it a good idea to have an enterprise data dictionary or is it defeating the whole notion of SOA?

It's an excellent idea to define standard XML data types and vocabularies to enable better information exchange and process integration within your enterprise. (It definitely does not defeat the whole notion of SOA -- in fact, vocabulary management is a prerequisite to gaining advanced SOA benefits.) As a general rule, WSDL messages should use standard data types whenever possible rather than proliferating redundant, incompatible, and inconsistent ways to represent enterprise data. The actual WSDL message elements, though, are typically unique to a specific service. For example, if you have a service that exposes the operation "getCustomer", you should define WSDL message elements called "getCustomer" and "getCustomerResponse", specifically for this WSDL, but the elements should use corporate standard types, such as "Customer".

read more on SearchSOA

[Tuesday, April 22, 2008]



HOME
WEB SERVICES
SOA SOLUTIONS
SOA SERVICES
MY ACCOUNT
ABOUT US