August 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-548) Conversation not available in EL

by David Beaumont (JIRA)

Conversation not available in EL -------------------------------- Key: WELD-548 URL: https://jira.jboss.org/browse/WELD-548 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.0.1.Final Environment: GlassFish Server Open Source Edition 3.0.1 on Mac OS 10.6 and Windows 7. WELD-000900 1.0.1 (SP2) Reporter: David Beaumont The Weld documentation states that you can use #{conversation} to access the conversation from within a facelets page. This does not work, though using #{javax.enterprise.context.conversation} does access the conversation. I discovered this by looking at the source at: http://anonsvn.jboss.org/repos/weld/core/trunk/impl/src/main/java/org/jbo... Also see: http://seamframework.org/Community/ApparentInaccuraciesInConversationDocu... -- 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

3
7
0 / 0

[JBoss JIRA] Created: (WELD-560) Allow beans.xml to parsed outside of Weld

by Pete Muir (JIRA)

Allow beans.xml to parsed outside of Weld ----------------------------------------- Key: WELD-560 URL: https://jira.jboss.org/browse/WELD-560 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Pete Muir Fix For: 1.1.0.BETA1 Allow beans.xml to be parsed externally, and provided via a Java API -- 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

1
3
0 / 0

[JBoss JIRA] Created: (WELD-618) Lifecycle observation swallows exceptions

by Nicklas Karlsson (JIRA)

Lifecycle observation swallows exceptions ----------------------------------------- Key: WELD-618 URL: https://jira.jboss.org/browse/WELD-618 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson If your observer throws an exception, the information is hidden (bad message) 13:43:52,556 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=vfs:///C:/Java/AS/jboss-6.0.0.M4/server/default/deploy/KaKe.war_WeldBootstrapBean state=Create: org.jboss.weld.exceptions.DeploymentException: Exception #0 :null at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:55) at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:34) -- 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

2
1
0 / 0

[JBoss JIRA] Closed: (WELD-593) Manual Shutdown in SE by Configuration

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-593?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed WELD-593. -------------------------- Labels: se shutdown sonfiguration (was: se shutdown sonfiguration) Assignee: Pete Muir Resolution: Out of Date ShutdownManager was added a long time ago > Manual Shutdown in SE by Configuration > -------------------------------------- > > Key: WELD-593 > URL: https://jira.jboss.org/browse/WELD-593 > Project: Weld > Issue Type: Feature Request > Environment: Java SE, w/o EJB > Reporter: Peter Royle > Assignee: Pete Muir > Priority: Minor > > The developer could set a configuration variable to let WebBeans know that they will be taking responsibility for initiating the shutdown sequence when it makes sense for their app, and hence WebBeans needn't do any automatic shutdown sequence. This could be done programatically: > public void (@Observes Deployed Manager manager, @Parameters List<String> params, @Current Configuration config) { > config.setManualShutdown(true); > System.out.println("You provided " + params.size() + " parameters. Well done."); > } > Alternatively this could be done by setting a property in beans.xml or beans.properties. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (WELD-584) Documentation for Jetty Bean Manager JNDI configuration is out of date.

by Lincoln Baxter III (JIRA)

Documentation for Jetty Bean Manager JNDI configuration is out of date. ----------------------------------------------------------------------- Key: WELD-584 URL: https://jira.jboss.org/browse/WELD-584 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.1.Final Environment: Jetty 7.1.3 Reporter: Lincoln Baxter III (RELATED) https://jira.jboss.org/secure/ManageAttachments.jspa?id=12416127 http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/environments.... The documentation is out of date, since the package names of required classes were changed during the eclipse ownership change: <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd"> <Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext"> <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg> <Ref id="webAppCtx"/> </Arg> <Arg>BeanManager</Arg> <Arg> <New class="javax.naming.Reference"> <Arg>javax.enterprise.inject.spi.BeanManager</Arg> <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg> <Arg/> </New> </Arg> </New> </Configure> This documentation is also incomplete, since a <resource-ref> must be included in the web.xml: <resource-ref> <res-ref-name>BeanManager</res-ref-name> <res-type>javax.enterprise.inject.spi.BeanManager</res-type> <res-auth>Container</res-auth> </resource-ref> -- 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

2
7
0 / 0

[JBoss JIRA] Created: (WELD-615) Change proxy CL to TCCL in default ProxyServices implementation

by David Allen (JIRA)

Change proxy CL to TCCL in default ProxyServices implementation --------------------------------------------------------------- Key: WELD-615 URL: https://jira.jboss.org/browse/WELD-615 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.BETA1 Reporter: David Allen Assignee: David Allen Fix For: 1.1.0.BETA2 There is still a problem with many applications and servers by not using the TCCL for proxy classes. GAE for instance was using the TCCL by initializing the static member of Javassist's ProxyFactory, and GlassFish needs to do the same. The only reason not to use TCCL is based on how the TCK and other tests are written for Weld: they make use of package protected classes and members. Since this approach to writing application classes is not common in practice (usually private, protected or public scope specified), I would recommend changing the default ProxyServices implementation to support the common practice and not our tests. The test frameworks or test sets can probably be changed to provide a different ProxyServices implementation. Off hand I don't know exactly how that can happen yet, but I think it's worth investigating. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (WELD-492) Allow servlet listeners to be managed beans

