OSB to SOA suite package not forming correctly

Question

Setup is as follows:
AIX 5.3 on the box, 10 gigs ram, installation of the latest releases of OSB and SOA suite on top of weblogic. I've built out a couple of simple database queries in BPEL based off wsdls, dropped them on to the SOA suite server, used EM to open a test console and plugged in some search data. Search returns successfully.
I then open up OSB's console, create a business service to the endpoint on the soa server, and a proxy based off the same wsdl used in the BPEL construction which I then route to the business service. Both service and proxy are made with basic http for the protocol (not sure how to use the sb protocol, and not sure if that will fix the problem). Load the test console on the proxy service, which displays an xml form similar to what is used in the SOA suite. Fill out the same information, but the invoke returns BEA-380000. Following the invocation trace in OSB everything looks good in terms of package content.
Wondering if it might simply be a problem with how the OSB interprets XML from a wsdl, I piped the XML from the SOA suite into the OSB's xml field, but to no luck, same error. After some more testing and frustration,I put the SOA suite XML straight in to the form field in the OSB test console, and it worked. However, the package itself seems oddly formed, consisting of:
<soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     </soap:Header>
     <soapenv:Body>
     <soap:Envelope      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header/>
Which I've been told is basically double wrapping the package, which shouldn't work, and more importantly wont be generated when someone uses say SOAPUI to access our service on the OSB.
Now, on the SOA suite side of things. In EM console, I navigate to my BPEL process and can see the faults caused by the OSB. The same faults are also generated when binding to the OSB's endpoint with SOAPUI, but not when going directly to the SOA suite's endpoint. The error is the following:
oracle.j2ee.ws.saaj.soap.SOAPVersionMismatchException: Mime Header Content-Type: text/xml requires SOAP envelope namespace: http://schemas.xmlsoap.org/soap/envelope/: Mime Header Content-Type: text/xml requires SOAP envelope namespace: http://schemas.xmlsoap.org/soap/envelope/
And the payload sent shows as empty.
So to my best uneducated guess, it looks like the OSB wraps the payload in an envelope, and then unwraps it before handing it to the SOA suite, which expects the payload to be wrapped. Sadly, I'm still pretty new to the wsdl/webservice/oracle world, so I'm not even sure if that's an accurate representation. Any insight on what might be happening or how to get OSB to talk with SOA suite correctly would be greatly appreciated. Included below are the XML payloads I've used (minus a bit for confidentiality reasons). Apologies if the formatting doesn't work so nice for it.
OSB Generated (fails):
SOAP Header:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
Body:
<ns2:SyncEmployeeIDRequest xmlns:ns="removed" xmlns:ns1="removed" xmlns:ns2="removed">
<!--You have a CHOICE of the next 2 items at this level-->
<ns:PersonIdentificationAssertion>
<!--Optional:-->
<ns1:PersonBirthDate>
<ns1:Date>2008-09-28</ns1:Date>
</ns1:PersonBirthDate>
<!--Optional:-->
<ns1:PersonGivenName>string</ns1:PersonGivenName>
<ns1:PersonSurName>string</ns1:PersonSurName>
</ns:PersonIdentificationAssertion>
<ns1:DepartmentIDText>string</ns1:DepartmentIDText>
</ns2:SyncEmployeeIDRequest>
SOA Generated(works if plugged into OSB form field)
SOAP Header:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header></soap:Header>
     <soap:Body xmlns:ns1="removed">
          <ns1:SyncEmployeeIDRequest xmlns:ns2="removed">
               <ns2:PersonIdentificationAssertion xmlns:ns3="removed">
                    <ns3:PersonBirthDate>
                         <ns3:Date>2008-09-28</ns3:Date>
</ns3:PersonBirthDate>
                    <ns3:PersonGivenName>string</ns3:PersonGivenName>
                    <ns3:PersonSurName>string</ns3:PersonSurName>
</ns2:PersonIdentificationAssertion>
</ns1:SyncEmployeeIDRequest>
</soap:Body>
</soap:Envelope>
Working Request Document in OSB:
<soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     </soap:Header>
     <soapenv:Body>
     <soap:Envelope      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header/>
     <soap:Body      xmlns:ns1="removed">
     <ns1:SyncEmployeeIDRequest      xmlns:ns2="removed">
     <ns2:PersonIdentificationAssertion      xmlns:ns3="removed">
     <ns3:PersonBirthDate>
     <ns3:Date>2008-09-28</ns3:Date>
     </ns3:PersonBirthDate>
     <ns3:PersonGivenName/>
     <ns3:PersonSurName>ALastName</ns3:PersonSurName>
     </ns2:PersonIdentificationAssertion>
     </ns1:SyncEmployeeIDRequest>
     </soap:Body>
     </soap:Envelope>
     </soapenv:Body>
     </soapenv:Envelope>
If I can provide anymore information that will help shed light on this issue please let me know.
Thank you for your time.
~Nick

Answer 1

Problem solved. When I originally created my business service inside of OSB, I created it based off an endpoint provided by the SOA server. Instead, I went and did a mass import from a url, pointed it at the SOA server wsdl, and then built the web service off of that wsdl resource in the OSB. Now it works like a charm.