« Return to Thread: Another Dynamic Partner Link Question

Re: Another Dynamic Partner Link Question

by Nikita Krjukov :: Rate this Message:

Hi Marcus.

Maybe Murali will give you some more information. But I suppose he meant
that the service-name should be prefixed
because it is an entity declared in a WSDL file. I think you should have
such file somewhere in your project.
In XML world it is common to identify anything not only with a simple
name, but rather with a QName.
It consists from namespace and local name and also the namespace usually
replaced with a prefix.
The prefix usually declared in the root element of document. And it
seems your prefix already declared
xmlns:ns="http://10.152.0.204:5080/portal2/componentes/Teste.jws?wsdl"
The only strange is that the ? sign is in the file name ".jws?wsdl"
I think it has to be "http://10.152.0.204/portal2/componentes/Teste.jws"
as declared in your
\src\10.152.0.204_5080\portal2\componentes\Teste.jws.wsdl
I've found the TesteService is declared there.

Also the WSDL should be imported to the BPEL to be visible. Though maybe
it isn't required in you case.
But you can try importing. It shouldn't heart anything.

And you should use the prefix. In your case it seems it is "ns":

<wsa:ServiceName PortName="Teste">
ns:TesteService
</wsa:ServiceName>

Nikita

Marcus Milanez wrote:

> Hi Murali,
>
> Thank you very much for your response. How exactly can I a qualify a service
> name? I tried a lot of things but none of them worked!
>
> yours,
>
> Marcus
>
>
> Murali Pottlapelli wrote:
>
>> Hi Marcus,
>>
>> <wsa:ServiceName PortName="Teste">
>> TesteService
>> </wsa:ServiceName>
>>
>> Service name "TesteService" name needs to be qualified. Add a prefix to
>> "TesteService" and declare NS/prefix in ServiceName element.
>>
>> Regards
>> Murali
>>
>> Marcus Milanez wrote:
>>
>>> Hello everyone,
>>>
>>> I'm trying to develop a simple BPEL process which can invoke web services
>>> dynamically. To simulate the scenario, I've created an axis web service
>>> and
>>> published it in two different servers, in the very same address. The
>>> server
>>> IPs are different, but the web services are identical. I've also created
>>> a
>>> very simple BPEL proccess to invoke one of the published services, and it
>>> worked the way it should.
>>>
>>> What I would like to do now is dynamically change the target server
>>> address,
>>> using Dynamic Partner Links, but I keep on getting 'unable to resolve the
>>> service endpoint dynamically' all the time.
>>>
>>> Is it possible to solve the described situation? Below is the code
>>> snippet
>>> where I'm trying to change the partner link target address:
>>>
>>> <assign name="AssignPartnerLink">
>>>
>>> <copy>
>>>
>>> <from>
>>>
>>> <literal>
>>>
>>> <sref:service-ref>
>>>
>>> <wsa:EndpointReference>
>>> 
>>> <wsa:Address>
>>>
>>>
>>> http://10.152.21.38:5080/portal2/componentes/Teste.jws
>>>
>>> </wsa:Address>
>>>
>>> <wsa:ServiceName
>>> PortName="Teste">
>>>
>>> TesteService
>>>
>>> </wsa:ServiceName>
>>>
>>> </wsa:EndpointReference>
>>>
>>> </sref:service-ref>
>>>
>>> </literal>
>>>
>>> </from>
>>>
>>> <to partnerLink="PartnerLinkServico"/>
>>>
>>> </copy>
>>>
>>> </assign>
>>>
>>>
>>> Also, attached to this message is my full project including the AXIS web
>>> service, which is quite simple. Can anybody please help me with that? I
>>> think I'm stuck in that for 3 days now...
>>>
>>> Thank you all in advance for your attention!
>>>
>>> http://www.nabble.com/file/p20346846/project-bpel.zip project-bpel.zip
>>> http://www.nabble.com/file/p20346846/AxisWSTeste.zip AxisWSTeste.zip
>>>
>>>
>>
>
>

« Return to Thread: Another Dynamic Partner Link Question