May 2009 - weld-issues - Jboss List Archives

[webbeans-issues] [JBoss JIRA] Created: (WBRI-244) Binding types defined in XML do not work

by David Allen (JIRA)

Binding types defined in XML do not work ---------------------------------------- Key: WBRI-244 URL: https://jira.jboss.org/jira/browse/WBRI-244 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.PREVIEW1 Reporter: David Allen Any binding type defined in XML and then associated with a bean defined in XML or via annotations on the bean does not work. The binding type is not recognized as a binding type. This affects some of the tests in AnnotationTypesTest for section 9.4 of the specification. -- 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, 9 months

2
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-252) Interceptor binding types defined in XML do not work

by David Allen (JIRA)

Interceptor binding types defined in XML do not work ---------------------------------------------------- Key: WBRI-252 URL: https://jira.jboss.org/jira/browse/WBRI-252 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.PREVIEW1 Reporter: David Allen Defining interceptor binding types in XML does not actually result in interceptor binding types. This affects TCK tests in AnnotationTypesTest (uncomment definitions in XML once fixed). -- 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, 9 months

2
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-254) Namespace schema validation being applied to entire beans.xml file

by David Allen (JIRA)

Namespace schema validation being applied to entire beans.xml file ------------------------------------------------------------------ Key: WBRI-254 URL: https://jira.jboss.org/jira/browse/WBRI-254 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.PREVIEW1 Reporter: David Allen When a namespace schema is added for one of the namespaces used in a beans.xml file, the entire beans.xml file is being validated against that schema starting with the <beans> element which is in a different namespace. The XmlBasedMetadataTest currently fails with the following validation error: Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'Beans'. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.jaxp.validation.StreamValidatorHelper.validate(Unknown Source) at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(Unknown Source) at javax.xml.validation.Validator.validate(Validator.java:127) at org.jboss.webbeans.xml.ParseXmlHelper.validateXmlWithXsd(ParseXmlHelper.java:203) ... 31 more ... Removed 22 stack frames -- 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, 9 months

2
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-207) Cache resolved observers

by Pete Muir (JIRA)

Cache resolved observers ------------------------ Key: WBRI-207 URL: https://jira.jboss.org/jira/browse/WBRI-207 Project: Web Beans Issue Type: Task Components: Events Reporter: Pete Muir Assignee: David Allen Fix For: 1.0.0.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, 9 months

1
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-264) JSF 2.0 Wrong Scope

by Alexander Bell (JIRA)

JSF 2.0 Wrong Scope ------------------- Key: WBRI-264 URL: https://jira.jboss.org/jira/browse/WBRI-264 Project: Web Beans Issue Type: Bug Components: JSF Integration Affects Versions: 1.0.0.PREVIEW1 Environment: Tomcat 6.0.18 JSF 2.0 (Mojarra) Reporter: Alexander Bell Priority: Critical I've created a "User" class which sould be request scoped with the properties "name" and "password". Also I've created a AuthenticationService which is session scoped and injects the User with @Current (so the User from the request scope must be injected). Finally I've got a xhtml page which you can enter the user and the password and press a button which triggers an "login" action in the AuthenticationService. (very similar to the jsf-web-example of chapter 2 of the introduction guide. only with jsf 2.0) When I am in the login action the properties "name" and "password" from the injected user are null. But the setters (for name and password) of the User were called before the action was invoked. So I suppose there are two User objects in two different scopes. Actually it should always be the request scope. -- 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, 9 months

2
6
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-267) Supporting proxies with no no-arg constructors

by Pete Muir (JIRA)

Supporting proxies with no no-arg constructors ---------------------------------------------- Key: WBRI-267 URL: https://jira.jboss.org/jira/browse/WBRI-267 Project: Web Beans Issue Type: Feature Request Components: Contexts Reporter: Pete Muir Assignee: Nicklas Karlsson On Tue, May 12, 2009 at 1:11 AM, Jason T. Greene <jason.greene(a)redhat.com> wrote: Hi Everyone, As a non-standard extension, I was thinking that we could support generation proxies of classes not containing no-arg constructors by using various techniques that are supported by most JDKs. This would involve generating a proxy with a constructor call passing bogus parameters. Then a JDK specific approach would be used to instantiate the proxy class: Sun, IcedTea, Mac: Unsafe.allocateInstance() - The most efficient Above + IBM, JRockit: ReflectionFactory.newConstructorForSerialization() -- 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, 9 months

