August 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-414) Make Weld docs available for JBoss AS 6

by Pete Muir (JIRA)

Make Weld docs available for JBoss AS 6 --------------------------------------- Key: WELD-414 URL: https://jira.jboss.org/jira/browse/WELD-414 Project: Weld Issue Type: Task Components: Documentation Reporter: Pete Muir Assignee: Dan Allen Priority: Critical Fix For: 1.0.2.CR1 Magnolia is the tool we use to build out the JBoss community site. Please take a moment and go to http://www.jboss.org/author. Username: ********** Password: ********** Scroll down and open jbossas --> docs --> 6-x Highlight 6-x and press the "Open page..." button at the bottom. The main AS6 docs page will open in another tab or window. >From here you can see how AS6 documentation will be broken up into "Core" and "Component". Click on the "JavaServer Faces (JSF)" link You'll get an idea of what you can do with your section. As you can see, we want to provide something beyond the DocBook documentation we've had in the past. We want a developer to be able to come to the docs section and find everything he might need to work with a particular part of AS6, including spec info, javadoc, sample code, and links to other info. Of course, we don't want to fork the stuff we already have but we also need to recognize that developers want to use AS6 as a single product and they come to AS6 with an "AS6" mindset. So they are thinking, "How do I use the EJB features built into AS6?" or "How do I use the Weld framework built into AS6?". We need to provide documentation that answers those questions from an AS6 point of view. But I'm using the word "documentation" in a loose sense. It doesn't have to be a single document. The aggregation of AS6 information is done with Magnolia and not necessarily with a single DocBook monograph. I am assuming that most components will have at least some AS6-specific content that needs to go somewhere. If it's possible/practical to use Maven profiles to pull in special content and create an AS6 version of a document then that would be best. If not, then AS6-specific content could be put into its own small document. The rest can be referenced with links to the component's project documentation. As for where the doco lives in what part of SVN, I don't think that it really matters. I like the idea that each component team is responsible for handling their section however is most practical for them. I just want to make sure that at the end of the day an AS6 user has everything he needs in a way that is easy to find and understand. Action items for you: * Take a look at http://jboss.org/help/projectpageguide.html to learn about Magnolia. * Find the section on Weld and start building out the page(s) * Work out how best to incorporate the Weld ref guide into the JBoss AS docs - remove irrelevant sections - apply JBoss AS styling -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Resolved: (CDITCK-16) Tests for transactional observers are inconsistent

by David Allen (JIRA)

