[ http://issues.apache.org/jira/browse/YOKO-68?page=comments#action_12416764 ]
Darren Middleman commented on YOKO-68: -------------------------------------- The sending of the version number in the service contexts should probably be removed for Yoko. This was done in the IONA code to handle backwards compatibility with some older versions of Orbacus that did not handle wide character data correctly. Moving forward, it should never be needed. We've also heard that it can cause issues with other ORBs which don't handle unknown service contexts very well. > Incorrect version number in o.a.y.orb.OB.Version > ------------------------------------------------ > > Key: YOKO-68 > URL: http://issues.apache.org/jira/browse/YOKO-68 > Project: Yoko - CORBA Server > Type: Bug > Reporter: Lars Kühne > Assignee: Lars Kühne > Fix For: 1.0-incubating-M1 > > Current output is "Yoko for Java 4.3.1 [GA release]". > The output should reflect the version number in the pom. One technique to > find the version is described in > http://mail-archives.apache.org/mod_mbox/maven-users/200605.mbox/[EMAIL > PROTECTED] > A numerical version number (4030100) is also in the Version class, it is sent > as a ServiceContext. Not sure how to generate such numbers from the pom > version which might include additional textual info like "SNAPSHOT" or > "Incubator". I can't see any uses for sending the version Context, except > logging the version of the communication partner. Maybe this functionality > should be removed completely? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
