[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
13 years
[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
13 years
[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
13 years