Mittwoch, Juli 13, 2005
WISIF - BPEL Java Binding Error
Within WISIF Java Binding you get properly an compile error for methode binding without paramters (eg. public Boolean ping();) like following:
[Error ORABPEL-10902]: compilation failed [Description]: in "bpel.xml", XML parsing failed because "notification operation not supported.In WSDL at MyService.wsdl", operation "ping" of portType "{http://xmlns.xxx.com/ch/rule/service}RLPortType" is a notification operation (The endpoint sends a message), which is not supported in this version. See chapter 2.4 of WSDL spec 1.1.Make sure the operation is "one-way" type or "request-response" type.". [Potential fix]: n/a.
To solve this problem you must define an message for empty parameters within portType section:
<message name="myPingRequest"> </message>
<message name="myPingResponse">
<part name="pingOutput" type="xsd:boolean"/>
</message>
<portType name="myPortType">
<operation name="ping">
<input name="myPingRequest" message="tns:myPingRequest"/>
<output name="myPingResponse" message="tns:myPingResponse"/>
</operation>
</portType>
[Error ORABPEL-10902]: compilation failed [Description]: in "bpel.xml", XML parsing failed because "notification operation not supported.In WSDL at MyService.wsdl", operation "ping" of portType "{http://xmlns.xxx.com/ch/rule/service}RLPortType" is a notification operation (The endpoint sends a message), which is not supported in this version. See chapter 2.4 of WSDL spec 1.1.Make sure the operation is "one-way" type or "request-response" type.". [Potential fix]: n/a.
To solve this problem you must define an message for empty parameters within portType section:
<message name="myPingRequest"> </message>
<message name="myPingResponse">
<part name="pingOutput" type="xsd:boolean"/>
</message>
<portType name="myPortType">
<operation name="ping">
<input name="myPingRequest" message="tns:myPingRequest"/>
<output name="myPingResponse" message="tns:myPingResponse"/>
</operation>
</portType>
Donnerstag, Juli 07, 2005
Oracle Business Rule Engine - JSR 94
Oracle offers a new Java based rule engine based on the JSR-94. Last view days I have the chance to test the rule enigin within an BPEL project to solve dynamic and high performance object manipulation requirements.
Now I'm very inspired about the performance and the ease of use. The main reason of this is the established Rule syntax like Java programming language. and the possiblility to mix Java objects and Java code with Rule RL without restrictions. This make it easy to integrate rules in Java code and manipulate or make dessisions depending of the current program status.
However, the web based rule author is currently in beta status and not realy usfull for complex rules. So I recommend to write your rule in the RL-Syntax and load the rules from file instead repository usage. This means you can omit the rule generation call java methode ruleSession.generateRL( props ) from the XML-Repository. Instead this use simple file loading of your own RL-Syntax file.
Now, have fun with Oracle Business Rules!
Now I'm very inspired about the performance and the ease of use. The main reason of this is the established Rule syntax like Java programming language. and the possiblility to mix Java objects and Java code with Rule RL without restrictions. This make it easy to integrate rules in Java code and manipulate or make dessisions depending of the current program status.
However, the web based rule author is currently in beta status and not realy usfull for complex rules. So I recommend to write your rule in the RL-Syntax and load the rules from file instead repository usage. This means you can omit the rule generation call java methode ruleSession.generateRL( props ) from the XML-Repository. Instead this use simple file loading of your own RL-Syntax file.
Now, have fun with Oracle Business Rules!
