Foo int std::vector std::string Bar std::string Bar std::string Bar std::stringObject Introspection (OI) Goals • Byte level memory footprint analysis for objects • Complete object type hierarchies • Code Generation • Object Introspection as a Library • Object Introspection as a Profiler • Object Introspection Applied Type Reconstruction Object Introspection• (Re)construct an entire object • Code Generation • Object Introspection as a Library • Object Introspection as a Profiler • Object Introspection Applied Type Reconstruction Object Introspection Measurement Code Code Generation/*

conventional editor check for array classes (in order to not break AspectJ weaving) * BeanWrapper's introspection resolves bridge methods to find setter method for getter method with covariant return type * respected * ClassPathBeanDefinitionScanner performs trace/debug logging during class resource introspection * ClassPathBeanDefinitionScanner ignores same class found multiple times in the classpath (i CachingMapDecorator to expose all state representations in a thread-safe manner, even for pure introspection * revised CachingMapDecorator to use weak references for caching only (not losing a value from

conventional editor check for array classes (in order to not break AspectJ weaving) * BeanWrapper's introspection resolves bridge methods to find setter method for getter method with covariant return type * respected * ClassPathBeanDefinitionScanner performs trace/debug logging during class resource introspection * ClassPathBeanDefinitionScanner ignores same class found multiple times in the classpath (i CachingMapDecorator to expose all state representations in a thread-safe manner, even for pure introspection * revised CachingMapDecorator to use weak references for caching only (not losing a value from

representation and apply Data Orientation techniques somehow. • C++ still does not have reflection (introspection): we have to “pick our poison”: • Doing the conversion manually (good luck, you’ll need it) handle of scattered components. • I showed a preprocessing library to simulate reflection (introspection) to generate both the “normal” classes/structs and the handles • Now, there are many needs Alexandrescu’s Policy Design Pattern 40Conclusion • The language needs to improve (reflection (introspection)), libraries need to improve support for scattering and handles, programmers need to avail

CachingMapDecorator to expose all state representations in a thread-safe manner, even for pure introspection * revised CachingMapDecorator to use weak references for caching only (not losing a value from ParameterizedBeanPropertyRowMapper * revised BeanPropertyRowMapper to use JavaBean property introspection instead of expecting field/setter name matches * factored out "initBeanWrapper"/"getColumnValue" for XML formatting with whitespace) * BeanWrapperImpl lazily performs JavaBeans introspection (avoiding introspection failure for non-visible target class) * TypeConverterDelegate protects its collection

Functions 31. Recursion 32. Nested Functions 33. Closures 34. Decorators 35. Docstrings 36. Introspection 37. Annotations 38. Exceptions 39. The with statement 40. Installing 3rd party packages automatically generate documentation for your code. 36. Introspection Functions, variables and objects can be analyzed using introspection. First, using the help() global function we can get the

ParameterizedBeanPropertyRowMapper * revised BeanPropertyRowMapper to use JavaBean property introspection instead of expecting field/setter name matches * factored out "initBeanWrapper"/"getColumnValue" for XML formatting with whitespace) * BeanWrapperImpl lazily performs JavaBeans introspection (avoiding introspection failure for non-visible target class) * TypeConverterDelegate protects its collection ClassLoader * added "getTargetInterfaceName()" method to RmiInvocationHandler, for client-side introspection * HttpInvokerClientInterceptor does not require an "afterPropertiesSet()" call for initializing

ParameterizedBeanPropertyRowMapper * revised BeanPropertyRowMapper to use JavaBean property introspection instead of expecting field/setter name matches * factored out "initBeanWrapper"/"getColumnValue" for XML formatting with whitespace) * BeanWrapperImpl lazily performs JavaBeans introspection (avoiding introspection failure for non-visible target class) * TypeConverterDelegate protects its collection ClassLoader * added "getTargetInterfaceName()" method to RmiInvocationHandler, for client-side introspection * HttpInvokerClientInterceptor does not require an "afterPropertiesSet()" call for initializing

ParameterizedBeanPropertyRowMapper * revised BeanPropertyRowMapper to use JavaBean property introspection instead of expecting field/setter name matches * factored out "initBeanWrapper"/"getColumnValue" for XML formatting with whitespace) * BeanWrapperImpl lazily performs JavaBeans introspection (avoiding introspection failure for non-visible target class) * TypeConverterDelegate protects its collection ClassLoader * added "getTargetInterfaceName()" method to RmiInvocationHandler, for client-side introspection * HttpInvokerClientInterceptor does not require an "afterPropertiesSet()" call for initializing

configure the following properties to validate tokens through introspection: Properties spring.security.oauth2.resourceserver.opaquetoken.introspection- uri=https://example.com/check-token spring.security.oauth2 Yaml spring: security: oauth2: resourceserver: opaquetoken: introspection-uri: "https://example.com/check-token" client-id: "my-client-id" client-secret: default, field introspection will be allowed on the schema as it is required for tools such as GraphiQL. If you wish to not expose information about the schema, you can disable introspection by setting