[ https://jira.jboss.org/browse/CDITCK-16?page=com.atlassian.jira.plugin.sy... ] David Allen resolved CDITCK-16. ------------------------------- Resolution: Done These tests were removed since they did not really test the assertions. > Tests for transactional observers are inconsistent > -------------------------------------------------- > > Key: CDITCK-16 > URL: https://jira.jboss.org/browse/CDITCK-16 > Project: CDI TCK > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tests > Affects Versions: 1.0.0.Beta1 > Reporter: David Allen > Fix For: 1.1.0.CR1 > > Attachments: server.log > > > The tests use a single stateful session bean which has many observer methods defined. Each test fires a different type of event through a stateless session bean. All of the observer methods have been invoked with the correct state information stored according to logging information, but the tests are not always seeing the same state information. > The results of the tests are never random in any way, but they have changed over a period of a day or two with other changes to the TCK or RI. Any local changes to these tests that are innocuous still do not change the results in any way. The same set of tests are always inconsistent with the logging information on the same day. -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-567) Weld should throw an exception if a resource producer field is defined with a scope other than @Dependent

by Stuart Douglas (JIRA)

Weld should throw an exception if a resource producer field is defined with a scope other than @Dependent --------------------------------------------------------------------------------------------------------- Key: WELD-567 URL: https://jira.jboss.org/browse/WELD-567 Project: Weld Issue Type: Feature Request Reporter: Stuart Douglas The spec does allow containers to support this, however in many cases it does not make sense, e.g. for an entity manager you can end up with a Conversation scoped proxy for a transaction scoped entity manager. It would be better to disallow this altogether, both for portability reason and to prevent end user confusion. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-476) OutOfMemory Exception When Deploying (Bootstrapping) Single BDA with 621 classes

by Roger Kitain (JIRA)

OutOfMemory Exception When Deploying (Bootstrapping) Single BDA with 621 classes -------------------------------------------------------------------------------- Key: WELD-476 URL: https://jira.jboss.org/jira/browse/WELD-476 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.Final Environment: GlassFish v3.01 Macos w/ 4 GB memory Reporter: Roger Kitain Upon deploying a war with WEB-INF/beans.xml and 621 classes under WEB-INF/classes, an outofmemory exception is produced: org.glassfish.deployment.common.DeploymentException: java.lang.OutOfMemoryError: Java heap space at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:167) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:125) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:224) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:310) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at org.glassfish.deployment.autodeploy.AutoOperation.run(AutoOperation.java:141) at org.glassfish.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:573) at org.glassfish.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:459) at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:391) at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:376) at org.glassfish.deployment.autodeploy.AutoDeployService$1.run(AutoDeployService.java:195) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: com.google.common.collect.ComputationException: java.lang.OutOfMemoryError: Java heap space at com.google.common.collect.MapMaker$StrategyImpl.compute(MapMaker.java:602) at com.google.common.collect.MapMaker$StrategyImpl.compute(MapMaker.java:462) at com.google.common.collect.CustomConcurrentHashMap$ComputingImpl.get(CustomConcurrentHashMap.java:2045) at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:164) at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:61) at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:88) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:134) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:377) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:165) ... 18 more Caused by: java.lang.OutOfMemoryError: Java heap space at java.lang.Class.copyMethods(Class.java:2745) at java.lang.Class.getDeclaredMethods(Class.java:1791) at org.jboss.weld.util.reflection.SecureReflections$8.work(SecureReflections.java:197) at org.jboss.weld.util.reflection.SecureReflections$8.work(SecureReflections.java:193) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAndWrap(SecureReflectionAccess.java:67) at org.jboss.weld.util.reflection.SecureReflections.getDeclaredMethods(SecureReflections.java:192) at org.jboss.weld.introspector.jlr.WeldClassImpl.<init>(WeldClassImpl.java:282) at org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:140) at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:50) at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:38) at com.google.common.collect.MapMaker$StrategyImpl.compute(MapMaker.java:592) at com.google.common.collect.MapMaker$StrategyImpl.compute(MapMaker.java:462) at com.google.common.collect.CustomConcurrentHashMap$ComputingImpl.get(CustomConcurrentHashMap.java:2045) at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:164) at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:61) at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:88) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:134) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:377) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:165) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:125) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:224) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:310) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at org.glassfish.deployment.autodeploy.AutoOperation.run(AutoOperation.java:141) at org.glassfish.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:573) There is nothing special about the BDA passed to weld - a single BDA with 621 classes. -- 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

14 years, 4 months

4
16
0 / 0

[JBoss JIRA] Assigned: (WELD-13) Switch to using a builder to make immutable bean objects

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-13?page=com.atlassian.jira.plugin.syst... ] Pete Muir reassigned WELD-13: ----------------------------- Assignee: (was: Nicklas Karlsson) > Switch to using a builder to make immutable bean objects > -------------------------------------------------------- > > Key: WELD-13 > URL: https://jira.jboss.org/browse/WELD-13 > Project: Weld > Issue Type: Feature Request > Components: Class Beans (Managed and Session) > Reporter: Pete Muir > Fix For: 1.1.0.BETA1 > > > Currently we do a lot of init in the *Bean which, to be flexible, isn't in the constructor, which stops the Bean objects being truly immutable. It's also not nice to read. > A challenge will be the two phase bootstrap. -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-443) Rewrite all beans to use builders and immutable objects

by Pete Muir (JIRA)

Rewrite all beans to use builders and immutable objects ------------------------------------------------------- Key: WELD-443 URL: https://jira.jboss.org/jira/browse/WELD-443 Project: Weld Issue Type: Feature Request Components: Built-in beans, Class Beans (Managed and Session), Producers (Methods, Fields and Disposers) Reporter: Pete Muir Priority: Critical Fix For: 1.0.2.CR1 -- 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

14 years, 4 months

1
2
0 / 0

[JBoss JIRA] Updated: (WELD-8) Reduce reliance on invokeOnInstance by mapping against interfaces at deploy

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-8?page=com.atlassian.jira.plugin.syste... ] Pete Muir updated WELD-8: ------------------------- Fix Version/s: 1.1.0.BETA2 (was: 1.1.0.BETA1) > Reduce reliance on invokeOnInstance by mapping against interfaces at deploy > --------------------------------------------------------------------------- > > Key: WELD-8 > URL: https://jira.jboss.org/browse/WELD-8 > Project: Weld > Issue Type: Feature Request > Components: Class Beans (Managed and Session) > Reporter: Pete Muir > Fix For: 1.1.0.BETA2 > > -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-581) Remove NamesStringBuilder, it's a pointless abstraction

by Pete Muir (JIRA)

Remove NamesStringBuilder, it's a pointless abstraction ------------------------------------------------------- Key: WELD-581 URL: https://jira.jboss.org/browse/WELD-581 Project: Weld Issue Type: Bug Components: Infrastructure Reporter: Pete Muir Fix For: 1.1.0.BETA1 -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-565) Unhelpful error message if observer message is annotated @Inject

by Pete Muir (JIRA)

Unhelpful error message if observer message is annotated @Inject ---------------------------------------------------------------- Key: WELD-565 URL: https://jira.jboss.org/browse/WELD-565 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session), Events Reporter: Pete Muir Fix For: 1.1.0.BETA1 WELD-000408 org.jboss.weld.event-ObserverMethod-com.foobar.MyPortableExtension.method afterDeploymentValidation(javax.enterprise.inject.spi.AfterDeploymentValidation, javax.enterprise.inject.spi.BeanManager) cannot be annotated with @Initializer * Should say @Inject ! * Should say that observer methods are automatically injection points -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-222) Coordinate with Mojarra to get Weld JSF app working from Maven central

by Dan Allen (JIRA)

Coordinate with Mojarra to get Weld JSF app working from Maven central ---------------------------------------------------------------------- Key: WELD-222 URL: https://jira.jboss.org/jira/browse/WELD-222 Project: Weld Issue Type: Feature Request Components: Infrastructure Reporter: Dan Allen Fix For: 1.0.0.CR2 Although the Weld artifacts are published to the Maven central repository, it's still not possible to get a JSF app built without relying on the JBoss Maven repository. The problem is JSF. See output below. We have sent a request to the Mojarra team to publish their artifacts in the central repository. When they do, we need to align with that version. Missing: ---------- 1) javax.faces:jsf-api:jar:2.0.0-RC Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.faces -DartifactId=jsf-api -Dversion=2.0.0-RC -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.faces -DartifactId=jsf-api -Dversion=2.0.0-RC -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.example:helloworld:war:0.0.1-SNAPSHOT 2) javax.faces:jsf-api:jar:2.0.0-RC ---------- 1 required artifact is missing. for artifact: org.example:helloworld:war:0.0.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) However, if you add java.net repository and override the JSF versions to use the 2.0 release, you get errors on startup INFO: Weld 1.0.0-CR1 2009-10-21 21:58:22.119::WARN: Failed startup of context org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@66f4652{/jsf2,/home/lily/workspace/jsf2/0_helloworld/src/main/webapp} java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) at org.mortbay.jetty.handler.ContextHandler.loadClass(ContextHandler.java:1101) at org.mortbay.jetty.plugin.Jetty6MavenConfiguration.parseAnnotations(Jetty6MavenConfiguration.java:135) at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configure(AbstractConfiguration.java:119) at org.mortbay.jetty.webapp.WebXmlConfiguration.configureWebApp(WebXmlConfiguration.java:180) at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configureWebApp(AbstractConfiguration.java:96) at org.mortbay.jetty.plus.webapp.Configuration.configureWebApp(Configuration.java:149) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1247) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) at org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) -- 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

14 years, 4 months

2
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010