At a minimum, you'll need to have WSDL that describes the services that you want to invoke or receive messages on. If you deploy ODE to ServiceMix, then it would be possible to bind the partner links to POJO's or other components. For example, setup a camel route that polls a directory and sends the contents of an xml file into your BPEL process whenever a file appears.
If you want to explicitly model the interaction with a database or file system within your BPEL then you'll need to look at vendors like Oracle that have implemented custom activities for file and db access. However, keep in mind that BPEL works with the abstract interfaces defined by WSDL so it's best to think of everything as a service since once you start down the path of modeling interactions with concrete bindings like SQL queries or inline Java code then you're making your orchestration dependent on these bindings and more prone to break when things change. It also locks you into the customizations provided by the vendor. A better approach is to keep at the abstract level and encapsulate everything with interfaces - even if it's just a thin wrapper around a file system or db. On 7/21/09 10:48 AM, "kodeninja" <[email protected]> wrote: So what you're saying, Nelson, is that if something like this is required, it also has to be exposed as a web service and that there's no other way? Nelson Andrés Alvarez Salcedo wrote: > > El 21/07/2009 9:30, kodeninja escribió: >> Howdy, >> >> If I want to read/write some stuff from/to a DB/File from within a BPEL >> process, should that also be exposed as web service to my process, or is >> there a way to write, say, some custom Java code that can talk directly >> to >> concerned entity? I'm trying to find out what kind customizations/hooks a >> BPEL supports? >> >> When I search for this stuff online, most of the links returned are from >> Oracle, where they talk about writing Adapters for achieving the above. >> Are >> adapters some standard BPEL stuff? >> >> Thanks, >> -Kodeninja >> >> >> > You should consider the elements you manage in the BPEL process as > *basic services*. Following this point of view, a BPEL process should > only interact with exposed services and it was, as far as i know, > designed to work that way. BPEL orchestrates (tells everyone what to do > and when to do it, even integrating human tasks into the process) and > its XML speech means that it talks to services through XML messages. > > Hope I make myself clear while trying to be helpful. > -- > Nelson Álvarez Salcedo > /"Verba volant, scripta manent"/ > > -- View this message in context: http://www.nabble.com/Reading-from-a-DB-File-in-a-BPEL-process-tp24588737p24589123.html Sent from the Apache Ode User mailing list archive at Nabble.com. -- Mark Ford MIT Lincoln Laboratory 244 Wood Street Lexington MA 02420 (781) 981-1843
