<div dir="ltr">Hi<div><br></div><div>I was following the docs online ( <a href="https://docs.jboss.org/weld/reference/latest/en-US/html/devmode.html">https://docs.jboss.org/weld/reference/latest/en-US/html/devmode.html</a> ) to integrate Weld Probe into an SE application.</div><div><br></div><div>It looks like Probe takes care of serving static assets itself via the filter.</div><div><br></div><div>Since this is an SE application, I programmatically register the ProbeFilter (name=&quot;WeldProbeFilter&quot;,value= new String[]{&quot;/weld-probe/*&quot;},</div><div>            uriPatterns=new String[]{&quot;/weld-probe/*&quot;},</div><div>            dispatcherTypes=Constants.DISPATCHER_TYPES, // short cut for all</div><div>            initParams=new WebInitParam[]{}, </div><div>            asyncSupported=true, </div><div>            servletName=null, </div><div>            filterClass=ProbeFilter.class)</div><div><br></div><div>I tried to start the application w/ -Dorg.jboss.weld.development=true and noticed that it seemed to switch to bean-discovery-mode=all (without trim, even though all of my JARs are with trim option).  I then tried to manually enable the extension, but that resulted in </div><div><br></div><div><div>21:08:25.149 [main] WARN  org.jboss.weld.probe.Probe - PROBE-000008: </div><div>=====================================</div><div> Weld Development Mode: ENABLED</div><div> ------------------------------------</div><div> Disable this mode in production - it may have negative impact on performance and/or represent a potential security risk</div><div>=====================================</div><div>21:08:25.767 [ForkJoinPool.commonPool-worker-7] WARN  org.jboss.weld.Validator - WELD-001473: javax.enterprise.inject.spi.Bean implementation org.apache.cxf.cdi.CdiBusBean@74cadd41 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won&#39;t be possible to inject this bean into a bean with a passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface.</div><div>Exception in thread &quot;main&quot; org.jboss.weld.exceptions.DeploymentException: PROBE-000005: Probe is not properly initialized</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:38)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:489)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:90)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.environment.se.Weld.initialize(Weld.java:800)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.environment.se.Weld.initialize(Weld.java:175)</div><div><span style="white-space:pre">        </span>at ws.ament.hammock.bootstrap.weld3.Weld3Bootstrapper.start(Weld3Bootstrapper.java:58)</div><div><span style="white-space:pre">        </span>at ws.ament.hammock.Bootstrap.main(Bootstrap.java:41)</div><div><span style="white-space:pre">        </span>at ws.ament.hammock.example.canonical.RestApplication.main(RestApplication.java:31)</div><div>Caused by: org.jboss.weld.exceptions.IllegalStateException: PROBE-000005: Probe is not properly initialized</div><div><span style="white-space:pre">        </span>at org.jboss.weld.probe.InvocationMonitor.init(InvocationMonitor.java:148)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.probe.InvocationMonitor.monitorCreation(InvocationMonitor.java:103)</div><div><span style="white-space:pre">        </span>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)</div><div><span style="white-space:pre">        </span>at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)</div><div><span style="white-space:pre">        </span>at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)</div><div><span style="white-space:pre">        </span>at java.lang.reflect.Method.invoke(Method.java:498)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.invokeNext(WeldInvocationContextImpl.java:92)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.proceed(WeldInvocationContextImpl.java:124)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.producer.ConstructorInterceptionInstantiator$1.aroundConstruct(ConstructorInterceptionInstantiator.java:100)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.ConstructorInjectionPoint.invokeAroundConstructCallback(ConstructorInjectionPoint.java:109)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.ConstructorInjectionPoint.invokeAroundConstructCallbacks(ConstructorInjectionPoint.java:95)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:78)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.producer.AbstractInstantiator.newInstance(AbstractInstantiator.java:28)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.producer.InterceptorApplyingInstantiator.newInstance(InterceptorApplyingInstantiator.java:62)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.producer.ConstructorInterceptionInstantiator.newInstance(ConstructorInterceptionInstantiator.java:66)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.producer.BasicInjectionTarget.produce(BasicInjectionTarget.java:112)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.injection.producer.BeanInjectionTarget.produce(BeanInjectionTarget.java:186)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:158)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:140)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:102)</div><div><span style="white-space:pre">        </span>at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131)</div></div><div><br></div><div><br></div><div>Even though based on the docs that should be all that&#39;s needed.  Is there something else required to get Probe running in SE?</div><div><br></div></div>