Hi Kristina

Which web service stack are you using?

This may be a jbossws issue, so you might want to also post on the jbossws forums - possibly including an example of the request and response you receive.

Regards

Gary

Hi

Ok we can take a look - however we are in the last stages of doing the release for 2.1.0.Final, so might have to wait until next week.

One thing you could try is that RiftSaw has a pre-requisite of using jbossws-native-3.2.2.GA. Could you try upgrading the web service stack, and see whether this fixes the problem.

You can upgrade the webservice stack during the riftsaw installation, by using the -Dws.version=3.2.2.GA option, e.g.:

ant deploy -Ddatabase=hsql -Dws.version=3.2.2.GA.

Once this is done, it may also be best to re-generate the client classes.

Regards

Gary

Hi Kristina

Had a quick look at your example, and noticed that the response message does not appear to be correct:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <getOrgDetailsResponse xmlns="http://processes/invokes/orgs">
         <tns:return xmlns:tns="http://processes/invokes/orgs">
            <addressId xmlns="">2</addressId>
            <countries xmlns="">Отечественная страна</countries>
            <country xmlns="">Россия</country>
            <countryId xmlns="">149</countryId>
            <dept xmlns="">Росрыболовство</dept>
            <deptId xmlns="">114</deptId>
            <org1 xmlns="">Росрыболовство</org1>
            <org2 xmlns="">АтлантНИРО</org2>
            <org3 xmlns=""></org3>
            <orgBirthday xmlns="">1949-01-01</orgBirthday>
            <orgDeathdate xmlns=""/>
            <orgId xmlns="">2</orgId>
            <orgId1 xmlns="">114</orgId1>
            <orgId2 xmlns="">2</orgId2>
            <orgId3 xmlns="">2</orgId3>
            <orgNameEng xmlns="">Atlantic Research Institute of Marine Fisheries and Oceanography Rosrybolovstvo</orgNameEng>
            <orgNameRus xmlns="">Атлантический научно-исследовательский институт рыбного хозяйства и океанографии</orgNameRus>
            <orgOccupation xmlns="">Гидробиологические, ихтиологические и океанографические наблюдения и исследования в Атлантическом
океане. Обеспечение пользователей рыбопромысловыми прогнозами по районам промысла в Атлантическом
океане, Южной части Балтийского моря, Куршском и Вислинском заливах Балтийского моря.</orgOccupation>
            <orgShortNameEng xmlns="">AtlRIFO</orgShortNameEng>
            <orgShortNameRus xmlns="">АтлантНИРО</orgShortNameRus>
            <orgs xmlns="">2</orgs>
            <orgtype xmlns="">НИИ,конструкторские бюро,научно-производ</orgtype>
            <orgtypeId xmlns="">3</orgtypeId>
         </tns:return>
      </getOrgDetailsResponse>
   </env:Body>
</env:Envelope>

The problem is that the default namespace on the lowest level elements are all blank. Looks like this is occurring during the ODE assignment.

Can you raise a bug in jira for this, attaching your example.

As a workaround, the only thing I can suggest is to simply pass the message through from the external service back to the client - although this requires the message types to be the same (which I guess is not currently possible due to the wsdl import issue?).

You might want to try moving the common message type into a separate wsdl, and import it from both of the other wsdls - but not the BPEL process.

Regards

Gary

Hi

Thats good news.

Yes, if you could create a jira still, attaching your original project - as there appears to be some issue with the ODE assignment implementation removing the namespace of the lowest level elements.

Regards

Gary