The fix has been applied to trunk and will be released with riftsaw-2.3.0.Final, which should be released in the coming weeks - we just need to synchronize with the release of the next version of jbossesb.
RIFTSAW-378 is only concerned with providing a junit testcase for your reported issue.
Ok, but what I don't understand, maybe you can help me... You've said "
Gary Brown wrote:
However this will depend upon jbossws-native or cxf 3.4.0.GA.
Are there any changes that must be done also on jbossws-native/cxf 3.4.0. GA? About the next riftsaw release, are there any changes in the next version of jbossesb that are influencing this issue, is it mandatory to updagrade also the jbossesb version together with the riftsaw?
There are no changes that need to be done in jbossws - however you will need to install jbossws 3.4.0.GA to get the fix you need. This version of jbossws is available now.
The next release of riftsaw will be dependent upon jbossesb 4.10 - as there are some changes in how the esb and riftsaw register UDDI entries, so the releases have had to be synchronized.
Thank you for your responses. I hope I do not disturb with so many questions, but maybe you can help me with more detailed information regarding the next riftsaw-2.3.0.Final, although I know it depends upon jbossesb-4.10. Do you have some planned date for the release? And do you know when will be released the enterprise version with this riftsaw version?
Thank you again,
Unfortunately I can't give you a more accurate date for riftsaw-2.3.0.Final, because we are dependent upon the release of jbossesb 4.10, and I don't have a definitive date for when they are going to release. But should hopefully be in the next couple of weeks.
I am not sure of the release schedule for the enterprise version (which will be SOA Platform 5.2). For more information it is probably better for you to contact Ken Johnson at: firstname.lastname@example.org