Alex, DOH! I was still using BPEL 1.1 syntax. Thanks for your time! -Doug.
-----Original Message----- From: Alex Boisvert [mailto:[email protected]] Sent: Tuesday, January 06, 2009 4:32 PM To: [email protected] Subject: Re: Catch error message Hi Douglas, The catch activity syntax is: <catch faultName="QName"? faultVariable="BPELVariableName"? ( faultMessageType="QName" | faultElement="QName" )? >* activity </catch> so you are missing either the faultMessageType or the faultElement attribute. BTW, the "name" attribute should be a ncname (not a qname), and the variable does not need to be defined earlier. It's defined in the catch itself. alex On Tue, Jan 6, 2009 at 1:04 PM, Jackson, Douglas < [email protected]> wrote: > Hi! > The following message does not look right to me. Does it have something to > do with a mismatch between the name and the variable? > > The namespace prefixes are declared, and other parts of the wsdl work fine > (i.e. the invoke related to the catch). > > The error makes me think that a messageType or elementType variable is > required and I have that... > > -Doug. > > > > org.apache.ode.bpel.iapi.ContextException: Deploy failed; error: > [CompilationErrors] Compilation completed with 1 error(s): > null:626: error: [VariableDeclMissingType] Declaration of variable > "abort-fault-msg" does not specify the required type (either MessageType or > ElementType). > > > Here is the offending line: > > <catch name="fault:XSException" faultVariable="abort-fault-msg"> > > Here are the decls: > > <variable name="abort-fault-msg" > messageType="abortws:abort-fault-msg"/> > > From abortws: > <wsdl:message name="abort-fault-msg"> > <wsdl:part name="abort-fault-part" element="fault:XSException"/> > </wsdl:message> > > From fault: > <xsd:element name="XSException" type="fault:exception-type"/> > > >
