This should definitely work, my patch is for something a lot more obscure!
I use persistence name quite often, and they work fine.

Example (copied and pasted directly from source)

    /**
     * @ejb:persistent-field
     * @ejb:interface-method view-type="local"
     * @orion:persistence persistence-name="currencyID"
     */
    public abstract java.lang.Integer getCurrency();



Daniele Arduini said:
> Hani Suleiman wrote:
>> the last released version (1.1) of xdoclet fully supports orion up to
>> version 1.5.4 (there is an obscure bug when it comes to mapping
>> compound  pk entities to orion-specific collections...I have a patch
>> for that  lying around somewhere).
>>
>
> If you find it please send it as soon as possible!
> I've been hit by this bug recently. The problem is that you can't
> have a different name/persistence-name for the PK-columns (compounds or
> simple).
>
> ex.:
>
> This doesn't work:
>
>     /**
>       * @ejb:pk-field
>       * @ejb:persistent-field
>       * @orion:persistence persistence-name="pk_field_id"
>       */
>      public abstract int getPKFieldId();
>
>
> This work:
>
>     /**
>       * @ejb:pk-field
>       * @ejb:persistent-field
>       * @orion:persistence persistence-name="pk_field_id"
>       */
>      public abstract int getPk_field_id();
>
>
>
> --
> Ing. Daniele Arduini <[EMAIL PROTECTED]>
> CINETICA - via III settembre, 11 - 47891 Dogana (San Marino)
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Xdoclet-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to