[MDSAL-52] Binding Java API Generator -> doesn't handle non-alphabetic signs in names of enum constants, allowed by rfc6020 though Created: 06/Nov/14 Updated: 09/Mar/18 Resolved: 26/Apr/17 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Martin Ciglan | Assignee: | Jakub Toth |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||||||
| External issue ID: | 2332 | ||||||||||||||||
| Description |
|
Binding Java API Generator doesn't handle non-alphabetic signs in names of enum constants, allowed by rfc6020 though. As an output of this issue, we're not able to compile generated code. |
| Comments |
| Comment by Martin Ciglan [ 11/Nov/14 ] |
|
I am adding some kind of proposal how should we handle this issue. public class NonAlphabeticHandler { //give occurence enum constants meanings private static final String PLUS_PATTERN = " private static final String ONE_PATTERN = "1"; private static final String QUESTIONMARK_PATTERN = " //might get deleted and be part of generic one, detected it in name of protocol private static final String GENERIC_PATTERN = "[^A-Za-z0-9]"; /**
public static void main(String[] args) { System.out.public class NonAlphabeticHandler {println(System.currentTimeMillis()); className = "Tdp:"; System.out.println(System.currentTimeMillis()); . Note: Not sure about nonalphabetic signs, which are part of words like device names, perhaps Device+ -> Device_Plus would be more reasonable. Of course, it's matter of discussion in team. |
| Comment by Martin Ciglan [ 20/Jan/15 ] |
|
in very first draft phase |
| Comment by Ryan Goulding [ 06/Apr/16 ] |
|
Hi Martin, I see that you actively have "taken" this one... is that still applicable? If not, please let me know so that I can take a look. Thanks, |
| Comment by Martin Ciglan [ 06/Apr/16 ] |
|
Hi Ryan This is one of several bugs, which we have identified during work with binding specification version 1. This issue depends on implementation of binding specification version 2, please see So, once 1411 is resolved, this should get resolved too. I hope that helps. Martin |
| Comment by Vratko Polak [ 04/Jul/16 ] |
|
Java binding v2 will not be ported to Beryllium, as far as I know. In the meantime, it is possible to somewhat reduce severity of this Bug. |
| Comment by Vratko Polak [ 22/Aug/16 ] |
|
> it is possible to somewhat reduce severity Merged to master (Boron and Carbon): https://git.opendaylight.org/gerrit/41280 Waiting for review for Beryllium: https://git.opendaylight.org/gerrit/44481 |
| Comment by Vratko Polak [ 26/Sep/16 ] |
|
> Beryllium: https://git.opendaylight.org/gerrit/44481 The workaround is now merged. Other characters aside slash have to be handled separately (possibly only in Java binding v2). |
| Comment by Jakub Toth [ 30/Jan/17 ] |