You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following some issue with some internal project using ZProject / Java, we had to dig a bint in
generated Java bindings.
From this, it seems that generated Java bindings do not implement the fresh = "0" in <return XXX />.
It looks like the returned object is always considered as fresh = "1".
At least, we do not find the "owned" mechanism found with Delphi or a similar with Python.
If I'm right about the "owned" and "fresh", AND if I'm able to provide a fix, there is a possibility that
some existing Java applications will see the change and face some issues ...
Now, I also read #776 ...
Looks like Java bindings already suffer some heavy restriction ...
Following some issue with some internal project using ZProject / Java, we had to dig a bint in
generated Java bindings.
From this, it seems that generated Java bindings do not implement the
fresh = "0"
in<return XXX />
.It looks like the returned object is always considered as
fresh = "1"
.At least, we do not find the "owned" mechanism found with Delphi or a similar with Python.
@bluca or @sappo, can you confirm ?
Thx for your help.
The text was updated successfully, but these errors were encountered: