Migration to Spring / JPA

[Yannick Menager-2]

EJBCA is a great piece of software, but the fact that is requires an
EJB2 server is a major pain in the backside :)

So in order to solve that issue, as well as making the whole thing more
maintainable, I've decided to put in the effort to migrate the whole
thing to JPA + Spring.

If anyone wants to give a hand, that would be welcome :)

In order to reduce risk of breaking things, i'm taking an approach to do
a progressive migration with the least changes as possible, keeping the
xdoclet EJB interface layer as-is for the time being. It will allow to
have the new Spring/JPA being running at the same time as EJB2 code, and
thus reduce the risk of breaking things during the process, as well as
reduce the amount of work as no changes to client code are required.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ejbca-develop mailing list
Ejbca-develop@...
https://lists.sourceforge.net/lists/listinfo/ejbca-develop

[Tomas Gustavsson]

There is work in progress to start migrating to EJB3 / JPA in not such a
distant future.

The biggest pain for EJBCA currently (imo) is the XDoclet and XML stuff.


Cheers,
Tomas


Yannick Menager wrote:

> EJBCA is a great piece of software, but the fact that is requires an
> EJB2 server is a major pain in the backside :)
>
> So in order to solve that issue, as well as making the whole thing more
> maintainable, I've decided to put in the effort to migrate the whole
> thing to JPA + Spring.
>
> If anyone wants to give a hand, that would be welcome :)
>
> In order to reduce risk of breaking things, i'm taking an approach to do
> a progressive migration with the least changes as possible, keeping the
> xdoclet EJB interface layer as-is for the time being. It will allow to
> have the new Spring/JPA being running at the same time as EJB2 code, and
> thus reduce the risk of breaking things during the process, as well as
> reduce the amount of work as no changes to client code are required.
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Ejbca-develop mailing list
> Ejbca-develop@...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ejbca-develop mailing list
Ejbca-develop@...
https://lists.sourceforge.net/lists/listinfo/ejbca-develop

[Yannick Menager-2]

I was thinking exactly about the EJB3 or Spring choice earlier today...

I don't mind using EJB3 for the services, but spring is more mature,
powerful as well a more common skill-set item than EJB3.

When you say XML stuff, what are you referring to ? EJB configuration
wiring ?

Tomas Gustavsson wrote:

> There is work in progress to start migrating to EJB3 / JPA in not such a
> distant future.
>
> The biggest pain for EJBCA currently (imo) is the XDoclet and XML stuff.
>
>
> Cheers,
> Tomas
>
>
> Yannick Menager wrote:
>  
>> EJBCA is a great piece of software, but the fact that is requires an
>> EJB2 server is a major pain in the backside :)
>>
>> So in order to solve that issue, as well as making the whole thing more
>> maintainable, I've decided to put in the effort to migrate the whole
>> thing to JPA + Spring.
>>
>> If anyone wants to give a hand, that would be welcome :)
>>
>> In order to reduce risk of breaking things, i'm taking an approach to do
>> a progressive migration with the least changes as possible, keeping the
>> xdoclet EJB interface layer as-is for the time being. It will allow to
>> have the new Spring/JPA being running at the same time as EJB2 code, and
>> thus reduce the risk of breaking things during the process, as well as
>> reduce the amount of work as no changes to client code are required.
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Ejbca-develop mailing list
>> Ejbca-develop@...
>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>    
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Ejbca-develop mailing list
> Ejbca-develop@...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>  

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ejbca-develop mailing list
Ejbca-develop@...
https://lists.sourceforge.net/lists/listinfo/ejbca-develop

[Johan Eklund]

Hi Yannick,

I'm doing my master thesis project on (among other things) the subject
of moving EJBCA to either Spring or EJB3.

Although I haven't done any sample conversion from EJBCA to Spring, my
impression was that *a lot* of bean wiring will be needed. I believe
that the conversion from xdoclet to EJB3 w JPA or Hibernate would be
pretty straighforward for EJBCA and greatly simplify the project. When
trying some Spring examples I also got the impression that things move
pretty quickly and I was not able to run older examples on the new
Spring framework. Since a lot of people depend on EJBCA I think
stability and maintainability should be prioritized. This is just my
opinion and I'm not done evaluating things yet, so feel free to crush my
illusions.. =)

What are the main benefits you think Spring would bring to the table?

Best Regards,
Johan Eklund

ymenager@... skrev:

> I was thinking exactly about the EJB3 or Spring choice earlier today...
>
> I don't mind using EJB3 for the services, but spring is more mature,
> powerful as well a more common skill-set item than EJB3.
>
> When you say XML stuff, what are you referring to ? EJB configuration
> wiring ?
>
> Tomas Gustavsson wrote:
>  
>> There is work in progress to start migrating to EJB3 / JPA in not such a
>> distant future.
>>
>> The biggest pain for EJBCA currently (imo) is the XDoclet and XML stuff.
>>
>>
>> Cheers,
>> Tomas
>>
>>
>> Yannick Menager wrote:
>>  
>>    
>>> EJBCA is a great piece of software, but the fact that is requires an
>>> EJB2 server is a major pain in the backside :)
>>>
>>> So in order to solve that issue, as well as making the whole thing more
>>> maintainable, I've decided to put in the effort to migrate the whole
>>> thing to JPA + Spring.
>>>
>>> If anyone wants to give a hand, that would be welcome :)
>>>
>>> In order to reduce risk of breaking things, i'm taking an approach to do
>>> a progressive migration with the least changes as possible, keeping the
>>> xdoclet EJB interface layer as-is for the time being. It will allow to
>>> have the new Spring/JPA being running at the same time as EJB2 code, and
>>> thus reduce the risk of breaking things during the process, as well as
>>> reduce the amount of work as no changes to client code are required.
>>>
>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Ejbca-develop mailing list
>>> Ejbca-develop@...
>>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>>    
>>>      
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Ejbca-develop mailing list
>> Ejbca-develop@...
>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>  
>>    
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Ejbca-develop mailing list
> Ejbca-develop@...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>  

--
PrimeKey Solutions offers a commercial EJBCA support subscription and training for EJBCA. Please see www.primekey.se or contact info@... for more information. http://download.primekey.se/documents/ejbca_subscription.pdf http://download.primekey.se/documents/ejbca_training.pdf




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ejbca-develop mailing list
Ejbca-develop@...
https://lists.sourceforge.net/lists/listinfo/ejbca-develop

[Tomas Gustavsson]

Hi Yannick,

EJB configuration wiring with XML is a bit of a headache.

There are several parts to this issue:
- EJBCA is say medium size project with a fair amount of wiring. XML
wiring in general is tedious and maintenance is manual. This is to a
large extent helped by using XDoclet though.
- Running in different application server brings in a application server
specific XML files, which can really be a big headache.
- EJB2 uses XML for database mappings as well, with addition to
application server specific mapping files. This is probably the biggest
mess of them all when trying to support multiple databases and multiple
application servers.

Also, XDoclet is an abandoned java 1.4 project and XDoclet does not work
with modern java 5/6 language constructs because XDoclet uses XML
parsing of the java files. So therefore we absolutely must move away
from XDoclet.

Cheers,
Tomas


ymenager@... wrote:

> I was thinking exactly about the EJB3 or Spring choice earlier today...
>
> I don't mind using EJB3 for the services, but spring is more mature,
> powerful as well a more common skill-set item than EJB3.
>
> When you say XML stuff, what are you referring to ? EJB configuration
> wiring ?
>
> Tomas Gustavsson wrote:
>> There is work in progress to start migrating to EJB3 / JPA in not such a
>> distant future.
>>
>> The biggest pain for EJBCA currently (imo) is the XDoclet and XML stuff.
>>
>>
>> Cheers,
>> Tomas
>>
>>
>> Yannick Menager wrote:
>>  
>>> EJBCA is a great piece of software, but the fact that is requires an
>>> EJB2 server is a major pain in the backside :)
>>>
>>> So in order to solve that issue, as well as making the whole thing more
>>> maintainable, I've decided to put in the effort to migrate the whole
>>> thing to JPA + Spring.
>>>
>>> If anyone wants to give a hand, that would be welcome :)
>>>
>>> In order to reduce risk of breaking things, i'm taking an approach to do
>>> a progressive migration with the least changes as possible, keeping the
>>> xdoclet EJB interface layer as-is for the time being. It will allow to
>>> have the new Spring/JPA being running at the same time as EJB2 code, and
>>> thus reduce the risk of breaking things during the process, as well as
>>> reduce the amount of work as no changes to client code are required.
>>>
>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Ejbca-develop mailing list
>>> Ejbca-develop@...
>>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>>    
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Ejbca-develop mailing list
>> Ejbca-develop@...
>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>  
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Ejbca-develop mailing list
> Ejbca-develop@...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ejbca-develop mailing list
Ejbca-develop@...
https://lists.sourceforge.net/lists/listinfo/ejbca-develop

[Yannick Menager-2]

They have a very similar feature-set, except spring is more mature,
flexible, and has more functionalities.

Johan Eklund wrote:

> Hi Yannick,
>
> I'm doing my master thesis project on (among other things) the subject
> of moving EJBCA to either Spring or EJB3.
>
> Although I haven't done any sample conversion from EJBCA to Spring, my
> impression was that *a lot* of bean wiring will be needed. I believe
> that the conversion from xdoclet to EJB3 w JPA or Hibernate would be
> pretty straighforward for EJBCA and greatly simplify the project. When
> trying some Spring examples I also got the impression that things move
> pretty quickly and I was not able to run older examples on the new
> Spring framework. Since a lot of people depend on EJBCA I think
> stability and maintainability should be prioritized. This is just my
> opinion and I'm not done evaluating things yet, so feel free to crush
> my illusions.. =)
>
> What are the main benefits you think Spring would bring to the table?
>
> Best Regards,
> Johan Eklund
>
> ymenager@... skrev:
>> I was thinking exactly about the EJB3 or Spring choice earlier today...
>>
>> I don't mind using EJB3 for the services, but spring is more mature,
>> powerful as well a more common skill-set item than EJB3.
>>
>> When you say XML stuff, what are you referring to ? EJB configuration
>> wiring ?
>>
>> Tomas Gustavsson wrote:
>>  
>>> There is work in progress to start migrating to EJB3 / JPA in not
>>> such a distant future.
>>>
>>> The biggest pain for EJBCA currently (imo) is the XDoclet and XML
>>> stuff.
>>>
>>>
>>> Cheers,
>>> Tomas
>>>
>>>
>>> Yannick Menager wrote:
>>>      
>>>> EJBCA is a great piece of software, but the fact that is requires
>>>> an EJB2 server is a major pain in the backside :)
>>>>
>>>> So in order to solve that issue, as well as making the whole thing
>>>> more maintainable, I've decided to put in the effort to migrate the
>>>> whole thing to JPA + Spring.
>>>>
>>>> If anyone wants to give a hand, that would be welcome :)
>>>>
>>>> In order to reduce risk of breaking things, i'm taking an approach
>>>> to do a progressive migration with the least changes as possible,
>>>> keeping the xdoclet EJB interface layer as-is for the time being.
>>>> It will allow to have the new Spring/JPA being running at the same
>>>> time as EJB2 code, and thus reduce the risk of breaking things
>>>> during the process, as well as reduce the amount of work as no
>>>> changes to client code are required.
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------------
>>>>
>>>> This SF.net email is sponsored by: Microsoft
>>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>> _______________________________________________
>>>> Ejbca-develop mailing list
>>>> Ejbca-develop@...
>>>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>>>          
>>> -------------------------------------------------------------------------
>>>
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Ejbca-develop mailing list
>>> Ejbca-develop@...
>>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>>      
>>
>>
>> -------------------------------------------------------------------------
>>
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Ejbca-develop mailing list
>> Ejbca-develop@...
>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>  
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ejbca-develop mailing list
> Ejbca-develop@...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>  

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ejbca-develop mailing list
Ejbca-develop@...
https://lists.sourceforge.net/lists/listinfo/ejbca-develop

[Yannick Menager-2]

Ha, yes that's the tipical EJB problems.

XDoclet is actually easy to get rid of, the moment you decide on doing
the migration, just generate the files and add them to version control :-)

Tomas Gustavsson wrote:

> Hi Yannick,
>
> EJB configuration wiring with XML is a bit of a headache.
>
> There are several parts to this issue:
> - EJBCA is say medium size project with a fair amount of wiring. XML
> wiring in general is tedious and maintenance is manual. This is to a
> large extent helped by using XDoclet though.
> - Running in different application server brings in a application server
> specific XML files, which can really be a big headache.
> - EJB2 uses XML for database mappings as well, with addition to
> application server specific mapping files. This is probably the biggest
> mess of them all when trying to support multiple databases and multiple
> application servers.
>
> Also, XDoclet is an abandoned java 1.4 project and XDoclet does not work
> with modern java 5/6 language constructs because XDoclet uses XML
> parsing of the java files. So therefore we absolutely must move away
> from XDoclet.
>
> Cheers,
> Tomas
>
>
> ymenager@... wrote:
>  
>> I was thinking exactly about the EJB3 or Spring choice earlier today...
>>
>> I don't mind using EJB3 for the services, but spring is more mature,
>> powerful as well a more common skill-set item than EJB3.
>>
>> When you say XML stuff, what are you referring to ? EJB configuration
>> wiring ?
>>
>> Tomas Gustavsson wrote:
>>    
>>> There is work in progress to start migrating to EJB3 / JPA in not such a
>>> distant future.
>>>
>>> The biggest pain for EJBCA currently (imo) is the XDoclet and XML stuff.
>>>
>>>
>>> Cheers,
>>> Tomas
>>>
>>>
>>> Yannick Menager wrote:
>>>  
>>>      
>>>> EJBCA is a great piece of software, but the fact that is requires an
>>>> EJB2 server is a major pain in the backside :)
>>>>
>>>> So in order to solve that issue, as well as making the whole thing more
>>>> maintainable, I've decided to put in the effort to migrate the whole
>>>> thing to JPA + Spring.
>>>>
>>>> If anyone wants to give a hand, that would be welcome :)
>>>>
>>>> In order to reduce risk of breaking things, i'm taking an approach to do
>>>> a progressive migration with the least changes as possible, keeping the
>>>> xdoclet EJB interface layer as-is for the time being. It will allow to
>>>> have the new Spring/JPA being running at the same time as EJB2 code, and
>>>> thus reduce the risk of breaking things during the process, as well as
>>>> reduce the amount of work as no changes to client code are required.
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------------
>>>> This SF.net email is sponsored by: Microsoft
>>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>> _______________________________________________
>>>> Ejbca-develop mailing list
>>>> Ejbca-develop@...
>>>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>>>    
>>>>        
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> Ejbca-develop mailing list
>>> Ejbca-develop@...
>>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>>  
>>>      
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Ejbca-develop mailing list
>> Ejbca-develop@...
>> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>>    
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Ejbca-develop mailing list
> Ejbca-develop@...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>  

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ejbca-develop mailing list
Ejbca-develop@...
https://lists.sourceforge.net/lists/listinfo/ejbca-develop