-
1. Re: must not be defined as abstract.
earlgrey Mar 20, 2002 4:55 AM (in response to dencel)I got this error when I declared an ejb by mistake to be:
a) ejb spec 2.0 compliant (default xdoclet, i.e. attribute not declared) and deployed in jboss 2.4.x
b) cmp 2.0 compliant and deployed in jboss 2.4.x
lars -
2. Re: must not be defined as abstract.
dencel Mar 20, 2002 5:21 AM (in response to dencel)Which CMP version supports abstract Bean Implementations and what version of JBoss supports this CMP-version?
Is there another solution in JBoss 2.4.4?
Dencel -
3. Re: must not be defined as abstract.
earlgrey Mar 20, 2002 7:32 AM (in response to dencel)> Which CMP version supports abstract Bean
> Implementations and what version of JBoss supports
> this CMP-version?
ejb 2.x + cmp 2.x + jboss 3.0
> Is there another solution in JBoss 2.4.4?
ejb 1.1 + cmp 1.x + jboss 2.4.x
it means, you cannot use abstract getter/setter in jboss 2.4.x. Anyway, you can use code generation with xdoclet (a must have!) or some CASE tool. the code generator handles these details for you (you would not care for cmp 1.x vs. 2.x in terms of abstract accessors/mutators).
Lars
>
> Dencel