by Nicklas Karlsson (JIRA)

Allow servlet listeners to be managed beans ------------------------------------------- Key: WELD-492 URL: https://jira.jboss.org/jira/browse/WELD-492 Project: Weld Issue Type: Bug Components: Activities Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Fix For: 1.0.2.CR1 Loosen then check return !Extension.class.isAssignableFrom(clazz.getJavaClass()) && !(clazz.isAnonymousClass() || (clazz.isMemberClass() && !clazz.isStatic())) && !Reflections.isParamerterizedTypeWithWildcard(javaClass) && !servletApiAbstraction.SERVLET_CLASS.isAssignableFrom(javaClass) && !servletApiAbstraction.FILTER_CLASS.isAssignableFrom(javaClass) && !servletApiAbstraction.SERVLET_CONTEXT_LISTENER_CLASS.isAssignableFrom(javaClass) && !servletApiAbstraction.HTTP_SESSION_LISTENER_CLASS.isAssignableFrom(javaClass) && !servletApiAbstraction.SERVLET_REQUEST_LISTENER_CLASS.isAssignableFrom(javaClass) && !ejbApiAbstraction.ENTERPRISE_BEAN_CLASS.isAssignableFrom(javaClass) && !jsfApiAbstraction.UICOMPONENT_CLASS.isAssignableFrom(javaClass) && (hasSimpleWebBeanConstructor(clazz) || InstantiatorFactory.useInstantiators()); in AbstractBeanDeployer to only prohibit classes explicitly mentioned in the spec, allowing servlet listeners to be managed beans (and UIComponents, too?) -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Updated: (WELD-26) Add database support to login example

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-26?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-26: -------------------------- Issue Type: Task (was: Feature Request) Priority: Minor (was: Major) > Add database support to login example > ------------------------------------- > > Key: WELD-26 > URL: https://jira.jboss.org/browse/WELD-26 > Project: Weld > Issue Type: Task > Components: Examples > Reporter: Pete Muir > Priority: Minor > 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-555) Pluggable validation

by Kabir Khan (JIRA)

Pluggable validation -------------------- Key: WELD-555 URL: https://jira.jboss.org/browse/WELD-555 Project: Weld Issue Type: Feature Request Components: Weld SPI Reporter: Kabir Khan >From Weld Dev mailing list: -------------------------------------------- Hey Kabir, Some time ago we decided to move the weld-int stuff (whatever is specific to JBAS) into JBAS itself, for making the integration between the two a bit more straightforward. So the stuff that is now inside JBAS is a copy of the former weld-int project (with the poms modified to match JBAS). I made some changes to JSF stuff and JNDI registration. Following a comment made by Ales, the deployer-mc-int stuff stayed in its old location (as it is not currently packaged inside the JBAS distro), and is mainly untouched. Since it seems to depend on other modules, it may make sense to extract the common stuff and make it a dependency to both the JBAS weld-int and the extraneous mc-weld-int. For now, I just made sure that the clone works, and perhaps this is a step that is hard to complete before M4. I think that you can use the deployer-mc-int as is for now, if you're not affected by the current duplication issues. Or, let me know if I can help working something out. Marius On 10-06-11 9:42 AM, Kabir Khan wrote: I am about to revisit the MC/Weld integration for Ales's and my talk at JUDCon. The work was done under https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk, more specificially under https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk/deployer-mc-int. Updating AS trunk now I see a new weld-int project with the following sub directories; assembly/ deployer/ ejb/ pom.xml/ webtier/ In https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk I see assembly/ deployer/ deployer-mc-int/ ejb/ pom.xml/ webtier/ The https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk/deployer-mc-int are working, and the next step is to try this out in AS, but I am confused how the two locations relate to each other and where my deployer-mc-int/ stuff should go? Cheers, Kabir _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev -- 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

2
4
0 / 0

[JBoss JIRA] Created: (WELD-459) A final class interceptor or an interceptor class with a final method not detected as a definition error

by Ondrej Skutka (JIRA)

A final class interceptor or an interceptor class with a final method not detected as a definition error -------------------------------------------------------------------------------------------------------- Key: WELD-459 URL: https://jira.jboss.org/jira/browse/WELD-459 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Ondrej Skutka Spec says: If the bean class of a managed bean declares or inherits a class level interceptor binding or a stereotype with interceptor bindings, it must not be declared final, or have any non-static, non-private, final methods. If a managed bean has a class- level interceptor binding and is declared final or has a non-static, non-private, final method, the container automatically detects the problem and treats it as a definition error. If a non-static, non-private method of a bean class of a managed bean declares a method level interceptor binding, neither the method nor the bean class may be declared final. If a non-static, non-private, final method of a managed bean has a method level interceptor binding, the container automatically detects the problem and treats it as a definition error. org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalClassClassLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalClassMethodLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalMethodClassLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalMethodMethodLevelInterceptorTest In the TCK trunk -- 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, 10 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010