I second that; I don't think it used to be that way in 1.1.2 and it seems
reasonable to me to assume that, *unless* you explicitly specify a
different interface, you want your home/component to extend the
corresponding default javax.ejb.EJBXXX. Looking up the hierarchy of the
implementation in hopes of a matching interface strikes me as just plain
wierd...
-Yori
On Thu, 13 Jun 2002, Richard Steele wrote:
>
> I have an entity bean which extends an entity bean adapter class, like
> this:
>
> /**
> * @ejb.bean
> * name="FooBean"
> * type="CMP"
> * view-type="local"
> * @ejb.home
> * local-extends="javax.ejb.EJBLocalHome"
> * @ejb.interface
> * local-extends="javax.ejb.EJBLocalObject"
> * @ejb.transaction
> * type="Required"
> */
> public abstract class FooBean
> extends EntityBeanAdapter {
>
> ...
>
> }
>
> If I don't specify @ejb.home local-extends="javax.ejb.EJBLocalHome",
> the local home interface extends a mythical
> class ".EntityBeanAdapterLocal" (note, no package--just a "."--and the
> class name is weird). The same goes for the local interface generated
> by @ejb.interface.
>
> I'm assuming this isn't the intended behavior...
>
> Rich
>
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -
>http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
>
> _______________________________________________
> Xdoclet-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
>
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
