Does BPEL allow partnerlinks where the WSDL has more than one namespace

Question

Hi
I have a WSDL where the schema is in a different namespace than the message types. BPEL Designer throws "Exception: Problem building schema" when accessing the variable in the "Assign" activity. Can someone point out if there is a problem with my WSDL file ?
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="ProvWithXSL"
targetNamespace="http://xmlns.oracle.com/ProvWithXSL"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/ProvWithXSL"
xmlns:tns="http://www.example.org"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
     <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     TYPE DEFINITION - List of services participating in this BPEL process
     The default output of the BPEL designer uses strings as input and
     output to the BPEL Process. But you can define or import any XML
     Schema type and us them as part of the message types.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
     <types>
          <schema attributeFormDefault="qualified"
               elementFormDefault="qualified"
targetNamespace="http://www.example.org"
xmlns:tns="http://www.example.org">
               xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="EventHdr">
<sequence>
<element name="eventType" type="string"/>
<element name="eventID" type="string"/>
<element name="eventSrc" type="string"/>
<element name="objectDN" type="string"/>
<element name="profileID" type="string"/>
</sequence>
</complexType>
<complexType name="Attribute">
<sequence>
<element name="attrname" type="string"/>
<element name="attrval" type="string" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="EventAttrs">
<sequence>
<element name="attr" type="tns:Attribute" maxOccurs="unbounded"/>
</sequence>
</complexType>
<element name="event">
<complexType>
<sequence>
<element name="hdr" type="tns:EventHdr"/>
<element name="attrs" type="tns:EventAttrs"/>
</sequence>
</complexType>
</element>
<element name="ProvWithXSLProcessRequest">
          <complexType>
               <sequence>
                    <element name="parameters" type="string"/>
               </sequence>
          </complexType>
     </element>
     <element name="ProvWithXSLProcessResponse">
          <complexType>
               <sequence>
                    <element name="result" type="string"/>
               </sequence>
          </complexType>
     </element>
</schema>
</types>
     <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     MESSAGE TYPE DEFINITION - Definition of the message types used as
     part of the port type defintions
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
     <message name="ProvWithXSLRequestMessage">
          <!--<part name="payload" element="tns:event"/>-->
<part name="payload" element="tns:ProvWithXSLProcessRequest"/>
     </message>
     <message name="ProvWithXSLResponseMessage">
          <part name="payload" element="tns:ProvWithXSLProcessResponse"/>
     </message>
     <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PORT TYPE DEFINITION - A port type groups a set of operations into
     a logical service unit.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
     <!-- portType implemented by the ProvWithXSL BPEL process -->
     <portType name="ProvWithXSL">
          <operation name="initiate">
               <input message="client:ProvWithXSLRequestMessage"/>
          </operation>
     </portType>
     <!-- portType implemented by the requester of ProvWithXSL BPEL process
     for asynchronous callback purposes
     -->
     <portType name="ProvWithXSLCallback">
          <operation name="onResult">
               <input message="client:ProvWithXSLResponseMessage"/>
          </operation>
     </portType>
     <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PARTNER LINK TYPE DEFINITION
     the ProvWithXSL partnerLinkType binds the provider and
     requester portType into an asynchronous conversation.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
     <plnk:partnerLinkType name="ProvWithXSL">
          <plnk:role name="ProvWithXSLProvider">
               <plnk:portType name="client:ProvWithXSL"/>
          </plnk:role>
          <plnk:role name="ProvWithXSLRequester">
               <plnk:portType name="client:ProvWithXSLCallback"/>
          </plnk:role>
     </plnk:partnerLinkType>
</definitions>

Answer 1

You can use more than one namespace (done so before), and several ways to do so.
But first, there's one error in your schema definition:
<schema attributeFormDefault="qualified"
elementFormDefault="qualified"
targetNamespace="http://www.example.org"
xmlns:tns="http://www.example.org">
xmlns="http://www.w3.org/2001/XMLSchema">
remove the ">" after xmlns:tns. Btw, this will cause the exception to occur as well.
Why not put your elements in a new schema, like below, and leave the original ports & messages intact, as you don't change anything in it from the original generation. Just add this schema above/below the schema for the messages and it will work just fine.
hth,
Mike
So, you will have a wsdl that looks like:
<schema attributeFormDefault="qualified"
elementFormDefault="qualified"
targetNamespace="http://www.example.org"
xmlns:tns="http://www.example.org"
xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="EventHdr">
<sequence>
<element name="eventType" type="string"/>
<element name="eventID" type="string"/>
<element name="eventSrc" type="string"/>
<element name="objectDN" type="string"/>
<element name="profileID" type="string"/>
</sequence>
</complexType>
<complexType name="Attribute">
<sequence>
<element name="attrname" type="string"/>
<element name="attrval" type="string" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="EventAttrs">
<sequence>
<element name="attr" type="tns:Attribute" maxOccurs="unbounded"/>
</sequence>
</complexType>
<element name="event">
<complexType>
<sequence>
<element name="hdr" type="tns:EventHdr"/>
<element name="attrs" type="tns:EventAttrs"/>
</sequence>
</complexType>
</element>
</schema>     
<schema attributeFormDefault="qualified"
elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/ProvWithXSL"
xmlns:tns="http://www.example.org"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="ProvWithXSLProcessRequest">
<complexType>
<sequence>
<element name="parameters" type="string"/>
</sequence>
</complexType>
</element>
<element name="ProvWithXSLProcessResponse">
<complexType>
<sequence>
<element name="result" type="string"/>
</sequence>
</complexType>
</element>
</schema>