|
I beleive that there is a bug in orion 1.4.5, using
env-entries of type java.lang.Long.
Here is a snippet of my ejb-jar.xml
file:
<env-entry>
<env-entry-name>minHistoryDurationMsec</env-entry-name> <env-entry-type>java.lang.Long</env-entry-type> <env-entry-value>60000</env-entry-value> </env-entry> This is inside an <entity> element, with the
bean's descriptor. When I try to create an instance of the bean, I get
this exception(on the client side, of all places):
com.evermind.server.rmi.OrionRemoteException:
javax.ejb.CreateException: javax.naming.NamingException: Unknown env-entry-type
for env-entry minHistoryDurationMsec: 'java.lang.Long'; nested exception
is:
javax.ejb.CreateException: javax.naming.NamingException: Unknown env-ent ry-type for env-entry minHistoryDurationMsec: 'java.lang.Long' com.evermind.server.rmi.OrionRemoteException: javax.ejb.CreateException: javax.naming.NamingException: Unknown env-entry-type for env-entry minHistoryDurationMsec: 'java.lang.Long' at com.evermind.server.ejb.EJBUtils.getUserException(JAX) at UserManager_StatelessSessionBeanWrapper232.getClientAgent(UserManager_StatelessSessionBeanWrapper232.java:406) at java.lang.reflect.Method.invoke(Native Method) ... and so on ... However, if I change it to a
"java.lang.Integer":
<env-entry-type>java.lang.Integer</env-entry-type>
It works.
Mike
|
