You are viewing a plain text version of this content. The canonical link for it is here.
Posted to savan-dev@ws.apache.org by "gerhard presser (JIRA)" <ji...@apache.org> on 2010/06/28 13:42:51 UTC
[jira] Created: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
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
Fix For: 1.6, 1.5.2
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "gerhard presser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889775#action_12889775 ]
gerhard presser commented on AXIS2-4755:
----------------------------------------
I think the name does matter!
for example, multiple hashmaps for caching various contextes/axisservicegroups etc. use the service(group)-name as key, so if there are multiple services with the same name, IMO, this can't work at all.
in my case i have a shared axis-configuration and multiple parallel invocations of the same service (but not the same serviceclient-instance)
while(true) {
new Thread(new Runnable() {
ServiceClient client = new ServiceClient(ConfigurationContext, Definition, QName, String);
try {
client.sendReceive(QName, OMElement);
} finally {
client.cleanup();
}
}).start();
}
having the same servicename causes following NPE:
java.lang.NullPointerException
at org.apache.axis2.context.ServiceGroupContext.getServiceContext(ServiceGroupContext.java:141)
at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:184)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:220)
at com.groiss.test.LoadTester$1.run(LoadTester.java:46)
at java.lang.Thread.run(Unknown Source)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-4755:
-----------------------------------
Fix Version/s: (was: 1.6)
(was: 1.5.2)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-4755:
-----------------------------------
Fix Version/s: (was: 1.6)
(was: 1.5.2)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889691#action_12889691 ]
Deepal Jayasinghe commented on AXIS2-4755:
------------------------------------------
Could you please elaborate more about this issues? anyway if I understand your question correctly, then the answer is the name of the service created at the client side does not really matter.
Deepal
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "gerhard presser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889775#action_12889775 ]
gerhard presser commented on AXIS2-4755:
----------------------------------------
I think the name does matter!
for example, multiple hashmaps for caching various contextes/axisservicegroups etc. use the service(group)-name as key, so if there are multiple services with the same name, IMO, this can't work at all.
in my case i have a shared axis-configuration and multiple parallel invocations of the same service (but not the same serviceclient-instance)
while(true) {
new Thread(new Runnable() {
ServiceClient client = new ServiceClient(ConfigurationContext, Definition, QName, String);
try {
client.sendReceive(QName, OMElement);
} finally {
client.cleanup();
}
}).start();
}
having the same servicename causes following NPE:
java.lang.NullPointerException
at org.apache.axis2.context.ServiceGroupContext.getServiceContext(ServiceGroupContext.java:141)
at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:184)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:220)
at com.groiss.test.LoadTester$1.run(LoadTester.java:46)
at java.lang.Thread.run(Unknown Source)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889691#action_12889691 ]
Deepal Jayasinghe commented on AXIS2-4755:
------------------------------------------
Could you please elaborate more about this issues? anyway if I understand your question correctly, then the answer is the name of the service created at the client side does not really matter.
Deepal
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889691#action_12889691 ]
Deepal Jayasinghe commented on AXIS2-4755:
------------------------------------------
Could you please elaborate more about this issues? anyway if I understand your question correctly, then the answer is the name of the service created at the client side does not really matter.
Deepal
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-4755:
-----------------------------------
Fix Version/s: (was: 1.6)
(was: 1.5.2)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "gerhard presser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889775#action_12889775 ]
gerhard presser commented on AXIS2-4755:
----------------------------------------
I think the name does matter!
for example, multiple hashmaps for caching various contextes/axisservicegroups etc. use the service(group)-name as key, so if there are multiple services with the same name, IMO, this can't work at all.
in my case i have a shared axis-configuration and multiple parallel invocations of the same service (but not the same serviceclient-instance)
while(true) {
new Thread(new Runnable() {
ServiceClient client = new ServiceClient(ConfigurationContext, Definition, QName, String);
try {
client.sendReceive(QName, OMElement);
} finally {
client.cleanup();
}
}).start();
}
having the same servicename causes following NPE:
java.lang.NullPointerException
at org.apache.axis2.context.ServiceGroupContext.getServiceContext(ServiceGroupContext.java:141)
at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:184)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:220)
at com.groiss.test.LoadTester$1.run(LoadTester.java:46)
at java.lang.Thread.run(Unknown Source)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-4755:
-----------------------------------
Fix Version/s: (was: 1.6)
(was: 1.5.2)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889691#action_12889691 ]
Deepal Jayasinghe commented on AXIS2-4755:
------------------------------------------
Could you please elaborate more about this issues? anyway if I understand your question correctly, then the answer is the name of the service created at the client side does not really matter.
Deepal
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "gerhard presser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889775#action_12889775 ]
gerhard presser commented on AXIS2-4755:
----------------------------------------
I think the name does matter!
for example, multiple hashmaps for caching various contextes/axisservicegroups etc. use the service(group)-name as key, so if there are multiple services with the same name, IMO, this can't work at all.
in my case i have a shared axis-configuration and multiple parallel invocations of the same service (but not the same serviceclient-instance)
while(true) {
new Thread(new Runnable() {
ServiceClient client = new ServiceClient(ConfigurationContext, Definition, QName, String);
try {
client.sendReceive(QName, OMElement);
} finally {
client.cleanup();
}
}).start();
}
having the same servicename causes following NPE:
java.lang.NullPointerException
at org.apache.axis2.context.ServiceGroupContext.getServiceContext(ServiceGroupContext.java:141)
at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:184)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:220)
at com.groiss.test.LoadTester$1.run(LoadTester.java:46)
at java.lang.Thread.run(Unknown Source)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-4755:
-----------------------------------
Fix Version/s: (was: 1.6)
(was: 1.5.2)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "gerhard presser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889775#action_12889775 ]
gerhard presser commented on AXIS2-4755:
----------------------------------------
I think the name does matter!
for example, multiple hashmaps for caching various contextes/axisservicegroups etc. use the service(group)-name as key, so if there are multiple services with the same name, IMO, this can't work at all.
in my case i have a shared axis-configuration and multiple parallel invocations of the same service (but not the same serviceclient-instance)
while(true) {
new Thread(new Runnable() {
ServiceClient client = new ServiceClient(ConfigurationContext, Definition, QName, String);
try {
client.sendReceive(QName, OMElement);
} finally {
client.cleanup();
}
}).start();
}
having the same servicename causes following NPE:
java.lang.NullPointerException
at org.apache.axis2.context.ServiceGroupContext.getServiceContext(ServiceGroupContext.java:141)
at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:184)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:220)
at com.groiss.test.LoadTester$1.run(LoadTester.java:46)
at java.lang.Thread.run(Unknown Source)
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4755) dynamic serviceclient:
axisservice-names are not unique
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889691#action_12889691 ]
Deepal Jayasinghe commented on AXIS2-4755:
------------------------------------------
Could you please elaborate more about this issues? anyway if I understand your question correctly, then the answer is the name of the service created at the client side does not really matter.
Deepal
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org