1
1
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-211) Simple bean type checker is too strict for XML defined beans

by Pete Muir (JIRA)

Simple bean type checker is too strict for XML defined beans ------------------------------------------------------------ Key: WBRI-211 URL: https://jira.jboss.org/jira/browse/WBRI-211 Project: Web Beans Issue Type: Bug Components: Simple Beans Reporter: Pete Muir Assignee: Nicklas Karlsson Priority: Minor Fix For: 1.0.0.PREVIEW • If the type is a concrete class, is not an EJB bean class, and is not a parameterized type, a simple bean was declared, as defined in Section 3.2.4, "Declaring a simple bean using XML". -- 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, 9 months

1
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-247) webbeans-numberguess-wicket does not deploy on tomcat

by Jozef Hartinger (JIRA)

webbeans-numberguess-wicket does not deploy on tomcat ----------------------------------------------------- Key: WBRI-247 URL: https://jira.jboss.org/jira/browse/WBRI-247 Project: Web Beans Issue Type: Bug Components: Examples Affects Versions: 1.0.0.PREVIEW1 Environment: Tomcat 6.0.18 JDK 5 update 16 Reporter: Jozef Hartinger Fix For: 1.0.0.PREVIEW2 Application throws the following exception during deployment: Apr 24, 2009 10:45:39 AM org.apache.catalina.core.StandardContext filterStart SEVERE: Exception starting filter wicket.numberguess-example java.lang.NoClassDefFoundError: org/jboss/webbeans/manager/api/WebBeansManager at org.jboss.webbeans.wicket.WebBeansApplication.<init>(WebBeansApplication.java:37) at org.jboss.webbeans.examples.wicket.SampleApplication.<init>(SampleApplication.java:5) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:552) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4363) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1217) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: org.jboss.webbeans.manager.api.WebBeansManager at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 30 more -- 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, 9 months

3
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-248) numberguess-wicket example allows values outside of the current valid range

by Jozef Hartinger (JIRA)

numberguess-wicket example allows values outside of the current valid range --------------------------------------------------------------------------- Key: WBRI-248 URL: https://jira.jboss.org/jira/browse/WBRI-248 Project: Web Beans Issue Type: Bug Components: Examples Affects Versions: 1.0.0.PREVIEW1 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.0.0.PREVIEW2 WBRI-80 should be ported to wicket example as well. -- 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, 9 months

3
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-140) Proxied beans cannot be deserialized

by David Allen (JIRA)

Proxied beans cannot be deserialized ------------------------------------ Key: WBRI-140 URL: https://jira.jboss.org/jira/browse/WBRI-140 Project: Web Beans RI Issue Type: Bug Affects Versions: 1.0.0.ALPHA2 Reporter: David Allen The test ClientProxyTest.testSimpleWebBeanClientProxyIsSerializable fails when run in a container due to classloader issues. Javassist is trying to use its own classloader, which in JBoss AS is a server classloader, to load the class loaded by the WAR classloader. The correct classloaders need to be setup with Javassist in order for persistence to work. Current error in the server is: java.io.InvalidClassException: org.jboss.jsr299.tck.unit.lookup.clientProxy.TunedTuna at javassist.util.proxy.SerializedProxy.readResolve(SerializedProxy.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at org.jboss.jsr299.tck.AbstractTest.deserialize(AbstractTest.java:268) at org.jboss.jsr299.tck.unit.lookup.clientProxy.ClientProxyTest.testSimpleWebBeanClientProxyIsSerializable(ClientProxyTest.java:55) -- 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, 10 months

2
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues May 2009