| Summary: | Structured events containing a user-defined IDL struct with an enumeration field never received by non-TAO ORBs | ||
|---|---|---|---|
| Product: | TAO | Reporter: | midnightdf |
| Component: | Notification Service | Assignee: | midnightdf |
| Status: | NEW --- | ||
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 1.4.2 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Bug Depends on: | 2048 | ||
| Bug Blocks: | |||
assigning to Jeff because this bug is about the ETCL library implementation. Accepted. Johnny Willemsen asked me to reassign this one. Could someone at OCI just take a quick look and see if any of the work you've done has had an effect on this bug? (In reply to comment #4) > Johnny Willemsen asked me to reassign this one. Could someone at OCI just take > a quick look and see if any of the work you've done has had an effect on this > bug? Same answer as in Bug 2048: I don't think so. Our changes to the Notification Service generally fall into these categories: - Stability changes (fixed memory leaks, thread leaks, race conditions, etc.) - Implementation of Reliability QoS (ConnectionReliability, EventReliability) - Addition of a separate ORB for dispatching (so event dispatching to consumers is separated from request processing and handling of incoming events) - Addition of monitoring and control interfaces I don't believe we have made any changes that would affect this use case. Reassigned this bug back to the reporter. If this feature is needed and you would like to sponsor or contribute its addition to TAO's Notification Service, we would be glad to help. changed to enhancement |
Hello, basically I have the following problem - 1. A (TAO) structured push supplier sends an event where: filterable_data[0].name="eventname" and filterable_data[0].value contains a user-defined IDL structure: enum anEnum { APC_CORRECTED, APC_UNCORRECTED, APC_CORRECTED_AND_UNCORRECTED }; struct anEvent { anEnum enumField; }; 2. The "enumField" of "someStruct" is not explicitly setting an enumeration value: ncfail::anEvent data; before being packed into a structured event. 3. (TAO) structured event consumers receive this event perfectly. 4. (omniORBPy) structured event consumers never receive this event. 5. If I explicitly set the "anEnum" field of the struct before publishing the event, both TAO and omniORBPy structured event consumers receive the event. Is this a problem with TAO or omniORB? Thanks in advance for your help, David Fugate ALMA SW Engineer