IBM Support

RS00533: INCORRECT XOM FILE GENERATED BY DYNAMIC XSDS UPON PUBLISHED INTO RTS

Fixes are available

WebSphere ILOG Rule Team Server V7.1.1.3 Fix Pack
WebSphere ILOG JRules V7.1.1.3 Fix Pack

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The XOM file generated based on dynamic xsds is found to be
incorrect upon published to RTS. This causes unexpected
execution output result where the element name become unknown.
For example, the XOM file in the resource folder of an ruleset
archive, the element_Marktpartneridentifikation was declared
twice under class IlogRulesXmlPackage.
class IlogRulesXmlPackage
     property "ilog.rules.xml.packageInfo" {
         "1" {
             xmlName
"{http://eon.com/emtg/smt/partnermgmt/bo/v1}element_Marktpartner
identifikation",
             xomType
"com.eon.emtg.smt.partnermgmt.bo.v1.Marktpartneridentifikation"
         },
         "2" {
             xmlName
"{http://eon.com/emtg/smt/partnermgmt/bo/v1}element_Marktpartner
identifikation",
             xomType
"com.eon.emtg.smt.partnermgmt.bo.v1.Marktpartneridentifikation"
         },

The correct should be 1) element_marktpartner and 2)
element_Marktpartneridentifikation

Local fix

  • Trigger a change in rule project's property (e.g. add and remove
a category), immediately synchronize and publish the changes to
RTS without restarting RS.

Problem summary

  • correct XOM file is now generated by dynamic XSDS

Problem conclusion

  • 



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    RS00533
    • 

  • Reported component name
    WS ILOG JRULES
    • 

  • Reported component ID
    5724X9800
    • 

  • Reported release
    702
    • 

  • Status
    CLOSED  FIN
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2011-01-17
    • 

  • Closed date
    2011-04-07
    • 

  • Last modified date
    2011-04-07
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    • 



Fix information


    



Applicable component levels


    

  • R703  PSY
       UP
    • 

  • R711  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS6MTS","label":"WebSphere ILOG JRules"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            07 April 2011
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback