Basically I think this is a good idea if it is spec compliant. It certainly makes the ActivationSpec more useful. I concluded that it probably wasn't spec compliant from reading the spec, but since I couldn't find a discussion I'd be very happy to be wrong.
Apparently, looking at the list of allowed types, primitives are explicitly not allowed for ResourceAdapter or ManagedConnectionFactory config-properties, so I'd be a bit reluctant to allow them for ActivationSpecs without a clear statement from the spec committee.
thanks david jencks
On Oct 2, 2004, at 4:14 PM, Aaron Mulder wrote:
So part of my previous problem deploying a J2EE connector was that
my ActivationSpec class had a property of type Integer. There's no
setting in the DD for the data type, and Geronimo was blowing up during
deployment with a ClassCastException. I think this was recently discussed
on the connector mailing list, with the implication that other data types
should be supported. I'm thinking we should try to convert the String to
the appropriate data type for the ActivationSpec property if it has a
constructor that takes a String (Integer, etc.) or perhaps if it's a
primitive. Any thoughts on this?
Aaron
