May be that my majors concerns are about what is intended by runtime and designtime phases in e-business and what is considered be a part of a phase.
Generally runtime describes the operation of a computer program, the duration of its execution, from beginning to termination. In the e-business context, runtime cover the execution time of business exchanges from beginning to termination => BP execution, messages exchange.
The e-business designtime cover all the rest => establishment of agreement, discovery, data modelisation, BP definition and system configuration.
Is my interpretation correct?
By this point of view the registry could be:
1. just a design time tool but
2. if we consider all *systems* participating to the execution time then the registry (that for example could be queried by an ebMS system to obtain a CPA for configuring the message handler while executing a BP) is a design and run time tool.
What is right for you?
Now I've not only a fever :-P
-----Message d'origine-----
De : Farrukh Najmi [mailto:]
Envoyé : jeudi 5 janvier 2006 03:03
À : Chiusano Joseph
Cc : BEDINI Ivan RD-BIZZ-CAE; ebXML Regrep;
Objet : Re: [regrep] Post-holiday registry riddle
Chiusano Joseph wrote:
> It's riddle fever.:)
>
> My answer: "design-time and run-time". I would speculate that there is
> more design-time usage out there than run-time usage; but I leave it
> to Farrukh, Duane/Matt, Miko, Carl and others (apologies for anyone
> else I have forgotten) who have implementations to verify this. My
> hope and vision is that over time, run-time usage will equal or
> surpass design-time usage, as our semantic capabilities expand.
I have seen more run time usage than design time usage in projects I
have been involved with. Most of these projects use the registry as a n
information store (metadata and content) that is used at run time in a
manner reminiscent of database in classic enterprise applications.
--
Regards,
Farrukh
