I have created an EJB 3.0.
One of its method have a primitive type as a parameter.
When I deploy the SU for this EJB, I am told the EJB is not compatible with the data-binding class.
In fact, the component compares types at deployment.
It tests an equality on Java types using "parameter.getClass()".
This test fails with a primitive type.
A mapping array should be used to bypass this error.
As an example, transform "int" into" java.lang.Integer" for the test.
Such a transformation is only required to make the test successful. It not required at runtime.
I have created an EJB 3.0.
One of its method have a primitive type as a parameter.
When I deploy the SU for this EJB, I am told the EJB is not compatible with the data-binding class.
In fact, the component compares types at deployment.
It tests an equality on Java types using "parameter.getClass()".
This test fails with a primitive type.
A mapping array should be used to bypass this error.
As an example, transform "int" into" java.lang.Integer" for the test.
Such a transformation is only required to make the test successful. It not required at runtime.
Vincent Zurczak added a comment - Thu, 26 Apr 2012 - 13:34:35 +0200 Merged in trunk (commit #32234).
Support primitive types when checking parameters.
Make some error messages better.
Fix some comments.
Vincent Zurczak added a comment - Fri, 8 Jul 2011 - 17:28:59 +0200 Commit # 26003
Fix for the type validation
Update of error messages
Committed on the branch /branches-legacy/petals-enterprise-3.1.x/petals/component-sls/petals-bc-ejb
To merge with the trunk.
Merged in trunk (commit #32234).
Support primitive types when checking parameters.
Make some error messages better.
Fix some comments.