Application Composer Series: Custom Object Web Services Dynamic XSD's

Extending from our recent Introduction To Custom Object Webservices post, we've seen a few questions around how to get the WDSL and current XSD files for using web services when interacting with customizations. The answer is actually rather simple, however it is worth explicitly explaining.

All WDSL files remain static, except between upgrades when a changed version may be released. Oracle Enterprise Repository (OER) lists all records  by release number, providing the details of each web service operation and the related data objects.

For XSD files, new custom fields added to your standard objects that extend the object definition means the XSD gets automatically regenerated upon request. This is illustrated in the embedded video below from our YouTube channel.


For any new custom objects created you will use the standard interface of the [ObjectName]CustomObjectService, as explained and listed out (for Release 8) here. For any new fields added to these custom objects again the XSD's are dynamically regenerated upon request, thereby always reflecting the very latest definition.

Obviously being this flexible to support customization also requires effective management and control, to ensure the rapid implementation of changes does not affect any existing integrations. For more detail use the links provided, review our integration blog posts, or consult the product documentation.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Follow us on twitter Fusion Applications Extensibility, Customizations and Integration forum Fusion Applications Dev Relations YouTube Channel
This blog offers news, tips and information for developers building extensions, customizations and integrations for Oracle Fusion Applications.

Search

Categories
Archives
« September 2015
SunMonTueWedThuFriSat
  1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today