I'm continuing to have problem into BPEL import Wizard. I have made a simple
orchestration that invokes a web service with simple methods, invoking a
simple hello method from my orchestration. I have exported it such as BPEL
and I have tried to import it another project using the BPEL import Wizard.
The import fails with the subsequent errors code:

-    error: B1030: 'input': part not found in message
'http://test.BPEL.import_1/WS#HelloSoapIn'. Referenced by to 'element'.
-    error: B1030: 'HelloResult': part not found in message
'http://test.BPEL.import_1/WS#HelloSoapOut'. Referenced by from 'element'.

The partner wsdl is generated automatically invoking IIS and it seems to be
correctly.
Where can I find some explanation on how to solve this problem and find some
information on this error code?

I attach the wsdl and BPEL of the orchestration and the wsdl partner.
Thanks.

--
Aniello

[ Post a follow-up to this message ]

Hi

So you want to take a orchestration and put it into another project?

There are two other ways to do this than exporting and importing.

1. Just include the file in the other BizTalk project. "Add existing
item" and point it out from the old BizTalk project directory

2. In your new BizTalk project, add a reference to the old project.
Then you can use the orchestration - but not change it.

Jan Eliasen

On Tue, 22 Jun 2004 13:00:59 +0200, "Aniello" <aniello> wrote:

>I'm continuing to have problem into BPEL import Wizard. I have made a simpl
e
>orchestration that invokes a web service with simple methods, invoking a
>simple hello method from my orchestration. I have exported it such as BPEL
>and I have tried to import it another project using the BPEL import Wizard.
>The import fails with the subsequent errors code:
>
>-    error: B1030: 'input': part not found in message
>'http://test.BPEL.import_1/WS#HelloSoapIn'. Referenced by to 'element'.
>-    error: B1030: 'HelloResult': part not found in message
>'http://test.BPEL.import_1/WS#HelloSoapOut'. Referenced by from 'element'.
>
>The partner wsdl is generated automatically invoking IIS and it seems to be
>correctly.
>Where can I find some explanation on how to solve this problem and find som
e
>information on this error code?
>
>I attach the wsdl and BPEL of the orchestration and the wsdl partner.
>Thanks.

--
Jan Eliasen, representing himself and not the company he works for.

[ Post a follow-up to this message ]

Hi Jan,
I don't want to add simple a bpel file into the project, but I want create a
new project in BizTalk using the bpel, xsd, wsdl of the orchestration and
wsdl of partner link. It's different, in fact BizTalk allow this. I have
tested the export and import only to verify that the import wizard works
well, but it seems that I have some problems.
Thanks.

"Jan Eliasen" <spam@eliasen.dk> ha scritto nel messaggio
 news:toaid0hgip7p5hf0hh9avkltqtjfulob9u@
4ax.com...
> Hi
>
> So you want to take a orchestration and put it into another project?
>
> There are two other ways to do this than exporting and importing.
>
> 1. Just include the file in the other BizTalk project. "Add existing
> item" and point it out from the old BizTalk project directory
>
> 2. In your new BizTalk project, add a reference to the old project.
> Then you can use the orchestration - but not change it.
>
> Jan Eliasen
>
> On Tue, 22 Jun 2004 13:00:59 +0200, "Aniello" <aniello> wrote:
> 
simple[vbcol=seagreen] 
BPEL[vbcol=seagreen] 
Wizard.[vbcol=seagreen] 
'element'.[vbcol=seagreen] 
be[vbcol=seagreen] 
some[vbcol=seagreen] 
>
> --
> Jan Eliasen, representing himself and not the company he works for.

[ Post a follow-up to this message ]