In this case, the file binding component
would be initially responsible for reading an input message from the file system.
After any JBI processing has occurred, the file binding component would then write
out the results of the process to a file.
Binding Components
[ 56 ]
Within the NetBeans Enterprise Pack, the entire set of properties for the file binding
component can be edited within the Properties window. The properties for the
binding component are displayed when either the input or output messages are
selected from the WSDL in a composite application as shown in the following
figure. (Don't worry if you don't understand the WSDL editor and its role in SOA
applications yet. In Chapter 6 we'll describe the WSDL editor in depth. Then in
Chapter 10, we'll bring all of the SOA concepts learned together, and describe how to
use them to build a complete business application.)
The entire set of properties that are configurable for an instance of a file binding
component is shown in the next screenshot. You probably won't need all of
the properties within your applications, so we've described some common
properties that you will probably need to access in applications where you use file
binding components.
fileName: Specifies the input or output filename (depending on whether
the binding component is acting as a consumer or a provider).
Pages:
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69