Re: [Ebxmlrr-tech] RE: [Bug] ExternalIdentifier's ClassificationScheme not included in submit request

[Farrukh N. <far...@su...>]

This message may be skipped if you do not use direct CVS bits.

Folks,

The recent bug(s) that was introduced in 
LifeCycleManagerImpl.saveObjects in jaxr module in CVS code has been 
fixed, regression tested and committed back to CVS.

The fix also addresses some long standing bugs in saveObjects.

The new design is much cleaner and we hope that it will be much more 
robust than the previous saveObjects code.

Thank you for your patience.

-- 
Regards,
Farrukh



Farrukh Najmi wrote:

> This is a new bug that I have introduced very recently :-(. I 
> discovered it late last night.
>
> I am in the middle of a high priority interrupt much of this week. I 
> would be grateful if people can work around the bug for a couple of 
> days by calling setModified on objects that are not being included in 
> the SubmitObjectRequest. I will try and attend to the bug for a few 
> hours later today an update.
>
> Marko Topolnik wrote:
>
>> Actually, and counterintuitively, it seems that you just have to do
>> setModified() on the ExternalIdentifier itself.
>>
>> Marko
>> -----Original Message-----
>> Subject: [Ebxmlrr-tech] [Bug] ExternalIdentifier's ClassificationScheme
>> not included in submit request
>>
>>        ClassificationSchemeImpl scheme =            
>> (ClassificationSchemeImpl) extId.getIdentificationScheme();
>>        scheme.setModified( true );
>>
>> This forces the scheme object to be included in the submit request.
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Ebxmlrr-tech mailing list
>> Ebx...@li...
>> https://lists.sourceforge.net/lists/listinfo/ebxmlrr-tech
>>  
>>
>