Corba module cannot handle unbounded sequences
----------------------------------------------
Key: AXIS2-4955
URL: https://issues.apache.org/jira/browse/AXIS2-4955
Project: Axis2
Issue Type: Bug
Components: corba
Affects Versions: 1.5.4
Reporter: David Cole
While trying to follow the example found on the WS02 website at:
http://wso2.org/library/2807#comment-17115
Like others, I encounted issues running the example.
It turns out that the corba module is unable to handle 'unbounded' sequences
within the IDL file, like that used in the example.
Here is the IDL code snipplet for the sequence that is creating an issue (for
the full IDL file refer to the link above):
typedef sequence <long> longVals;
When defining an unbounded sequence like this, the corba module will throw an
exception and is unable to parse the IDL file:
org.apache.axis2.corba.exceptions.InvalidIDLException: an identifier is
required after the 'long' keyword
at
org.apache.axis2.corba.idl.parser.IDLVisitor.findDataType(IDLVisitor.java:397)
at
org.apache.axis2.corba.idl.parser.IDLVisitor.visitAnonymousSequence(IDLVisitor.java:554)
at
org.apache.axis2.corba.idl.parser.IDLVisitor.findDataType(IDLVisitor.java:354)
at
org.apache.axis2.corba.idl.parser.IDLVisitor.visitAndAddTypedefs(IDLVisitor.java:509)
at org.apache.axis2.corba.idl.parser.IDLVisitor.visit(IDLVisitor.java:111)
at org.apache.axis2.corba.idl.parser.IDLVisitor.visit(IDLVisitor.java:80)
at org.apache.axis2.corba.idl.IDLProcessor.process(IDLProcessor.java:49)
The only workaround for now is to use a bounded sequence instead:
typedef sequence <long,20> longVals;
The corba module should not enforce using only bounded sequences and it seems
that this is imposing an unnecessary restriction.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
