Read only archive ; use https://github.com/JacORB/JacORB/issues for new issues
Bug 1029 - Can't compile old idl files using JacORB, causes loop
Summary: Can't compile old idl files using JacORB, causes loop
Status: NEW
Alias: None
Product: JacORB
Classification: Unclassified
Component: IDL compiler (show other bugs)
Version: 2.1
Hardware: PC other
: P3 major
Assignee: Mailinglist to track bugs
URL:
Depends on:
Blocks:
 
Reported: 2016-03-16 04:42 UTC by Stefan Hagström
Modified: 2016-03-17 03:42 UTC (History)
1 user (show)

See Also:

Attachments
Idlfiles and log (86.83 KB, application/x-7z-compressed)
2016-03-16 04:42 UTC, Stefan Hagström 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Hagström 2016-03-16 04:42:50 UTC 
Created attachment 473 [details]
Idlfiles and log

Hi,

I'm trying to compile some old idl files from 2007 that were developed for a visibroker corba integration using jacorb. The problem is that I get a strange loop when trying to compile.

I'm running this command
"c:\jacorb-2.1\bin\idl.bat" -W 4 -Ic:\jacorb-2.1\idl\omg -i2jpackage basicnet:new.package.name.basicnet BasicNet.idl

..everything seems to go fine in the beginnin..
[jacorb.idl] INFO : checking identifier locationName
[jacorb.idl] INFO : checking identifier ExternalTime
[jacorb.idl] INFO : checking identifier managedElementExternalTime
[jacorb.idl] INFO : ScopedName.setId ExternalTime
[jacorb.idl] INFO : ScopedName.escapeName ExternalTime
[jacorb.idl] INFO : checking identifier OptSystemTimingSource
[jacorb.idl] INFO : checking identifier systemTimingSource
[jacorb.idl] INFO : ScopedName.setId OptSystemTimingSource
[jacorb.idl] INFO : ScopedName.escapeName OptSystemTimingSource
[jacorb.idl] INFO : checking identifier GeneralError
[jacorb.idl] INFO : checking identifier GeneralErrorList
[jacorb.idl] INFO : checking identifier generalErrorListException
[jacorb.idl] INFO : ScopedName.setId GeneralErrorList
[jacorb.idl] INFO : ScopedName.escapeName GeneralErrorList
[jacorb.idl] INFO : checking identifier EquipmentHolderID
[jacorb.idl] INFO : ScopedName.setId EquipmentHolderID
[jacorb.idl] INFO : ScopedName.escapeName EquipmentHolderID
[jacorb.idl] INFO : checking identifier EquipmentHolderIDList
[jacorb.idl] INFO : checking identifier CircuitPackID
[jacorb.idl] INFO : ScopedName.setId CircuitPackID
[jacorb.idl] INFO : ScopedName.escapeName CircuitPackID
[jacorb.idl] INFO : checking identifier CircuitPackIDList
[jacorb.idl] INFO : checking identifier Equipment
[jacorb.idl] INFO : checking identifier nms
[jacorb.idl] INFO : ScopedName.setId nms
[jacorb.idl] INFO : ScopedName.escapeName nms
[jacorb.idl] INFO : checking identifier nms
[jacorb.idl] INFO : ScopedName.setId nms.nms
[jacorb.idl] INFO : ScopedName.escapeName nms.nms
[jacorb.idl] INFO : checking identifier nms
[jacorb.idl] INFO : ScopedName.setId nms.nms.nms
[jacorb.idl] INFO : ScopedName.escapeName nms.nms.nms
[jacorb.idl] INFO : checking identifier nms
[jacorb.idl] INFO : ScopedName.setId nms.nms.nms.nms
[jacorb.idl] INFO : ScopedName.escapeName nms.nms.nms.nms
[jacorb.idl] INFO : checking identifier nms
[jacorb.idl] INFO : ScopedName.setId nms.nms.nms.nms.nms
[jacorb.idl] INFO : ScopedName.escapeName nms.nms.nms.nms.nms
[jacorb.idl] INFO : checking identifier nms
[jacorb.idl] INFO : ScopedName.setId nms.nms.nms.nms.nms.nms
[jacorb.idl] INFO : ScopedName.escapeName nms.nms.nms.nms.nms.nms
... and so on

Do you have any idea why I get this loop?

I've attached a complete outputfile.

I tried using a newer jacorb (3.7) but get the same error.

When I try jdk1.8.0_45:s idlj I get this error, which I understand to be because theese idl-files are older than the TF standard 3.0 and doesn't conform to the new standard.

SEVERE org.jacorb.idl.lexer emit_error :\workspace\nexusCorbaAdapter\idl\idl_netact\NMS.idl, line: 841(1): In operation nms.Notifications.attributeValueChange argument attributeValueChangeInfo clashe
s with type nms.AttributeValueChangeInfo

Thanks
Stefan
Comment 1 Nick Cross 2016-03-16 05:58:53 UTC 
Looks like a bug in the IDL Compiler.
Comment 2 Stefan Hagström 2016-03-17 03:42:15 UTC 
(In reply to Nick Cross from comment #1)
> Looks like a bug in the IDL Compiler.

When can it be fixed?