[JBoss JIRA] Created: (CDI-3) Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes
by Stuart Douglas (JIRA)
Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes
------------------------------------------------------------------------------------------------------------
Key: CDI-3
URL: https://jira.jboss.org/browse/CDI-3
Project: CDI Specification Issues
Issue Type: Feature Request
Affects Versions: 1.0
Reporter: Stuart Douglas
At the moment AnnotatedTypes can only be added in the BeforeBeanDiscovery phase. This means that if you want to install additional beans based on the beans processed in the ProcessAnnotatedType phase you must instead add implementations of the Bean interface in the AfterBeanDiscovery phase. This interface is more limited than annotated type, and does not let you exactly mimic the behaviour of beans added as AnnotatedTypes.
Some of the things that the bean interface will not let you mimic are:
- Interceptors
- Disposal methods
- Producer fields for normal scoped beans
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (CDI-2) Interceptor bindings defined at method level should override those at the class level
by Pete Muir (JIRA)
Interceptor bindings defined at method level should override those at the class level
-------------------------------------------------------------------------------------
Key: CDI-2
URL: https://jira.jboss.org/browse/CDI-2
Project: CDI Specification Issues
Issue Type: Bug
Components: Specification
Reporter: Pete Muir
We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec.
In section 9.5.2 of the spec:
If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (CDITCK-168) extensions.processBean.ProcessBean event count issue
by Scott Ferguson (JIRA)
extensions.processBean.ProcessBean event count issue
----------------------------------------------------
Key: CDITCK-168
URL: https://jira.jboss.org/browse/CDITCK-168
Project: CDI TCK
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tests
Affects Versions: 1.0.2.CR1
Environment: any
Reporter: Scott Ferguson
The issue is in an assertion in extensions.processBean.ProcessBeanTest, counting the number of times the Cowshed bean raises a discovery event. There are three tests affected by this issue:
extensions.processBean.ProcessBeanTest
testProcessProducerFieldEvent()
testProcessProducerMethodEvent()
extensions.processBean.ProcessSessionBeanTest
testProcessSessionBeanEvent()
specifically
testProcessProducerMethodEvent()
79: assert ProcessBeanObserver.getCowShedProcessBeanCount() == 2;
testProcessProducerFieldEvent()
102: assert ProcessBeanObserver.getChickenHutchProcessBeanCount() == 2;
testProcessSessionBeanEvent()
63: assert ProcessBeanObserver.getElephantProcessBeanCount() == 2;
But I can't see how this number is 2 instead of 1. The Cowshed looks like:
public class Cowshed {
@Produces public Cow getDaisy() { ... }
}
So there should be 3 relevant extension events fired:
ProcessBean<Cowshed>
ProcessProducerMethod<Cowshed, Cow>
ProcessBean<Cow>
I double checked the ProcessProducerMethod interface:
ProcessProducerMethod<T,X> extends ProcessBean<X>
which is where the ProcessBean<Cow> comes from, but I don't see where
the 2nd ProcessBean<Cowshed> comes from.
The ProcessSessionBean issue is essentially the same
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (WELD-703) SEVERE: Exception while loading the app
by sreekanth manga (JIRA)
SEVERE: Exception while loading the app
---------------------------------------
Key: WELD-703
URL: https://jira.jboss.org/browse/WELD-703
Project: Weld
Issue Type: Bug
Components: Testing Infrastructure (Mocks and Harness Integration)
Environment: Linux, Glassfish Embedded.
Reporter: sreekanth manga
When running the weld tests against embedded glassfish , I am unable to get any of the test passing.So I started running a test case "activities.current.InactiveScopeTest" which passed with stand alone glassfish v3.1. Here is the maven output.
Actually there are around 28 tests failing with glassfish standalone server, with the same exception.I don't get any stack trace from the glassfish server log except for single line "SEVERE: Exception while loading the app". An issue has already been filed with glassfish .[https://glassfish.dev.java.net/issues/show_bug.cgi?id=13713]
Not sure if this is test/weld test framework issue.So filing an issue here.
Maven run log:
=============
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Weld Integration Tests (JBoss AS) 1.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ weld-core-test-arquillian ---
[INFO] Deleting /space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target
[INFO]
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce) @ weld-core-test-arquillian ---
[WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks.
[INFO]
[INFO] --- build-helper-maven-plugin:1.5:maven-version (default) @ weld-core-test-arquillian ---
[INFO]
[INFO] --- build-helper-maven-plugin:1.5:parse-version (default) @ weld-core-test-arquillian ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (attach-license) @ weld-core-test-arquillian ---
[INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ weld-core-test-arquillian ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ weld-core-test-arquillian ---
[INFO] Compiling 3 source files to /space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ weld-core-test-arquillian ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 44 resources
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @ weld-core-test-arquillian ---
[INFO] Compiling 730 source files to /space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.6:test (default-test) @ weld-core-test-arquillian ---
[INFO] Concurrency config is {parallel=none, configurableParallelComputerPresent=false}
[INFO] Surefire report directory: /space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
4 Oct, 2010 9:09:01 PM org.jboss.arquillian.impl.XmlConfigurationBuilder loadArquillianConfiguration
INFO: building configuration from XML file: arquillian.xml
4 Oct, 2010 9:09:01 PM org.jboss.arquillian.impl.XmlConfigurationBuilder matchContainerConfiguration
WARNING: No container configuration found for URI: java:urn:org.jboss.arquillian.container.jbossas.managed_6
4 Oct, 2010 9:09:01 PM com.sun.enterprise.glassfish.bootstrap.EmbeddedNonOSGiGlassFishRuntimeBuilder provisionInstanceRoot
WARNING: AS_DEF_DOMAINS_PATH is not set.
4 Oct, 2010 9:09:01 PM com.sun.enterprise.glassfish.bootstrap.EmbeddedNonOSGiGlassFishRuntimeBuilder build
INFO: Created GlassFishRuntime com.sun.enterprise.glassfish.bootstrap.NonOSGiGlassFishRuntime@f2a55aa with Bootstrap Properties {com.sun.aas.installRootURI=file:/space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target/glassfish_fdeb7e07-4d0f-48f1-9c9f-94c9977b021c, GlassFish_Platform=Static, com.sun.aas.configFileURI=jar:file:/home/sreekanth/.m2/repository/org/glassfish/extras/glassfish-embedded-all/3.1-b19/glassfish-embedded-all-3.1-b19.jar!/org/glassfish/embed/domain.xml, com.sun.aas.installRoot=/space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target/glassfish_fdeb7e07-4d0f-48f1-9c9f-94c9977b021c, com.sun.aas.instanceRootURI=file:/space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target/glassfish_fdeb7e07-4d0f-48f1-9c9f-94c9977b021c, com.sun.aas.instanceRoot=/space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target/glassfish_fdeb7e07-4d0f-48f1-9c9f-94c9977b021c}
4 Oct, 2010 9:09:02 PM com.sun.enterprise.util.EarlyLogger add
INFO: Total time to parse domain.xml: 110 milliseconds
4 Oct, 2010 9:09:02 PM com.sun.logging.LogDomains$1 log
INFO: GlassFish Server Open Source Edition 3.1-b19 (java_re-private) startup time : Embedded(585ms) startup services(452ms) total(1037ms)
4 Oct, 2010 9:09:03 PM com.sun.logging.LogDomains$1 log
INFO: enterprise_used_delegate_name
4 Oct, 2010 9:09:03 PM com.sun.logging.LogDomains$1 log
INFO: JMXStartupService: JMXConnector system is disabled, skipping.
4 Oct, 2010 9:09:03 PM AppServerStartup run
INFO: [Thread[GlassFish Kernel Main Thread,5,main]] started
4 Oct, 2010 9:09:03 PM org.jboss.arquillian.impl.DynamicServiceLoader verifySameImplementation
Running org.jboss.weld.tests.activities.current.InactiveScopeTest
WARNING: More then one reference to the same implementation was found for org.jboss.arquillian.spi.DeploymentPackager, please verify you classpath
4 Oct, 2010 9:09:03 PM org.jboss.arquillian.impl.DynamicServiceLoader verifySameImplementation
WARNING: More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath
4 Oct, 2010 9:09:03 PM org.jboss.shrinkwrap.impl.base.ServiceExtensionLoader findExtensionImpl
WARNING: Multiple extension implementations found for org.jboss.shrinkwrap.api.BeanArchive, please verify classpath or add a extensionOverride
4 Oct, 2010 9:09:03 PM org.jboss.shrinkwrap.impl.base.ServiceExtensionLoader findExtensionImpl
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.023 sec <<< FAILURE!
WARNING: Multiple extension implementations found for org.jboss.shrinkwrap.api.BeanArchive, please verify classpath or add a extensionOverride
classLoader = WebappClassLoader (delegate=true; repositories=WEB-INF/classes/)
4 Oct, 2010 9:09:03 PM org.jboss.shrinkwrap.impl.base.ServiceExtensionLoader findExtensionImpl
SharedSecrets.getJavaNetAccess()=java.net.URLClassLoader$7@37748ba4
WARNING: Multiple extension implementations found for org.jboss.shrinkwrap.api.spec.JavaArchive, please verify classpath or add a extensionOverride
classLoader = WebappClassLoader (delegate=true; repositories=WEB-INF/classes/)
4 Oct, 2010 9:09:03 PM org.jboss.shrinkwrap.impl.base.ServiceExtensionLoader findExtensionImpl
SharedSecrets.getJavaNetAccess()=java.net.URLClassLoader$7@37748ba4
WARNING: Multiple extension implementations found for org.jboss.shrinkwrap.api.spec.WebArchive, please verify classpath or add a extensionOverride
4 Oct, 2010 9:09:03 PM org.jboss.shrinkwrap.impl.base.ServiceExtensionLoader findExtensionImpl
WARNING: Multiple extension implementations found for org.jboss.shrinkwrap.glassfish.api.ShrinkwrapReadableArchive, please verify classpath or add a extensionOverride
4 Oct, 2010 9:09:03 PM org.jboss.shrinkwrap.impl.base.ServiceExtensionLoader findExtensionImpl
WARNING: Multiple extension implementations found for org.jboss.shrinkwrap.api.exporter.ZipExporter, please verify classpath or add a extensionOverride
4 Oct, 2010 9:09:03 PM org.jboss.shrinkwrap.impl.base.ServiceExtensionLoader findExtensionImpl
WARNING: Multiple extension implementations found for org.jboss.shrinkwrap.spi.Configurable, please verify classpath or add a extensionOverride
4 Oct, 2010 9:09:04 PM com.sun.logging.LogDomains$1 log
INFO: security.secmgroff
4 Oct, 2010 9:09:05 PM com.sun.logging.LogDomains$1 log
INFO: sec.service.startup.enter
4 Oct, 2010 9:09:05 PM com.sun.logging.LogDomains$1 log
INFO: policy.loading
4 Oct, 2010 9:09:05 PM com.sun.logging.LogDomains$1 log
INFO: realm.loaded.successfully
4 Oct, 2010 9:09:05 PM com.sun.logging.LogDomains$1 log
INFO: realm.loaded.successfully
4 Oct, 2010 9:09:05 PM com.sun.logging.LogDomains$1 log
INFO: realm.loaded.successfully
4 Oct, 2010 9:09:05 PM com.sun.logging.LogDomains$1 log
INFO: sec.service.startup.exit
4 Oct, 2010 9:09:05 PM com.sun.common.util.logging.LoggingConfigImpl openPropFile
INFO: Cannot read logging.properties file.
4 Oct, 2010 9:09:05 PM com.sun.logging.LogDomains$1 log
INFO: webContainer.virtualServer.created
4 Oct, 2010 9:09:06 PM com.sun.logging.LogDomains$1 log
INFO: PersistenceStrategyBuilderFactory>>createPersistenceStrategyBuilder: CandidateBuilderClassName = class com.sun.enterprise.web.MemoryStrategyBuilder
4 Oct, 2010 9:09:06 PM com.sun.logging.LogDomains$1 log
INFO: webContainer.virtualServer.loadedDefaultWebModule
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/sreekanth/.m2/repository/org/slf4j/slf4j-simple/1.5.10/slf4j-simple-1.5.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/sreekanth/.m2/repository/org/glassfish/extras/glassfish-embedded-all/3.1-b19/glassfish-embedded-all-3.1-b19.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
24 [main] INFO org.jboss.weld.Version - WELD-000900 1.1.0 (2010-09-23 00:14)
56 [main] INFO org.hibernate.validator.util.Version - Hibernate Validator null
72 [main] INFO org.hibernate.validator.engine.resolver.DefaultTraversableResolver - Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
4 Oct, 2010 9:09:16 PM com.sun.logging.LogDomains$1 log
SEVERE: Exception while loading the app
Results :
Tests in error:
testInactiveScope(org.jboss.weld.tests.activities.current.InactiveScopeTest)
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 30.445s
[INFO] Finished at: Mon Oct 04 21:09:16 IST 2010
[INFO] Final Memory: 39M/245M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.6:test (default-test) on project weld-core-test-arquillian: There are test failures.
Please refer to /space/Sreekanth/workspace/CDI/Oct4th/core/tests-arquillian/target/surefire-reports for the individual test results.
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (WELD-648) CLONE -jsf/permalink example fails with "identifier 'blog' resolved to null"
by sreekanth manga (JIRA)
CLONE -jsf/permalink example fails with "identifier 'blog' resolved to null"
----------------------------------------------------------------------------
Key: WELD-648
URL: https://jira.jboss.org/browse/WELD-648
Project: Weld
Issue Type: Bug
Components: Examples
Affects Versions: 1.0.0.GA
Environment: JBoss_5_2_0_Beta1 date=200911091833
Sun JDK 1.6.0_16-b01
Linux 32bit
Reporter: sreekanth manga
Fix For: 1.0.0.GA
jsf/permalink example deploys, but when accessing the application it fails with following exception:
13:56:27,628 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
javax.el.PropertyNotFoundException: /home.xhtml @30,78 listener="#{blog.loadLatestEntries}": Target Unreachable, identifier 'blog' resolved to null
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:100)
at com.sun.faces.facelets.tag.jsf.core.DeclarativeSystemEventListener.processEvent(EventHandler.java:112)
at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2342)
at javax.faces.event.SystemEvent.processListener(SystemEvent.java:102)
at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:1993)
at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:1941)
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:285)
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:243)
at org.jboss.weld.integration.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:336)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:114)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (WELDX-80) Exception thrown by GAE local ode
by Pete Muir (JIRA)
Exception thrown by GAE local ode
---------------------------------
Key: WELDX-80
URL: https://jira.jboss.org/jira/browse/WELDX-80
Project: Weld Extensions
Issue Type: Bug
Components: Servlet Containers
Reporter: Pete Muir
Feb 21, 2010 11:06:12 PM com.google.appengine.tools.development.JettyContainerService$ScannerListener fileChanged
INFO: /Users/pmuir/workspace/weld-build/dist/weld-1.0.1-Final/examples/jsf/numberguess/src/main/webapp/WEB-INF/appengine-web.xml updated, reloading the webapp!
Feb 21, 2010 11:06:12 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed /Users/pmuir/workspace/weld-build/dist/weld-1.0.1-Final/examples/jsf/numberguess/src/main/webapp/WEB-INF/appengine-web.xml
Feb 21, 2010 11:06:12 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed /Users/pmuir/workspace/weld-build/dist/weld-1.0.1-Final/examples/jsf/numberguess/src/main/webapp/WEB-INF/web.xml
Bad level value for property: .level
Feb 21, 2010 11:06:13 PM org.jboss.weld.bootstrap.WeldBootstrap <clinit>
INFO: WELD-000900 1.0.1 (Final)
Feb 21, 2010 11:06:13 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer
INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
Feb 21, 2010 11:06:13 PM org.jboss.weld.environment.servlet.Listener contextInitialized
INFO: JSR-299 injection will not be available in Servlets, Filters etc. This facility is only available in Tomcat
Feb 21, 2010 11:06:13 PM com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: failed com.google.apphosting.utils.jetty.DevAppEngineWebAppContext(a)36101d01{/,/Users/pmuir/workspace/weld-build/dist/weld-1.0.1-Final/examples/jsf/numberguess/src/main/webapp}
java.lang.AbstractMethodError: javax.servlet.jsp.JspFactory.getJspApplicationContext(Ljavax/servlet/ServletContext;)Ljavax/servlet/jsp/JspApplicationContext;
at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:157)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:530)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:135)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1218)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:500)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at com.google.appengine.tools.development.JettyContainerService.reloadWebApp(JettyContainerService.java:305)
at com.google.appengine.tools.development.JettyContainerService$ScannerListener.fileChanged(JettyContainerService.java:250)
at org.mortbay.util.Scanner.reportChange(Scanner.java:434)
at org.mortbay.util.Scanner.reportDifferences(Scanner.java:305)
at org.mortbay.util.Scanner.scan(Scanner.java:254)
at org.mortbay.util.Scanner$1.run(Scanner.java:225)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Feb 21, 2010 11:06:13 PM com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: failed JettyContainerService$ApiProxyHandler@56dc64a2
java.lang.AbstractMethodError: javax.servlet.jsp.JspFactory.getJspApplicationContext(Ljavax/servlet/ServletContext;)Ljavax/servlet/jsp/JspApplicationContext;
at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:157)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:530)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:135)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1218)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:500)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at com.google.appengine.tools.development.JettyContainerService.reloadWebApp(JettyContainerService.java:305)
at com.google.appengine.tools.development.JettyContainerService$ScannerListener.fileChanged(JettyContainerService.java:250)
at org.mortbay.util.Scanner.reportChange(Scanner.java:434)
at org.mortbay.util.Scanner.reportDifferences(Scanner.java:305)
at org.mortbay.util.Scanner.scan(Scanner.java:254)
at org.mortbay.util.Scanner$1.run(Scanner.java:225)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Feb 21, 2010 11:06:13 PM com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: EXCEPTION
java.lang.AbstractMethodError: javax.servlet.jsp.JspFactory.getJspApplicationContext(Ljavax/servlet/ServletContext;)Ljavax/servlet/jsp/JspApplicationContext;
at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:157)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:530)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:135)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1218)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:500)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at com.google.appengine.tools.development.JettyContainerService.reloadWebApp(JettyContainerService.java:305)
at com.google.appengine.tools.development.JettyContainerService$ScannerListener.fileChanged(JettyContainerService.java:250)
at org.mortbay.util.Scanner.reportChange(Scanner.java:434)
at org.mortbay.util.Scanner.reportDifferences(Scanner.java:305)
at org.mortbay.util.Scanner.scan(Scanner.java:254)
at org.mortbay.util.Scanner$1.run(Scanner.java:225)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (WELD-522) Weld makes my Java SE app startup time >100x slower
by Morten Christensen (JIRA)
Weld makes my Java SE app startup time >100x slower
----------------------------------------------------
Key: WELD-522
URL: https://jira.jboss.org/jira/browse/WELD-522
Project: Weld
Issue Type: Bug
Affects Versions: 1.0.1.Final
Environment: Java 6, Weld 1.01 SE + lots of jars on the classpath
Reporter: Morten Christensen
Booting my Java SE app without weld takes << 1s BUT the 1 line for initializing weld to autowire my app takes at least 4-5 seconds.
My app is not so big and consist of ~20-30 singletons that must be wired + various other non-weld stuff. I have lots of stuff on my classpath so I suspect that could be why weld is going crazy.
I guess this could be improved if I can have weld limited to work only inside my own jar and/or only work with specific classes/packages.
P.S. With breakpoints enabled in a debugger and a bit of unluck, I was even able to have welds initialization to take ~ 5 minutes one day (reduced to seconds again after I removed all breakpoints though).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months