|
Hi Bruce,
Thank you for bringing this issue to our attention. We have confirmed that, as you describe, the hyphen in the data provided does cause Artix Data Services to incorrectly label the message invalid. We are investigating solutions for this problem and will update you on our results. Thank you and best regards, Pat IONA Technologies "Making Software Work Together" (tm) -------- See the improvements to our Online Support Centre with the introduction of the new Knowledge Base with improved content, search and browsing facilities: http://www.iona.com/support/kb/index.jspa Check out the CORBA community portal at: http://www.orbzone.org ------- Hi Bruce,
Could you provide us with some details on the impact this issue has on your business? This information will help schedule a suitable solution. Thank you and best regards, Pat IONA Technologies "Making Software Work Together" (tm) -------- See the improvements to our Online Support Centre with the introduction of the new Knowledge Base with improved content, search and browsing facilities: http://www.iona.com/support/kb/index.jspa Check out the CORBA community portal at: http://www.orbzone.org ------- Hi Bruce,
Apologies for a delay in replying to you. Our engineering team has confirmed that this issue to is a bug. In order to get it fixed it will require a major re-write of the SWIFT FIN model. As this work is quite a large undertaking, it has been scheduled for the 4.0 release. We do not currently have a fixed date for the 4.0 release yet, but it has not been scheduled within the next 12 months. Sincerest apologies for any inconvenience this has caused. Please let me know if you have any questions or comments. Kind regards, Jack Hi Bruce,
Just to elaborate on Jack's comment. This may seem on the face of it a relatively straight forward issue to resolve but appearances can be deceptive. The root cause of the problem is that SWIFT have a rule which states that ":" or "-" cannot be used as the first character of a line except the first line of a field. The omission of this rule was first highlighted in PUB-3181 some time ago. In order to create our model in a generic modeling fashion we build complex types up from simple types, so our view of what constitutes a field is different from SWIFT's with respect to this particular restriction. This therefore goes right to the heart of the way we parse the SWIFT model and therefore will necessitate major rework of either the model or the parser (API) which would break backwards compatibility for both yourselves and all of our other SWIFT customers of which there are around 50. As a rule we only break major areas of backwards compatibility at major releases and hence this has been scheduled to go in the Version 4 release of the product which Product Management have yet to schedule. I hope that helps in your understanding of the issue and why the status is as it is. Best Regards Fiona Hamilton Manager Standards Practice Group Iona Technologies Ltd Hi Saritha,
To answer your query posted in PUB-4533, we have added you as a watcher for the Artix Data Services' issue If you require any further information, please do not hesitate in contacting us. Thank you and best regards, Pat IONA Technologies "Making Software Work Together" (tm) -------- See the improvements to our Online Support Centre with the introduction of the new Knowledge Base with improved content, search and browsing facilities: http://www.iona.com/support/kb/index.jspa Check out the CORBA community portal at: http://www.orbzone.org ------- Hi Bruce,
If you are satisfied with the above information, we will close We would like to resolve this issue to your satisfaction as soon as possible. Thank you and best regards, Pat IONA Technologies "Making Software Work Together" (tm) -------- See the improvements to our Online Support Centre with the introduction of the new Knowledge Base with improved content, search and browsing facilities: http://www.iona.com/support/kb/index.jspa Check out the CORBA community portal at: http://www.orbzone.org ------- Hi Fiona, Pat,
We have noticing this issue more frequently with our messages having "-" in the name fields. What's the update on this? When are you planning to release the fix? Thanks, Saritha Saritha,
This particular problem with the "-" in the J option fields of 5x and 8x fields has been fixed and is included in the SWIFT 2009 library which will be available with the release of 3.9.0 of ADS. The 2009 library work has already been completed but the 3.9.0 release itself is due in a couple of months time as per our normal release schedule. At least this year there were very few changes so it should be a small project for you to upgrade this time. Regards Fiona This was checked in yesterday so TC would have picked up the change and added to the SWIFT 2009 plugin
Thanks Fiona!
Please keep us posted once 3.9.0 is available. Regards, Saritha |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
P3 - Defect
Illegal character reported for MT304
Thank you for contacting IONA Artix Data Services for support.
Please ensure that you provide us with all necessary information to reproduce the problem.
What is the current business impact of this issue on your organization?
Please advise.
Regards,
Abdul Adesanya.