1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
//! Identity reconstruction at the task handler boundary.
//!
//! When a job is enqueued, Boson stores `actor_json` on the job record. When a worker dispatches
//! the job, it calls [`ExecutionContextFactory::build`] to reconstruct handler context from that
//! JSON. Task handlers (including those defined with `#[boson::task]`) receive the result as
//! `Box<dyn ExecutionContext>`.
//!
//! # In task handlers
//!
//! Use [`ExecutionContext::label`] for logs and [`ExecutionContext::actor_json`] when the handler
//! only needs the captured actor payload. You do not configure the factory inside the handler.
//!
//! # Choosing a factory (integrator)
//!
//! Install the factory once at worker boot via
//! [`BosonBuilder::execution_context_factory`](https://docs.rs/boson-runtime/latest/boson_runtime/struct.BosonBuilder.html#method.execution_context_factory).
//! See the [`boson`](https://docs.rs/uf-boson) crate
//! [Getting started](https://docs.rs/uf-boson/latest/boson/index.html#getting-started) for a full boot example.
//!
//! | Approach | When to use |
//! |----------|-------------|
//! | [`JsonExecutionContextFactory`] | Examples, smoke tests, and handlers that only need [`ExecutionContext::label`] and [`ExecutionContext::actor_json`] |
//! | Custom [`ExecutionContextFactory`] | Production apps that map actor JSON to sessions, permissions, database access, or other application identity |
//!
//! # Custom factory sketch
//!
//! ```rust,no_run
//! use boson_core::{ExecutionContext, ExecutionContextFactory, IdentityError};
//! use serde_json::Value;
//!
//! struct AppContext {
//! actor_json: Value,
//! }
//!
//! impl ExecutionContext for AppContext {
//! fn label(&self) -> &str {
//! "app"
//! }
//! fn actor_json(&self) -> &Value {
//! &self.actor_json
//! }
//! }
//!
//! struct AppFactory;
//!
//! impl ExecutionContextFactory for AppFactory {
//! fn build(&self, actor_json: &Value) -> Result<Box<dyn ExecutionContext>, IdentityError> {
//! // Validate actor_json and construct application-specific context.
//! Ok(Box::new(AppContext {
//! actor_json: actor_json.clone(),
//! }))
//! }
//! }
//! ```
use Value;
use crateIdentityError;
/// Opaque execution context for task handlers.
///
/// The runtime passes this as the first argument to `#[boson::task]` handlers and to registered
/// invoke functions. Use [`label`](Self::label) for logs and [`actor_json`](Self::actor_json) when
/// the handler only needs the captured actor payload.
/// Builds handler execution context from captured actor JSON at enqueue time.
///
/// Implement this trait (or use [`JsonExecutionContextFactory`]) and pass the factory to
/// [`BosonBuilder::execution_context_factory`](https://docs.rs/boson-runtime/latest/boson_runtime/struct.BosonBuilder.html#method.execution_context_factory) when booting the runtime.
///
/// # Example
///
/// Most apps start with [`JsonExecutionContextFactory`]. Custom factories validate `actor_json` and
/// attach sessions or permissions — see [Custom factory sketch](crate::identity#custom-factory-sketch).
///
/// ```ignore
/// use std::sync::Arc;
///
/// use boson_backend_mem::MemQueueBackend;
/// use boson_core::JsonExecutionContextFactory;
/// use boson_runtime::Boson;
///
/// # fn main() -> boson_core::Result<()> {
/// let _boson = Boson::builder()
/// .queue_backend(Arc::new(MemQueueBackend::new()))
/// .execution_context_factory(JsonExecutionContextFactory)
/// .build()?;
/// # Ok(())
/// # }
/// ```
/// Default factory that wraps actor JSON in a labeled [`ExecutionContext`].
///
/// Suitable for examples and handlers that only need [`ExecutionContext::label`] and
/// [`ExecutionContext::actor_json`]. For application-specific identity (database sessions,
/// permission checks, typed actors), implement [`ExecutionContextFactory`] instead.
///
/// The default [`label`](ExecutionContext::label) keeps short actor JSON as-is (up to 64
/// characters) and replaces longer payloads with a stable `json:<hash>` form so logs stay
/// compact. The full actor payload remains available via [`actor_json`](ExecutionContext::actor_json).
///
/// # Example
///
/// Pass to [`BosonBuilder::execution_context_factory`](https://docs.rs/boson-runtime/latest/boson_runtime/struct.BosonBuilder.html#method.execution_context_factory) at worker boot:
///
/// ```ignore
/// use std::sync::Arc;
///
/// use boson_backend_mem::MemQueueBackend;
/// use boson_core::JsonExecutionContextFactory;
/// use boson_runtime::Boson;
///
/// # fn main() -> boson_core::Result<()> {
/// let _boson = Boson::builder()
/// .queue_backend(Arc::new(MemQueueBackend::new()))
/// .execution_context_factory(JsonExecutionContextFactory)
/// .auto_registry()
/// .build()?;
/// # Ok(())
/// # }
/// ```
;
/// Compact log label for actor JSON: keep short payloads; hash long ones.