Re: [Pride-users] Java Persistence API (JPA)

[Jan L. <jle...@gm...>]

Hi Anders
Ok, I think I see what you have in mind. That means that you don't 
suggest to extend PriDE in general but only the entity generator.
Yes of course, it should be pretty easy to extend the generator in a way 
that it also produces JPA compliant code annotations. I would even say 
that - if your are planing to implement parts of JPA on top of PriDE - 
the extemsion of the entity generator were the easiest part ;-)

Just take a look at the generator code which follows the template method 
design pattern and therefore can easily be extended. If you need a 
helping hand, just let me know. If you can specify exactly which 
annotations you'd like to have supported, we may find someone who does 
the job. But of course you are invited to contribute the corresponding 
extension by your own :-)

Regards,
Jan

Anders Peterson wrote:

> My intention are unclear, but something like this... (people get 
> strange ideas)
>
> 1) I'd like to do a (my own) JPA implementaion with PriDE as a 
> building block. Using PriDE I've had to write code for caching, 
> relationship management and other things.  I'm thinking that maybe I'm 
> already well on my way to JPA compliance.
>
> 2) I don't necessarily need full JPA compliance. PriDE (with my 
> extensions) does not need to be fully JPA compliant (a drop in 
> replacement for any other JPA implementation), but I should be able to 
> replace "my code" with some/any other JPA implementation.
>
> 3) JPA users will need an entity bean generator - PriDE already has 
> one (ant task and eclipse plugin). Adding support for JPA annotations 
> can't be too much work. If I (or someone else) would like to try what 
> I mentioned above having a PriDE tools that generates JPA compliant 
> entity beans would help. Perhaps you can see supplying a JPA entity 
> bean generator as marketing for PriDE.
>
> /Anders