|
|
|
(no subject) [message #687881 is a reply to message #686525] |
Thu, 23 June 2011 12:44 |
Eclipse User |
|
|
|
Originally posted by:
Farooq,
as Miro already said, it mainly depends on your needs and the
environment you plan to run the application in.
I also prefer Jetty as OSGi bundle (embedded) as it is the technically
simpler solution.
Whichever way you chose now, it is a just a packaging option and you can
still change from embedded to standard and vice versa later on without
too much effort.
HTH
Rüdiger
On 22.06.2011 14:37, Farooq Kamal wrote:
> Hi, are there any performance, stability, memory usage benefits of using
> jetty / tomcat as an OSGI bundle vs standalone server? My application
> also uses Spring-DM, Hibernate JTA etc. Looking forward to insight and
> recommendations
>
> Thanks
> Farooq
--
Rüdiger Herrmann
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
|
Re: (no subject) [message #689685 is a reply to message #689305] |
Tue, 28 June 2011 07:19 |
Eclipse User |
|
|
|
Originally posted by:
You are right, updating with p2 will not be possible with WAR deployment.
On 27.06.2011 13:48, Farooq Kamal wrote:
> Thanks for the input Miro and Rüdiger. I would always favor OSGI Bundles
> approach as you guys pointed out it is much more cleaner.
> This RAP application and a couple of our RCP based applications, share
> multiple core 'features' we have developed. We provide updates with P2
> at installed locations for RCP apps and now I am working on getting the
> RAP app to update from a P2 repo which wouldn't have worked in the case
> of a WAR deployment I suppose.
--
Rüdiger Herrmann
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
Powered by
FUDForum. Page generated in 0.03166 seconds