Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 3.0.0.Beta1
-
Component/s: None
-
Labels:None
Description
17:54:29,059 WARNING [ServiceLoader] Could not load service class org.jboss.weld.extensions.interceptor.InterceptorExtension
17:54:41,769 INFO [org.jboss.weld.extensions.core.CoreExtension] Preventing class com.ocpsoft.socialpm.domain.user.User from being installed as bean due to @Veto annotation
A full 12, almost 13 seconds required during part of weldx bootup. Seems like something we could improve.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
This is actually a weld issue with portable extensions, which will be resolved in the next release.
Show
Stuart Douglas
added a comment - This is actually a weld issue with portable extensions, which will be resolved in the next release.
Stuart Douglas
added a comment - This is actually a weld issue with portable extensions, which will be resolved in the next release. Re-opened to edit issue
Show
Shane Bryzak
added a comment - Re-opened to edit issue
Shane Bryzak
added a comment - Re-opened to edit issue 
I think is may actually be more of an issue with the performance of the weld portable extensions implementation rather than weldx itself. Also not all of that 12 seconds would be spent in weldx, some of it is spent as part of the normal weld boot process.
I will try and look into this with a profiler and find out exactly what is to blame here.