]
Norman Richards updated JBSEAM-4105:
------------------------------------
Fix Version/s: The future
(was: 2.2.1.CR1)
NullPointer exception configuring a component using a qualified XML
element
---------------------------------------------------------------------------
Key: JBSEAM-4105
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4105
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.2.CR1
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: The future
Original Estimate: 15 minutes
Remaining Estimate: 15 minutes
Consider the case where there is an existing component defined with the @Name annotation.
Now, you want to be able to configure that component in XML. If the class name for the
component cannot be derived from the name of the component, then Seam throws a
NullPointerException.
Case in point. Assume the following component
package com.mydomain.project;
@Name("com.mydomain.project.init")
public class ProjectInit {
...
}
Now assume I am configuring it with:
<project:init stage="test"/>
Because the class of the component, com.mydomain.project.ProjectInit, cannot be derived
form the component name, com.mydomain.project.init, Seam tries to do something with the
class object that leads to a NullPointerException. What should happen is that Seam should
recognize it is configuring an existing component and ignore that fact that it cannot
resolve the class. That is the intended behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: