[
https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932472#action_12932472
]
Oliver Schwerk commented on AXIS2-4755:
---------------------------------------
Is there any workaround for this? I have the same problem, even if the first
invocation is finished. Does it help if I use the same ServiceClient object
instead of creating a new one?
BTW, the name has to match the operation name in the WSDL, right? So I need to
have the same service name for each invocation.
Any help appreciated!
Thanks,
Oliver Schwerk
flexis AG
Schockenriedstraße 46
D-70565 Stuttgart
Telefon: +49 (711) 78 23 80 - 0
Telefax: +49 (711) 78 23 80 - 78
E-Mail: [email protected]
www.flexis.de
--------------------------
flexis AG
Handelsregister Stuttgart, HRB 21229
Vorstand: Philipp Beisswenger (Vorsitzender), Benno Ziller, Oliver Reisch
Vorsitzender des Aufsichtsrats: Dr. Rolf Aschermann
> dynamic serviceclient: axisservice-names are not unique
> -------------------------------------------------------
>
> Key: AXIS2-4755
> URL: https://issues.apache.org/jira/browse/AXIS2-4755
> Project: Axis2
> Issue Type: Bug
> Components: client-api, deployment
> Affects Versions: 1.5.1
> Reporter: gerhard presser
>
> in case of concurrent invocations, this may cause problems, because one
> client cleans up the other-clients context etc.
> both, anonservices and stub-services generate a unique service name; dynamic
> service-clients should do so too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
