[ 
https://issues.apache.org/jira/browse/YOKO-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488967
 ] 

Lars Kühne commented on YOKO-320:
---------------------------------

Added o.a.y.t.idlpreprocessor package, svn revision 529064.

The package contains an IdlPreprocessorReader which is the central class in the 
package. Features:
 
* Always opens files using ISO-8851-1 encoding
* notices infinite include recursion and throws a PreprocessingException
* differentiates between normal ("") and system includes (<>), however actually 
resolving system includes is currently not implemented
* writes CPP style location markers to the output
* define state is preserved across multiple files

I also have some unit tests for the preprocessor sitting on my hard drive, but 
that needs to be reshuffled a bit to accommodate for the test data location in 
tools. My current test have the test data alongside the test classes and use 
this.getClass().getResource() as the way to locate input files and expected 
results.

I haven't started actually integrating this code into the current codebase. For 
basic testing this should mainly be a replacement of the current inputstream 
with the IdlPreprocessorReader and handling PreprocessingExceptions. I expect 
the main part of the integration work is to make ANTLR aware of the location 
markers and create error messages accordingly.


> IDLToWSDL tool cannot handle includes
> -------------------------------------
>
>                 Key: YOKO-320
>                 URL: https://issues.apache.org/jira/browse/YOKO-320
>             Project: Yoko - CORBA Server
>          Issue Type: Bug
>          Components: Idl2Wsdl
>    Affects Versions: v1.0.0
>            Reporter: Balaji Ravi
>         Assigned To: Balaji Ravi
>             Fix For: v1.0.0
>
>         Attachments: preprocessor.patch
>
>
> The IDLToWSDL tool cannot handle the include of another idl.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to