[ 
https://issues.apache.org/jira/browse/AXIS2-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509067
 ] 

Amila Chinthaka Suriarachchi commented on AXIS2-2860:
-----------------------------------------------------

I'll put synchronization part for sake. but that may not realy necessary in 
this case. because what we want is to getunique set of prefixes for one thread.

if we keep one object per thread this could create a memory increase and have 
to parse this object among each ADB generated class. So the implemented way is 
a much simpler solution.

On the otherhand we can parse an int to serialize method and an use it to 
generate prefixes for each serialization. This requried some code changes and 
I'll look into it.


> Namespace prefix counter not reseted
> ------------------------------------
>
>                 Key: AXIS2-2860
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2860
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.2
>            Reporter: Full Name
>            Assignee: Amila Chinthaka Suriarachchi
>            Priority: Minor
>
> We are using current Axis2 release with ADB binding. Each Axis stub is reused 
> after each call. After several calls, we have noticed, that some 
> namespace-prefix counters are never reseted and will increase after every 
> loop:
> <ns27:tag..> will result to: <ns1233:tag..> after several calls with the same 
> stub instance. You can reproduce this behaviour if you just put a loop aroung 
> a stub:
> while (true) {
> try {
>   stub.call(param);
> } catch (Exception e) {
>    e.printStackTrace();
> } finally {
>   stub.cleanup();
> }
> }
> It seems, that 'xmlWriter.getPrefix(namespace)' inside the ADB classes is not 
> reseted after each call. 
> It would be better (performance and payload length), to reset counter (e.g. 
> to ns1) back.

-- 
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]

Reply via email to