[
https://issues.apache.org/jira/browse/ODE-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900202#comment-13900202
]
Sathwik Bantwal Premakumar commented on ODE-1013:
-------------------------------------------------
ODE axis2 layer has a ConfigurationContext with correct context path. When the
ServiceClient is created for invocation of an external service, another
ConfigurationContext object is created and associated with the ServiceClient
which actually changes the information within AxisConfiguration with respect to
the TransportListener and hence all the WSDL documents endup with no context
path in the service endpoints.
There are 2 approaches to solve this issue.
1) Use the same ConfigurationContext object which was created within ODE axis2
Layer while creating the ServiceClients.
2) Use separate axis2 configuration xml files, one for ODE axis2 integration
layer responsible for creating Services representing the processes and another
configuration for the generation of clients (ServiceClient) for invocation of
external services.
> Missing context information in Service Endpoint in auto generated WSDL from
> Axis2
> ---------------------------------------------------------------------------------
>
> Key: ODE-1013
> URL: https://issues.apache.org/jira/browse/ODE-1013
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 1.3.6
> Reporter: Sathwik Bantwal Premakumar
> Assignee: Sathwik Bantwal Premakumar
> Fix For: 1.3.7, 1.4
>
>
> It has been reported that when the process has an external service call, and
> after the execution of the process instance the wsdl service endpoint loses
> the context information.
> Before the execution of the Process Instance the endpoint in the auto
> generated WSDL by axis2 looks like below:
> http://localhost:8080/ode/processes/HelloWorld.HelloWorldPort/
> After the execution of the process instance the endpoint looks like below:
> http://localhost:8080//HelloWorld.HelloWorldPort/
> This behaviour is seen across all deployed process services.
> Forum reporting:
> http://markmail.org/message/m4awoofvdz7nuael?q=problem+with+endpoint+in+Ode+1%2E3%2E6
> http://markmail.org/message/f7lwan3skhkzmbyu?q=404+error+of+BPEL+WebService+at+the+second+run
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
