This is not a bug. It's misusing the API. If the URI mappers are used
with the plan serializer, a SerializationCallback has to be registered
which allows the plan serializer to retrieve the exact same mappers that
were registered before.

** Changed in: zorba
       Status: New => Invalid

You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.

  plan serialization error with registerURIMapper

Status in Zorba - The XQuery Processor:

Bug description:
  The following program:
         StaticContext_t lSctx = aZorba->createStaticContext();
         OneToOneURIMapper lStopWordsMapper(EntityData::STOP_WORDS);
         XQuery_t lQuery = aZorba->compileQuery(lIn, lSctx);
         lQuery->saveExecutionPlan(lOut, ZORBA_USE_BINARY_ARCHIVE, 

         std::istringstream lIn(lOut.str());
         XQuery_t lQuery = aZorba->createQuery();
         std::cout << lQuery << std::endl;

  Zorba serialization error [zerr:ZCSE0013]: failed to load pre-compiled query: 
document, collection, or module resolver required but no SerializationCallback 

  By commenting " lSctx->registerURIMapper(&lStopWordsMapper);" this
  program works fine.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to