Gino Gervasio penned
> My problem is that the primary key of some of my tables are primitive
> integers so my entitybeans' primary keys also are primitive integers.
This is not allowed by the EJB spec. An entity bean's primary key must
be a real object *and* implement java.io.Serializable. Part of the
reason for requiring an object, I assume, is that when the bean starts
out life, it has a null PK, and you cannot universaly represent null in
a primitive.
> Jboss doesn't allow me to deploy these EJBs because it says that "The
> Bean Provider must specify a primary key class in the deployment
> descriptor." What should I do? I can't use java.lang.Integer, can I?
This is precisely what I've done in the past.
> Will the get method retrieve a primitive integer even if its return
> type is an Integer object?
AFAIK you'll need to change your entity beans as well -- you can't just
specify "java.lang.Integer" in the deployment descriptor and have it
autobox for you (though maybe JBoss has that feature?).
--
David Harkness Sony Pictures Digital
Sr. Software Engineer 310.482.4756 [EMAIL PROTECTED]
Those who judge the value of advice by its source
will at once dismiss the best and follow the worst.
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id808&op=click
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
