[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Assigning the Value of the Service-Ref Element
Hi, Andrew, I saw two emails asking about how to make use of service-ref element in BPEL. Particularly how to compile-time checking. Hopefully, this email will be able to answer the questions in your two emails. Let's spilt the situation in multiple parts:
I hope I have answered your questions. :-) (And, not confusing u ...) Thanks! Regards, Alex Yiu andrew.francis@mail.mcgill.ca wrote: Hello: I would like to soon implement section Nine (variables, expressions, and assignment) of the BPEL4WS specification. I am trying to figure out how to implement partnerLinks, keeping issue 34 and 152 in mind. I am trying to figure out the machinery for service-ref. I have a question: how are the values for the service-ref element and more specifically, the reference-schema acquired? Since service-element is partner specific and one binds this partner specific information essentially at runtime (you pick an actual port/end-point), it seems to me that service-ref is difficult to use for compile time checking. For example, how to I figure out if a variable or variable property's type agree with a partnerlink's EPR, if I can only really only know this at runtime? At best I can only do a runtime type checking for what the specification calls "undefined behaviour." It also seems to me that this information is difficult to acquire a priori. Is my compiler/BPEL tool looking at a WSDL or a UDDI tModel? Do I really need all this machinery to invoke say Amazon's, Google's, or most currently existing web services? I am interested to hear how others are approaching this problem. Cheers, Andrew To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php. |
<?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" targetNamespace="http://foo.com" xmlns:foo="http://foo.com" xmlns:bpws="http://schemas.xmlsoap.org/ws/2004/03/business-process/"> <xs:import namespace="http://schemas.xmlsoap.org/ws/2004/03/business-process/" schemaLocation="C:\my_data\work\wso\bpel\spec\cvs_home\specifications\SchemaFiles\wsbpel_main.xsd"/> <xs:complexType name="BarServiceRefType"> <xs:complexContent> <xs:restriction base="bpws:ServiceRefType"> <xs:sequence> <xs:element ref="foo:barAddr"/> </xs:sequence> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:element name="barWrapper" type="foo:BarServiceRefType"/> <xs:element name="barAddr" type="xs:string" /> </xs:schema>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]