[
https://issues.apache.org/jira/browse/YOKO-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873471#comment-15873471
]
David Jencks commented on YOKO-466:
-----------------------------------
commit cf24428542b17b5dc43d14676046c1b0e5f8935f
Author: Neil Richards <n...@linux.vnet.ibm.com>
Date: Thu May 14 10:58:20 2015 +0100
Disable TypeCodeFactory IDL name checking tests
commit 258cd81da308dda5afc12ca4432524ce942b0047
Author: Neil Richards <n...@linux.vnet.ibm.com>
Date: Thu May 14 09:37:42 2015 +0100
Disable IDL name checking in TypeCode construction
commit 838260daf33739db725c930f13f1d7356c0727a0
Author: Neil Richards <n...@linux.vnet.ibm.com>
Date: Tue May 12 18:20:09 2015 +0100
Use IDL Helper class to create stubs for IDLEntity
> Disable idl name checking
> -------------------------
>
> Key: YOKO-466
> URL: https://issues.apache.org/jira/browse/YOKO-466
> Project: Yoko - CORBA Server
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: orb core
> Affects Versions: v1.1.0
> Reporter: David Jencks
>
> TypeCode creation tries to enforce all names are IDL names.
>
> By comparison with the behaviour seen from other ORB implementations,
> this is not necessarily the case, for example when generating the
> FullValueDescription for Java (Serializable) valuetypes.
> Other parts of yoko behave in a compatible manner to these other
> implementations, which currently causes the IDL name checking to fail during
> FVD generation.
>
> This introduces minimal changes to disable IDL name checking.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
